06-19-2023, 09:13 PM
Hi Remy
Thanks for the code to capture the error. The error is "support.google.com BadCredentials" + plus a long string of characters. I do not understand this at all.
I can send email via ordinary gmail using these same credentails. If there were some issue with Indy I would expect that I wouldn't be alone with this problem.
My code has not changed for over a year and has been working fine until early June.
Your previous comment is probably the issue.
what does your configuration of TIdSMTP (and TIdFTP?) look like? Especially in regards to authentication? Service providers do change their authentication requirements over time. And right now, a lot of service providers are switching to newer TLS versions, and/or to OAuth2, etc. So, it might just be that your code is simply outdated for your service provider's needs. Maybe they cut over to a new system at the beginning of June, and you didn't get your code ready in time.
I'm using libeay32.dll and ssleay32.dll
gSMTP->AuthType = satDefault;
gSMTP->IOHandler = IdSSLIOHandlerSocketOpenSSL1;
gSMTP->Host = "smtp-relay.gmail.com";
gSMTP->Port = 587;
gSMTP->Username = "myusername";
gSMTP->Password = "mypassword";
gSMTP->MailAgent = "AISLA";
gSMTP->UseTLS = utUseExplicitTLS;
gSMTP->PipeLine = true;
// gSMTP->OnStatus = gSMTPStatus; //gSMTPStatus is unknown
IdSSLIOHandlerSocketOpenSSL1->Destination = "smtp.gmail.com";
IdSSLIOHandlerSocketOpenSSL1->Host = "smtp.gmail.com";
IdSSLIOHandlerSocketOpenSSL1->MaxLineAction = maException;
IdSSLIOHandlerSocketOpenSSL1->SSLOptions->Method = sslvTLSv1;
IdSSLIOHandlerSocketOpenSSL1->SSLOptions->Mode = sslmUnassigned;
IdSSLIOHandlerSocketOpenSSL1->SSLOptions->VerifyDepth = 0;t
I don't know if this is what you asked for re configuration.
Thanks for your help as always.
Bob
Thanks for the code to capture the error. The error is "support.google.com BadCredentials" + plus a long string of characters. I do not understand this at all.
I can send email via ordinary gmail using these same credentails. If there were some issue with Indy I would expect that I wouldn't be alone with this problem.
My code has not changed for over a year and has been working fine until early June.
Your previous comment is probably the issue.
what does your configuration of TIdSMTP (and TIdFTP?) look like? Especially in regards to authentication? Service providers do change their authentication requirements over time. And right now, a lot of service providers are switching to newer TLS versions, and/or to OAuth2, etc. So, it might just be that your code is simply outdated for your service provider's needs. Maybe they cut over to a new system at the beginning of June, and you didn't get your code ready in time.
I'm using libeay32.dll and ssleay32.dll
gSMTP->AuthType = satDefault;
gSMTP->IOHandler = IdSSLIOHandlerSocketOpenSSL1;
gSMTP->Host = "smtp-relay.gmail.com";
gSMTP->Port = 587;
gSMTP->Username = "myusername";
gSMTP->Password = "mypassword";
gSMTP->MailAgent = "AISLA";
gSMTP->UseTLS = utUseExplicitTLS;
gSMTP->PipeLine = true;
// gSMTP->OnStatus = gSMTPStatus; //gSMTPStatus is unknown
IdSSLIOHandlerSocketOpenSSL1->Destination = "smtp.gmail.com";
IdSSLIOHandlerSocketOpenSSL1->Host = "smtp.gmail.com";
IdSSLIOHandlerSocketOpenSSL1->MaxLineAction = maException;
IdSSLIOHandlerSocketOpenSSL1->SSLOptions->Method = sslvTLSv1;
IdSSLIOHandlerSocketOpenSSL1->SSLOptions->Mode = sslmUnassigned;
IdSSLIOHandlerSocketOpenSSL1->SSLOptions->VerifyDepth = 0;t
I don't know if this is what you asked for re configuration.
Thanks for your help as always.
Bob

