We recently upgraded our password for AWS SES to Signature v4 using the process described here:
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-credentials.html
Note: We are using SMTP to send our e-mails, not web services (HTTP).
After generating the signed password I plugged it into our application and tested sending e-mails from our staging and production servers. Success!
However, we are now finding that we are unable to send e-mails when running the application locally on our development workstations (localhost).
The error we get at runtime is:
StatusCode: MustIssueStartTlsFirst
Message: The SMTP server requires a secure connection or the client was not authenticated. The server response was: Authentication required
Is there any way to get this to work from our development workstations or does Signature v4 absolutely prevent that?
I should add that when running from our development workstations, we are configured to use the staging database. So the parameters we are using in development are the same as on staging. The primary difference is that on the staging server the application runs on an SSL secured IIS platform, while in development we are running on localhost - no SSL. Still - the web application is the client to AWS's SMTP server so I'm not quite sure how that factor plays a role.
question from:
https://stackoverflow.com/questions/65829940/cant-access-aws-ses-via-smtp-from-localhost-after-upgrading-password-to-signatu 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…