Unable to deliver to Yahoo addresses (SES IP getting blocked)

IP address 54.240.4.9 is also being blocked by Yahoo. SES is pretty much unusable now since we can't communicate with customers who use Yahoo.

mspza wrote:
IP address 54.240.4.9 is also being blocked by Yahoo. SES is pretty much unusable now since we can't communicate with customers who use Yahoo.
Hi,

same here: Yahoo blocks SES Service
Our SES Account number: 057459126252

Affected IP´s
54.240.4.12
54.240.4.17

Reporting-MTA: dsn; a4-12.smtp-out.eu-west-1.amazonses.com

Action: failed
Final-Recipient: rfc822; [DELETEDbyMe]@aol.com
Diagnostic-Code: smtp; 554 4.4.7 Message expired: unable to deliver in 840 minutes.<421 4.7.0 [TSS04] Messages from 54.240.4.12 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html>
Status: 4.4.7

Reporting-MTA: dsn; a4-17.smtp-out.eu-west-1.amazonses.com

Action: failed
Final-Recipient: rfc822; [DELETEDbyMe]@yahoo.de
Diagnostic-Code: smtp; 554 4.4.7 Message expired: unable to deliver in 840 minutes.<421 4.7.0 [TSS04] Messages from 54.240.4.17 temporarily deferred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html>
Status: 4.4.7

In addition both IP are blacklisted at
IPrange RBL Project
SORBS SPAM
ZapBL

See also MXToolbox
https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a54.240.4.9&run=toolpage
https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a54.240.4.12&run=toolpage
https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a54.240.4.17&run=toolpage

This is pretty annoying, because I can´t raise a case to AWS, because we are just Basic Users. But this SPAM - Issue is to be solved by AWS immediately. Is there nor monitoring from AWS on that issue? AWS can reblock them self at SORBS SPAM.

Is someone from AWS reading here?

Johannes

Addendum:
Our Domain is pretty OK:
https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3aminifink.com&run=toolpage

Edited by: Hans-im-glueck on Apr 30, 2019 1:15 PM

Hi Hans-im-glueck and mspza,

Our systems automatically identified the issue that you observed, and we immediately started working with Yahoo to fix it. According to our data, the issue has been resolved since the afternoon (Pacific time) of April 30.

Additionally, please note that this issue was not caused by these IP addresses being added to the SORBS Spam list. Major email providers, including Yahoo, use their own proprietary systems to identify unsolicited content, and do not rely on lists such as SORBS. I mention this because you might continue to see these addresses listed on SORBS’ lookup page. However, this issue was caused by Yahoo customers complaining directly to Yahoo about content sent from those IP addresses. For more information about Blacklists and Amazon SES, please see our FAQ at https://docs.aws.amazon.com/ses/latest/DeveloperGuide/blacklists.html.

I’m very sorry that this issue impacted your ability to send email through SES. Please let me know if you continue to experience any issues sending to Yahoo addresses.

Thank you for using Amazon SES!

Brent @ AWS

Thank you for the feedback. The problem does seem to be resolved now.

Hi Brent

We are having the same problem.
Emails sent with SES are marked as spam for Yahoo.
The emails work fine and arrive in Inbox for Gmail.
Can you help me please? What should I do for fixing the problem?

Thank you in advance

Tsiory

Hello, We are having the same problem. Emails sent with SES were not delivered to Yahoo. The emails work fine and arrive in Inbox for Gmail. What should I do to fix the problem? I really appreciate any help you can provide. Mina