We're having an interesting issue with email addresses getting added to the Suppression List because of a complaint. In our case, we have an email sent after a user registers for an event and the email is addressed to the registrant and BCCs two other email addresses. The email is first routed to postfix locally on the server and then postfix hands it off to SES to send.
It looks like the recipient (or the recipients email host) complained about the email and their email address was correctly added to the Suppression List. However, the two BCCd email addresses were also added to the Suppression List as a "complaint" at the exact same time. That doesn't seem correct. Is this normal behavior? If so, is there a way to avoid it?
Here's the anonymized mail.log output. test1@test.org and test2@test.org were BCCd and registrant@anothertest.org was the recipient in the To field.
Jan 14 17:10:55 209 postfix/cleanup[323810]: 309DD17756C: message-id=<20220114171055.309DD17756C@aserver.com>
Jan 14 17:10:55 209 postfix/qmgr[2363]: 309DD17756C: from=<test1@test.org>, size=30856, nrcpt=3 (queue active)
Jan 14 17:10:55 209 postfix/smtp[323812]: 309DD17756C: to=<test2@test.org>, relay=email-smtp.us-west-2.amazonaws.com[52.43.195.206]:587, delay=0.35, delays=0.01/0/0.13/0.22, dsn=2.0.0, status=sent (250 Ok 0101017e59921e79-f8db37fc-1474-4a92-8cbd-58d7f96cd24d-000000)
Jan 14 17:10:55 209 postfix/smtp[323812]: 309DD17756C: to=<test3@test.org>, relay=email-smtp.us-west-2.amazonaws.com[52.43.195.206]:587, delay=0.35, delays=0.01/0/0.13/0.22, dsn=2.0.0, status=sent (250 Ok 0101017e59921e79-f8db37fc-1474-4a92-8cbd-58d7f96cd24d-000000)
Jan 14 17:10:55 209 postfix/smtp[323812]: 309DD17756C: to=<registrant@anothertest.org>, relay=email-smtp.us-west-2.amazonaws.com[52.43.195.206]:587, delay=0.35, delays=0.01/0/0.13/0.22, dsn=2.0.0, status=sent (250 Ok 0101017e59921e79-f8db37fc-1474-4a92-8cbd-58d7f96cd24d-000000)
Jan 14 17:10:55 209 postfix/qmgr[2363]: 309DD17756C: removed
AWS 官方已更新 2 年前
I also have the same sort of situation. Send from user@test.org Sent to user@another.org cc'd: user@test,org; baduser@test.org
The bounce back for baduser@test.org added baduser@test.org to the suppression list, but it also added user@test.org to the suppression list. Is this expected normal behavior? Both addresses get put on the suppression list? Is it because they are the same domain? In this case, someone mistyped one of the addresses. I would have expected only the badaddress@test.org to be the one put on the suppression list
"bouncedRecipients": [{ "emailAddress": "user@test.org", "action": "failed", "status": "5.3.0", "diagnosticCode": "smtp; 550 permanent failure for one or more recipients (baduser@test.org:550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [DM3NAM02FT014.eop-nam...)" }, { "emailAddress": "baduser@test.org", "action": "failed", "status": "5.3.0", "diagnosticCode": "smtp; 550 permanent failure for one or more recipients (baduser@test.org:550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [DM3NAM02FT014.eop-nam...)" }],