Starting about two days ago our server is unable to send any emails to any @bellsouth.net addresses.

Myself, or my customers do not receive any bounces from bellsouth, but the mail-queue does list:
deferral:Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
Thus, the emails aren't getting delivered --- For any emails going to bellsouth.net.

This isn't a temporary deferral as the bellsouth emails have stayed in the queue over 20+ hours now so far..

I contacted them (bellsouth) today and they didn't have a clue.

I am not listed in any dnsrbl's at all.. Totally clean. So I am perplexed as to why this issue is occurring.

It appears also the problem possibly doesn't just exist with bellsouth, but with the other branches of AT&T as well such as sbcglobal etc etc.

Thanks for your time and any help you can provide.

(P.S. For any TP techs ---- I have an open TT about this: 4902135PLNT)

Same for me. Getting bounced emails from sbcglobal.net & att along with bellsouth, all of which are using an att.net blacklist. Thought at first it was a fluke on one server, tried another, then another, .... all with the same results.

I think att.net is listing large IP blocks and not blocking out individual servers.

I agree, my server is now blocked and all of the IPs on my server are blocked. Normally, only one IP sends mail, so if it were a spam issue, that IP would be blocked. As all my IPs are blocked, I can only assume they are just blocking everything from all IPs in a range.

They don't even offer a feedback loop... I really though AOL was the worst, but at least they send me a warning before they block me. I wish I could get my hands on the Bellsouth tech that make the decision to block my IP block...

Any way to relay through a non blocked smtp server? I am now being blocked by all ATT domains. All IPs on my server are blocked. It is no cause of my own. I reviewed all outgoing mail, and found only 48 messages in the last 45 days to any ATT domain. I examined each messahe and found no problems with any, they were all legitimate e-mail. Also, I too, cannot be found on any block list. This is bigger than me. I say that because I have only used one ip address for outbound mail, yet they have blocked all my IPs. There is no way they could know the other ips on my server. They must have blocked an entire subnet from theplanet.

In case someone at the planet is going to try and sort this out, my ip is 74 54 40 226.

My customers are starting to get agitated.

Jason

Hi Folks.

I received a response to my trouble ticket about this issue.

And thought I would give a general summary to y'all since it is relevant.

Basically I have been told by the abuse dept from here at TP that ATT and their affiliates are blocking a very large number of IP ranges from TP. They (TP Abuse) are aware of the situation and are in contact with ATT/etc to resolve it ASAP.

It is quite apparent (from what I gather) that this issue isn't at the fault of us, the TP customers. My personal opinion is whoever is in charge of the blocklist at ATT went nuts or something (reasonable explanation LOL)
I personally have complete faith that TP will rectify this situation ASAP.

Just curious what what other IP ranges you guys/gals are in.
I'm the the 70.85.*.* range.
And i see Jasgot is in the 74.54.*.* range..

@Serra:
I also thought AOL was the worst. But they have really cleaned up their operation the past year or so IMO.
And they always seem to respond to any queries/concerns I have within a reasonable amount of time.
But as far as ATT/Bellsouth:
I have personally sent a couple emails and reports to Bellsouth/ATT-abuse about this over the past 24-48 hours or so (when I thought it was just me) with no response .


I think at this point in time though, it's more "in TP's ballpark" to get it handled since it appears many many multiple IP ranges have been effected from TP and it isn't just an isolated incident (as I feared it was just me, and I spazzed - You better believe it! See my sig! LOL).

But again, with such a widespread block like this I have full and complete faith in TP in fixing this. As they are on the case as we speak

(Sorry if my message is a bit garbled, and rambling. It's what a spaz-a-thon does to me LOL)

My IP is in the 207.218.*.* range, so its a fairly large block of IPs!



Yea, I'm looking at that next. I have a server in CA that isn't blocked, so I may try to relay mail through that server, but that seems a bit hard. Clients would need to send mail to my TP server, then the server would relay it to CA.

I'm pretty sure this is related to the DNS issues of the missing PTR records. One of their (TP's) DNS servers is out of whack and returns blank info for any PTR lookup. Many mail servers will not receive mail if your IP does not resolve to anything... and depending on the software used the IP will eventually fall into the blacklist / spam scores...

AT&T and all it's subsidiaries use the same list AFAIK... I've started getting bounces from Comcast and about half a dozen other ISPs... Who knows how many just silently delete the emails...

Good luck getting TP to fix it...

Nope, I checked my PTR record and it looks fine, according to a DNS checker. Here is another funny thing... I thought my server in CA was ok, but I just started getting bounces from it as well.

xxx@bellsouth.net
SMTP error from remote mail server after initial connection:
host gateway-f2.isp.att.net [207.115.11.16]: 550-66.x.xx.xx blocked by ldap:ou=rblmx,dc=att,dc=net
550 Error - Blocked for abuse. See http://att.net/blocks

This server is at PacificRack at One Wilshire, so it can't be a TP problem blocking email from both servers.

It is affecting all of my servers and I am not using the planets DNS

Indeed... This seems like a possibility.
In my resolv.conf as it came out of the box I have as one of the IP's: 70.84.160.11
Which returns, when looking for a PTR:
Host 11.160.84.70.in-addr.arpa not found: 3(NXDOMAIN)

Would this have anything to do with it?

Edit: NM, found updated resolvers for D5.. Seems the ones I had been using were pretty old. But the problem still persists with ATT/SBC/etc.

Er... Wait...bellsouth.net mails are going thru for me now!
I was gonna fiddle with the resolv.conf.. But I thought I'd give sending an email to bell one more time.. Works.. Don't know what TP did. But Kudos!

sbcglobal is still being retarded though.
failure: Connected_to_207.115.20.23_but_sender_was_rejected./Remote_host_said:_553_5.3.0_flpi113,DNSBL:521<_MY IP_>_is_blocked.__For_information_see_http://worldnet.att.net/general-info/bls_info/block_inquiry.html/


So, this is very weird IMO.. Bellsouth-OK SBCGLOBAL-NOT OK.. When they should be running off the same BL.

Getting blocked on 67.15.XXX.XXX network.

Same problem here -- our IPs are on 75.125.XXX.XXX

Remote host said: 553 Unable to Resolve Reverse DNS

Same thing happens with ATT group of domains and others. SBCglobal has been rejecting ours for weeks.

Same here..

I came here to see if it was just me they're ignoring. I've submitted their removal form twice since Friday and both times they said my IP is not blocked.

It's somewhat comforting to know I'm not alone, but my clients are getting pretty upset with me about it..

553 5.3.0 flpi092,DNSBL:521< 67.19.xxx.xxx>_is_blocked.__For_information_see_http://worldnet.att.net/general-info/bls_info/block_inquiry.html

I haven't even gotten a response from the abuse folks at att/sbc/bell/crazyipblockerISP yet.
But seriously, they are saying you're not blocked when you are?.......geez
About how long did it take for you to get the initial response back from those folks? It's been right at about 48hrs here for me so far since I initially filled in their form.

FWIW,

A traceroute from my server to a SBC mailserver:

traceroute to 207.115.21.24 (207.115.21.24), 30 hops max, 300 byte packets
1 me.com (me) 15.561 ms 12.152 ms 11.973 ms
2 vl2.dsr02.dllstx5.theplanet.com (70.84.160.162) 0.696 ms 0.717 ms 0.467 ms
3 po52.dsr02.dllstx3.theplanet.com (70.85.127.109) 0.601 ms 0.834 ms 0.717 ms
4 et5-2.ibr04.dllstx3.theplanet.com (70.87.253.29) 0.699 ms 0.599 ms *
5 12.87.41.149 (12.87.41.149) 1.158 ms 1.115 ms 0.967 ms
Icmp checksum is wrong
6 tbr2.dlstx.ip.att.net (12.122.100.98) 44.561 ms Icmp checksum is wrong
46.601 ms Icmp checksum is wrong
44.891 ms
MPLS Label=32277 CoS=6 TTL=1 S=0
7 cr2.dlstx.ip.att.net (12.122.18.205) 45.047 ms 44.853 ms 44.310 ms
MPLS Label=17274 CoS=6 TTL=255 S=0
8 cr2.la2ca.ip.att.net (12.122.28.178) 44.415 ms 44.358 ms 44.549 ms
MPLS Label=16515 CoS=6 TTL=255 S=0
9 cr2.sffca.ip.att.net (12.122.31.134) 44.543 ms 44.606 ms 44.444 ms
MPLS Label=17149 CoS=6 TTL=255 S=0 Icmp checksum is wrong
10 tbr1.sffca.ip.att.net (12.122.19.14) 47.023 ms Icmp checksum is wrong 44.697 ms Icmp checksum is wrong 44.810 ms
MPLS Label=31978 CoS=6 TTL=1 S=0
11 gar7.sffca.ip.att.net (12.122.85.129) 44.143 ms 43.966 ms 44.070 ms
12 12.122.79.98 (12.122.79.98) 45.559 ms 45.599 ms 45.565 ms
13 ded2-p8-0.snfcca.sbcglobal.net (151.164.95.113) 47.059 ms 47.345 ms 47.185 ms
14 SBCIS-PRODIGY-1148522.cust-rtr.pacbell.net (67.113.233.186) 48.557 ms 48.586 ms 48.563 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Just got the "You are not blocked email" from att....... But yet:
failure:Connected_to_207.115.20.23_but_sender_was_rejected./Remote_host_said:_553_5.3.0_flpi113,DNSBL:521<_MyIp_>_is_blocked.__
For_information_see_http://worldnet.att.net/general-info/bls_info/block_inquiry.html/

Persists.......very very very weird.

No response to the two tickets I put in at Bellsouth, but TP has responded to my ticket and I'm now unblocked. Looks like they were able to get BS/ATT to unblock me.

Need to check my other IPs, but the main IP is working.

Cool deal Serra.
I also am now able to send to BS, but not to SBCGLOBAL which is another ATT aff.
There must be a separate blocklist that SBC uses. Because according to ATT/BS I'm not on their's.. But yet the same error is given when I send to SBC, as I was receiving from BS/ATT. With the same "See: www.att.blah.blah" part in the error.

Though, I must say TP abuse Dept. has been great so far and very helpful thru this.

Edit to add, there are issues as well with the same bounce back from pacbell.net addresses. Does anyone have a list of all ATT affiliated ISP's?

No change in the situation overnight. Still can't send to anyone@sbcglobal. I've submitted a ticket at TP. Hopefully they can help me out.

I have 2 customers who are mostly affected by it and one of them has all their mail forwarded from my server to her sbcglobal email, so she isn't getting any mail. I've offered to set up mailboxes instead of forwards but I think we both keep assuming it will start working again soon..

In the past, its been a very bad idea to forward emails to an account that is at risk of being blocked for spam. They often penalize the sender for the spam that arrives at the account, which would be the forwarding server.

I suggest that you have them stop using the sbc account, if that is possible. If that is not possible, make it clear that if they report any spam, they are reporting themselves.

Ok.

All appears to be cool on my end once again. Can send to SBC/Pac/att/bell with no bounces or deferrals.

Anyone still facing this issue, I would recommend putting in a TT with TP first so they know what's up (they have been fantastic with me during this issue, kudos to TP Abuse)..

And then also email:
rbl@abuse-att.net
abuse_rbl@abuse-att.net

With a copy of the email error and your server IP listed in the error.. And also a little tidbit about how you believe their listing is in error, etc. Also be sure to mention if you are being blocked by any of their affiliates like SBC etc.

Also fill out their form at:
http://worldnet.att.net/general-info/bls_i...lock_admin.html

At first you may get a "You are not Blocked" email from att. But be persistent, and reply with copies of the error message until they unblock.

The above combo did it for me. So hopefully it shall work for you guys/gals too.

It is a shame though, that they (ATT) make us jump thru such hoops when we shouldn't have been listed in the first place.

We are also having problems with our email server Exchange 2003 Sp2 contacting ATT.NET and SBCGlobal.net email addresses. I have sent at least a dozen emails to all the abuse emails with all of them to get this resolved and have yet to see this happen. We are getting the blocked emails as well. ATT.net is working again, but sbcglobal.net is still blocking our emails. I have been on the phone with AT&T for 2.5 hours trying to resolve this with no luck. They always want to toss the blame back at our systems when it isn't. They keep saying we are not on any black/block list.

Anyways, I will try to keep everyone posted on our status, but I did a internet search and found these posts that reallly point to a ATT problem. This all started last Friday it seems.

I'm not affiliated with TP, I googled up this thread after getting blocked.
GET THIS-its on a brand new AT&T circuit with brand newly AT&T issued ip addresses.

I've been sending with my old bellsouth circuit and ips for years, cut to AT&T last night.
Reverse DNS shows good at dnsstuff.
Who knows.

I had issues with Bellsouth about two years ago and the issues lasted almost 2 months.
That was two months of my time wasted on the phone too.
I never really did figure out if it was Bellsouth or ThePlanet (or both).
All I know is one day it started working.

Good luck talking to Bellsouth.
From what I figured out, their understanding of a mail server is about the same as a 2-year old's.

Just started having the same issues within the last few days.

I sent emails to the email addresses above but none of the links listed above worked.

I got a response from abuse_rbl@abuse-att.net, but even the link in the email http://www.att.net/general-info/rblinquiry.html doesn't work.

Hopefully someone will actually respond vs. an automated response.

Started seeing this issue here as well.
My servers are in dallas so not affected by the H1 rdns issue at all.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

removed-for-forum-post@sbcglobal.net
SMTP error from remote mail server after MAIL FROM:<mydomain removed for forum post>:
host sbcmx7.prodigy.net [207.115.37.21]: 553 5.3.0 nlpi090 - m5LHch27002255, DNSBL:521< 70.86.xxx.yyy>_is_blocked.__For_information_see_http://att.net/blocks

Have filled out the form so hopefully if enough of us contact att/sbcglobal they will resolve it for us.