#26 SMTP Stopped working

[Adam]

Webcollab has be working great for almost a year sending mail thourgh my gmail account. Today it stopped working and gave me the blow error when I try to send. Please help.

Setup I have taken;
made sure "Less secure apps" was on
check google for new security setting
check setting including user name and password
Created an outlook.com accound and tried to send from there. (Same result)

Opening connection to smtp.gmail.com on port 587
S: 220-as7.*.com ESMTP Exim 4.87 #1 Wed, 09 Nov 2016 15:19:51 -0500
S: 220-We do not authorize the use of this system to transport unsolicited,
S: 220 and/or bulk e-mail.
C: EHLO www.mydomain.com
S: 250-s7.*.com Hello s7.*.com [...]
S: 250-SIZE 52428800
S: 250-8BITMIME
S: 250-PIPELINING
S: 250-AUTH PLAIN LOGIN
S: 250-STARTTLS
S: 250 HELP
C: STARTTLS
S: 220 TLS go ahead
Starting TLS...
C: TLS success
C: EHLO www.mydomain.com
S: 250-s7.*.com Hello s7.**.com [...]
S: 250-SIZE 52428800
S: 250-8BITMIME
S: 250-PIPELINING
S: 250-AUTH PLAIN LOGIN
S: 250 HELP
C: TLS negotiation completed
C: AUTH PLAIN
S: 334
C: Authenticating...
S: 535 Incorrect authentication data
C: Authentication failure for PLAIN AUTH
C: AUTH LOGIN
S: 334 VXNlcm5hbWU6
C: Sending username...
S: 334 UGFzc3dvcmQ6
C: Sending password...
S: 535 Incorrect authentication data
C: Authentication failure for AUTH LOGIN
WebCollab not able to authenticate with SMTP server

---

//-- Email --

//enable email to send messages? (Values are 'Y' or 'N')
define('USE_EMAIL', 'Y' );

//location of SMTP server (IP address or FQDN)
define('SMTP_HOST', 'smtp.gmail.com' );

//mail transport (SMTP for standard mailserver, or PHPMAIL for PHP mail() )
define('MAIL_TRANSPORT', 'SMTP' );
//SMTP port (leave as 25 for ordinary mailservers)
define('SMTP_PORT', 587 );

//use smtp auth? ('Y' or 'N')
define('SMTP_AUTH', 'Y' );
  //if using SMTP_AUTH give username & password
  define('MAIL_USER', 'myemailaddress@gmail.com' );
  define('MAIL_PASSWORD', 'correctpassword' );
  //use TLS encryption?
  define('TLS', 'Y' );

[Andrew Simpson]

Very interesting. What you've done looks correct and it was working.
Everything works fine until WebCollab asks to authenticate by AUTH PLAIN to which the server replies '334' (O.K. to proceed). Then authentication with user and password fails.

WebCollab then asks to use AUTH LOGIN which is also accepted with '334' and a base64 encoded request for username. Trying alternate forms of authentication is permitted by the RFC. However that fails too.

After that there are no other forms of authentication available and WebCollab has to abort.

I have double checked the relevant RFC's and WebCollab is correctly following the protocol for AUTH PLAIN and AUTH LOGIN. I guess your username and password is correct.

Looking around the web, I think that Gmail will 'ban' addresses that fail authentication more than a few times - or even try more than form of authentication in one session. There is an interesting article here:

http://www.webholism.com/blog/sara/gmail-suddenly-stopped-sending-my-business-emails/#

I will try connecting to Gmail myself and see if that works.