-
Notifications
You must be signed in to change notification settings - Fork 451
Description
When the sender is
Bilbo Baggins <bbaggins@theshire.com>
the regex for replacing the From address works. The part between < and > is removed, and the verified From address is added, leaving
From: Bilbo Baggins <i-am-verified@sender.com>
If the sender is just
bbaggins@theshire.com
then the removal of the original fails, leaving
From: bbaggins@theshire.com <i-am-verified@sender.com>
AWS scans the first item in the From header and fails with unverified sender.
message: 'sendRawEmail() returned error.',
error:
{ MessageRejected: Email address is not verified. The following identities failed the check in region EU-WEST-1: <bbaggins@theshire.com>
Have been using the function for over 12 months without problem until failures when the sender address is as described, surrounded by others still working correctly with the more usual sender format, so it's not anything to do with sandboxes or other config. The only difference I can see for the failed messages is the sender from address being as discussed.
This line:
aws-lambda-ses-forwarder/index.js
Line 209 in 6522b93
| fromText = 'From: ' + from.replace(/<(.*)>/, '').trim() + |