- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Unless you are using a custom MAIL FROM with your verified sending domain, Amazon will generate an envelope sender on the amazonses.com domain in the format GUID@amazonses.com, where GUID is a unique identifier. If you want to tie the complaint to the original message, you will need a mechanism to archive sent messages and correlate the generated MAIL FROM address by capturing both the generated MAIL FROM and the original Message-ID by catching a delivery feedback notification though an SES topic configured to dispatch an HTTPS event for that purpose.
Have you taken a look at the suppression list, this way if you send to bad address it will not send again which increases your bounce rate and impacts your rating. https://docs.aws.amazon.com/ses/latest/DeveloperGuide/sending-email-suppression-list.html
Thanks @mdibella. I am able to match sent messages via the ID. I can see all data related to the sending of individual mails sent for site registrations. However, your point about the Return-Path being @amazonses.com could be relevant to spam categorisation, although my SPF records DO list this domain as a legitimate sender.
Thanks @Rob_H. I already block email addresses that reply with a complaint. All complaints are from the first and only message to that address.
There is no mystery surrounding what these messages are, or how many are sent etc.. The only mystery is why Yahoo are so aggressive in their abuse reporting when people have elected to receive the mail by registering for a service. I find it hard to believe that so many reach the wrong person, or that so many people sign up for a service and then mark their activation email as spam.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 8 mesi fa