Announcements
Don’t miss your chance to add AT&T Protect Advantage. Peace of mind, starting at $15 per month. Open enrollment ends 3/31. See all protection plans.

New Member

 • 

4 Messages

Thu, Jan 23, 2020 9:30 PM

Email I try to send to att.net addresses is failing due to prodigy.net servers not using TLS

I send a sports newsletter from my server every couple of days and severeal of my subscribers have att email addresses (@att.net, @sbcglobal.net, @pacbell.net, etc.). For the past 3 days, i.e. starting on 1/20/2020, many of my emails to those subscribers have been failing (they've been fine for years before now). I first noticed this in my email send logs (for one email I was trying to send to my own email address, [email scrubbed]):

LOG: MAIN

cwd=/usr/local/cpanel/whostmgr/docroot 4 args: /usr/sbin/exim -v -M 1iugtK-0009l9-2s

delivering 1iugtK-0009l9-2s

LOG: MAIN

Sender identification U=tourna D=tournamart.com S=[email scrubbed]

Connecting to al-ip4-mx-vip1.prodigy.net [144.160.235.143]:25 from 216.38.29.5 ... failed: Connection timed out (timeout=5m)

LOG: MAIN

H=al-ip4-mx-vip1.prodigy.net [144.160.235.143] Connection timed out

Connecting to ff-ip4-mx-vip1.prodigy.net [144.160.159.21]:25 from 216.38.29.5 ... failed: Connection timed out (timeout=5m)

LOG: MAIN

H=ff-ip4-mx-vip1.prodigy.net [144.160.159.21] Connection timed out

Connecting to al-ip4-mx-vip2.prodigy.net [144.160.235.144]:25 from 216.38.29.5 ... failed: Connection timed out (timeout=5m)

LOG: MAIN

H=al-ip4-mx-vip2.prodigy.net [144.160.235.144] Connection timed out

Connecting to ff-ip4-mx-vip2.prodigy.net [144.160.159.22]:25 from 216.38.29.5 ... failed: Connection timed out (timeout=5m)

LOG: MAIN

H=ff-ip4-mx-vip2.prodigy.net [144.160.159.22] Connection timed out

LOG: MAIN

== [email scrubbed] R=dkim_lookuphost T=dkim_remote_smtp defer (110): Connection timed out

Other emails I send that do not end up using those prodigy.net servers go through just fine. I did a little more digging and found on https://ns.tools/prodigy.net that the above servers do not support TLS:

al-ip4-mx-vip1.prodigy.net [144.160.235.143] does not accept TLS.

al-ip4-mx-vip2.prodigy.net [144.160.235.144] does not accept TLS.

ff-ip4-mx-vip1.prodigy.net [144.160.159.21] does not accept TLS.

ff-ip4-mx-vip2.prodigy.net [144.160.159.22] does not accept TLS.

while I believe my outgoing server requires TLS and so I THINK that is probably my problem. I really don't want to have to configure my outgoing server to not use TLS but is that my only option? I was on the phone with multple AT&T departments for hours today and none of them could tell me even who at AT&T to discuss this problem with.

Responses

Brand User
ATTHelp

Administrator

 • 

108.4K Messages

3 weeks ago

We're here to help, @TournaMart!

 

We suggest e-mailing the AT&T Postmaster staff regarding this, as they are able to assist with delivery issues similar to the one you are currently experiencing.

 

To find more information, go to our AT&T Postmaster support page, and go down to the tab labeled "I sent an email to an AT&T customer but received an error. What does this mean?" from there, it will have the information for e-mailing our Postmaster staff.

 

Let us know if you have any questions- we'll be here to help!

 

Donovan, AT&T Community Specialist

*I am an AT&T employee, and the postings on this site are my own and don't necessarily represent AT&T's position, strategies or opinions.

New Member

 • 

4 Messages

Thanks, but it turned out to be a problem with the CSF firewall settings on the server that hosts my site. Neithger I nor my site provider nor the server hosting company were able to figure out what changed recently or why it only affected email to your prodigy.net serevers but reinstalling the CSF software cleared the problem up.

Brand User
ATTHelp

Administrator

 • 

108.4K Messages

@TournaMart

 

We're glad to see that you found a resolution!

 

Thank you for reaching out to the AT&T Community Forums team for assistance. If you need help with anything in the future, we'll be here. Have a wonderful day!

 

Aminah, AT&T Community Specialist

*I am an AT&T employee, and the postings on this site are my own and don't necessarily represent AT&T's position, strategies or opinions.