said by khockin:
Can anyone verify if AT&T Southeast filters outbound port 25?
Specifically I am wondering if you can reach the following 2 IP's on port 25
220.127.116.11 Port 25
18.104.22.168 Port 25
I need to verify this for all AT&T regions
Toward the end of 2002 SBC implemented port 25 blocking across their entire 13-state footprint (West, Southwest, Midwest, and Northeast). It was outbound only, and they provided a web site for unblock requests.
At the end of 2005 the SBC purchase of AT&T went into effect. The corporation was re-branded as AT&T. With the assimilation of AT&T Worldnet, port 25 blocking became more difficult to lift.
In 2006 AT&T acquired Bellsouth, which had long blocked port 25, both outbound and inbound, in their 9-state footprint. As all acquired regions were assimilated, the legacy Bellsouth pattern of blocking port 25 bidirectionally became the new standard.
AT&T now blocks port 25 both ways across their entire 22-state footprint (all regions); though up until I canceled service (April, 2011), legacy customers who had requested unblocking (I was one) apparently still had port 25 access. Because of those legacy unblock requests, responses to your query will vary; but if your client is blocked, that is the current default for new AT&T accounts.
I have heard that unblock requests can still be made through AT&T Direct, but I would strongly recommend exploring alternatives.--
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum