Port 25 blocked on my Static IP address since june 1st?!?

I'm seeing the problem on regular DSL in the Richmond, CA area. Using tcptraceroute (TCP version of traceroute that can send SYN packets to a specific port), my port 587 packets go right through from my company gateway to my personal outside mail server (running on a Linode VM). Port 25 packets get blocked on the first hope after my DSL modem. The local gateway in the modem responds but the next hop doesn't. So this looks to be a setting in the firewall in the DSLAM.

BTW, I got MUCH better tech support response yesterday when I called in at 877-353-3668. Almost no wait on the phone queue and the tech was able to quickly get a ticket entered and escalated. Still waiting for an update. Right now we're still blocked. 

As a temporary workaround, I'm using my $5/month Linode VM server as an email gateway. It's set to relay all mail only from my blocked IP and accepts connections on port 587. Linode bills by the hour so you could set this up without too much difficulty and (hopefully) pay pennies while AT&T sorts this out. Yeah, it (Edited per community guidelines) that we have to do this, but at least it's a way to keep the business operating until they do. 

In addition to this forum, I had been working with some AT&T tech's on a different one.

They have successfully removed my block and indicated they are working on changes that will address things system wide.

They also suggest a reboot on the modem to force a new login session on the PPPOE.

I am able to send e-mails.

Congratulations!

Is your service on DSL or UVERSE?

Still blocked on my DSL lines

Thanks for the update!  I just rebooted our DSL modem (business account, static IP), and port 25 became unblocked.  Outgoing emails finally flowing out again.  🙂 

Previously we also had the same blocked port 25 issue since last Thursday.. what a major inconvenience!

My SMTP port is also open now.  I haven't receive any response back from AT&T regarding the case numbers yet.  I just saw @DyerUser 's post here, disconnected my AT&T business DSL modem's PPPOE connection, waited for 20 seconds and reconnected and the port is now open again. 

Can confirm from Southern California that resetting the router to initiate a new session has returned port 25 to normal behavior. Email flow is working again now that AT&T has finally corrected their mistake. Thanks everyone in this thread, especially @DyerUser and @JefferMC. Your efforts are well appreciated.

It is beyond frustrating however that it took since Thursday night for AT&T to correct this. The abysmal customer service I received over the phone and the extreme rudeness of the so called supervisor I spoke with has left a lasting impression of what to expect from AT&Ts business model. Customer service departments are so fractured and disconnected from each other it is literally by all definitions not functional. It truly took forum members (not paid att employees) to get to the bottom of this and push the solution. It makes no sense that parts of the fees we pay goes to pay these phone techs to rudely tell us we don't know what we are talking about because we are saying things they aren't trained in.

@BrewtisSD I'd agree with your disappointed sentiment about the fractured nature of AT&T and the inability of the front-line support to understand the type of Business/Static IP issues like this.  Not to mention the timeframe.

However, I'd also like to point out that it was some above and beyond action by dedicated AT&T personnel who also put in time on forums like this that actually cut through whatever Gordian Knot was going on internally to cause it.  We just raised enough of a stink to get some attention. 

I can remember when I first got DSL, many, many years ago, the technical level of support available from AT&T was excellent.  Some of those people are still around, and I'm glad we can at least get their attention.

It is a shame, though, that we cannot even get the issue raised via standard support channels to get action.

Working again in Richmond, CA after a modem reboot.