Amazon SES IP address is showing up on 0SPAM and SORBS SPAM blocklists

1

We have just setup using Amazon SES to send out mailings and was going through final preparations today before utilizing it. We ran a test message through a test portal and it came back showing that the sending IP address was blocklisted by 0SPAM and SORBS SPAM. I have confirmed this using MXToolbox. Is there a way to get this resolved quickly or to get us setup with another shared IP address that is NOT already listed as SPAM by blocklists? 54.240.48.132 ...... a48-132.smtp-out.amazonses.com is the IP in question.

Thanks.

demandé il y a 2 ans815 vues
2 réponses
1

Yeah good luck getting AWS to care about this issue. According to support, AWS engineers should respond here within a day or so, and I see your question has been up for 16 days now with no response. I have no idea why so many people pay to use such a flawed service as SES

répondu il y a 2 ans
-2

I understand this is an old issue, but I would just like to clear this up:

We actively monitor DNSBLs that could impact delivery across the entire Amazon SES service, or that could impact the ability to send email to recipients who use major email providers, such as Gmail, Yahoo, AOL, and Hotmail. The DNSBLs offered by Spamhaus fall into this category. When one of our IP addresses appears on a list that meets either of these criteria, we take immediate action to have that address removed from the DNSBL as quickly as possible.

We don't monitor DNSBLs that are unlikely to impact delivery across the entire Amazon SES service, or that don't have a measurable impact on delivery to major email providers. The DNSBLs offered by SORBS and UCEPROTECT fall into this category. Because of the specific listing and delisting practices of the vendors who operate these lists, we are unable to have our IP addresses removed from these lists.

DNS Blackhole List (DNSBL) FAQs

AWS
omare
répondu il y a 2 ans
  • What about delivery to addresses managed by Apple under the me.com icloud.com and mac.com domains? They routinely reject almost all of the messages we send via SES, despite being fully compliant and configured with SPF, DKIM, DMARC and custom FROM domains as recommended by AWS. Apple does not tell you which specific blocklist the Amazon SES IP addresses are on, so there is no recourse for having them removed. The one and only piece of information you receive from them is "Diagnostic-Code: smtp; 554 5.7.1 [CS01] Message rejected due to local policy. Please visit https://support.apple.com/en-us/HT204137"

    What is Amazon doing to address SES deliverability problems with one of the biggest email providers on the planet, Apple?

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions