[FOLIO-2243] Cannot send email as support.lib@chalmers.se Created: 06/Sep/19  Updated: 03/Jun/20  Resolved: 12/Sep/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: Peter Murray Assignee: Peter Murray
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:

 Description   

Using the AWS SES credentials, cannot send email as support.lib@chalmers.se even though that email address is verified with AWS.



 Comments   
Comment by Peter Murray [ 06/Sep/19 ]

Posted to AWS' support forum:

I'm following the instructions for "Testing Email Sending Using the Command Line" (https://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email-smtp-client-command-line.html), and I'm receiving a `554 Message rejected: Email address is not verified` even though the email address is marked as Verified in SES. It has been verified for a couple of hours. Two independent developers have tried to send mail using that From address using IAM credentials that work for another email address that has been verified for months.

The only thing slightly unusual about the email address is that the user name portion contains a period. Has anyone else seen a problem sending email using a recently verified email address?

Comment by Peter Murray [ 09/Sep/19 ]

Got a reply from an AWS staffer that wasn't helpful in solving the problem.

Are you connecting to the SMTP endpoint in the same AWS Region where you verified the email address? When you verify an email address or domain, the verification only applies to the Region that you verified it in.

For example, if you verified an email address in the US East (N. Virginia) Region, then you'd receive the "Email address not verified" error if you tried to send an email by connecting to the email-smtp.us-west-2.amazonaws.com endpoint (in this case, you'd have to connect to email-smtp.us-east-1.amazonaws.com instead).

I hope this information helps. Let me know if I can provide any additional information.

Added additional information to the Forum post. Also tested the email address this morning and got the same SMTP error.

Comment by Peter Murray [ 12/Sep/19 ]

No word from AWS. Closing because Hongwei found a work-around.

Generated at Thu Feb 08 23:19:15 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.