Dear AT&T,
The customers of some large email service providers can not send email to the users in your acquired domains such as snet.net, prodigy.net, and ameritech.net, at least some of which may have been outsourced to Yahoo.
An example log file is 553 5.3.0 flph384 DNSBL:RBL 521 < x.x.x.x > is blocked.
The technical support representatives at 1-888-803-2455 insist that the problem is, and that it is correct, that you are blocking email from senders when the MX record for their domain points to a different IP address than the IP address of their SMTP relay servers.
It's mind boggling that this is really a check a large email service provider could be performing.
I hope this response is a misunderstanding, but it has been told to your customers several times who can not receive email from other ISP's.
Please do not put the blame on other ISP's when you appear to be blocking email for a technically incorrect reason.
The online form for AT&T delisting requests insists the above SMTP relay is not blocked.
I suspect the real issue may be that the internal RBL used within the AT&T servers is not updating for the the acquired domain names mentioned above.
I have an escalation open with abuse_rbl@abuse-att.net that is awaiting a response.
It is not clear if it is AT&T, Yahoo, or some other outsourced support is behind the scenes providing support to resolve this issue.
I would appreciate if someone from AT&T who understands the nature of this problem and can help address this issue would contact me for more information.
The customers of some large email service providers can not send email to the users in your acquired domains such as snet.net, prodigy.net, and ameritech.net, at least some of which may have been outsourced to Yahoo.
An example log file is 553 5.3.0 flph384 DNSBL:RBL 521 < x.x.x.x > is blocked.
The technical support representatives at 1-888-803-2455 insist that the problem is, and that it is correct, that you are blocking email from senders when the MX record for their domain points to a different IP address than the IP address of their SMTP relay servers.
It's mind boggling that this is really a check a large email service provider could be performing.
I hope this response is a misunderstanding, but it has been told to your customers several times who can not receive email from other ISP's.
Please do not put the blame on other ISP's when you appear to be blocking email for a technically incorrect reason.
The online form for AT&T delisting requests insists the above SMTP relay is not blocked.
I suspect the real issue may be that the internal RBL used within the AT&T servers is not updating for the the acquired domain names mentioned above.
I have an escalation open with abuse_rbl@abuse-att.net that is awaiting a response.
It is not clear if it is AT&T, Yahoo, or some other outsourced support is behind the scenes providing support to resolve this issue.
I would appreciate if someone from AT&T who understands the nature of this problem and can help address this issue would contact me for more information.