US Telco Support > AT&T > AT&T West > [General] Using my own SMTP server with AT&T business DSL possib

[General] Using my own SMTP server with AT&T business DSL possib

Re: [General] Using my own SMTP server with AT&T business DSL po

So I guess I'm using mail.nvbell.net until it works no more at this point. We're talking up to several hundred emails a day rolling through.

It 'appears' that AT&T *is* blocking traffic on port 25 unless it is their own SMTP server so I'm not sure where that leaves me on running my own SMTP server. Surely AT&T has some workaround for Business DSL users?

It used to be that anyone could request port 25 to be unblocked, in fact, there was a form on the AT&T Help site that had this option up until a few months ago.

Recent reports indicate that they've stopped doing this for residential customers but AT&T techs on this forum have said they'll still do it for Business DSL customers if you call in and request it.

As an alternative, why not use port 587? They don't block that port.

reply to technologiq
I don't think a business account should be blocked on port 25. If you have a static IP address, you should check into getting your own hostname on the record for that IP address.

If you have a dynamic IP address, that can be problematic for reaching other gateway mail servers; many don't want to accept SMTP traffic from dynamically assigned IP addresses.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

reply to technologiq
If you call us - we will unblock port 25. By default we block port 25, but will unblock upon request.

reply to technologiq
Interestingly enough - it seems that mail.nvbell.net now requires authentication.

Does AT&T offer any SMTP/Relay for customers?

Your client can't authenticate to the server? I run my own mail server, and I use the MTA's SMTP relay client with 'mail.pacbell.net', which is another alias for 'mail.nvbell.net'. Other than those servers, none that I know of. If you run your own server, you use any of:

• 'mail.nvbell.net'
• 'mail.pacbell.net'
• 'mail.swbell.net'
• 'smtpauth.flash.net'
• 'smtpauth.prodigy.net'
• 'smtpauth.sbcglobal.net'

All are aliases; all require authentication. All may also be accessed using port 587.

If you are using your own domain, does your registrar not offer SMTP relay service?
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

reply to technologiq
Heres my problem.

I have a few devices on my network (Multifunction Scanner & Phone Switch) that do NOT do SSL encryption for SMTP.

We use google apps for our email which REQUIRES SMTP w/ SSL.

Unfortunately the tech that did the install left me with a username XXXXX@att.net and a password that don't work to authenticate against the mail server(s) you posted. Does AT&T require SSL or just authentication?

Thanks! I'm at my wits end with this

reply to technologiq
Is that a new static account that the tech installed?

I guess it doesn't matter if it is static or dynamic, either way if it is a new account, it would be forced into using the ATT-Yahoo servers which require SSL. I think that ATT might have forced Yahoo into using SSL.

Do you have a computer that would be on all the time? Then that computer could serve as an SSL relay proxy for the devices that can't do SSL.

(Firstly - to get out of the way - a *huge* Thank you to NormanS, FroHIke and d_l for all your help)

Yes, I could setup a SSL relay proxy - didn't even think of that... But before I go down that route....

Will AT&T have an issue at all if I just set up a SMTP server on my network? It would only be accessible from my internal network (obviously) and I would ask AT&T to open port 25 for me. We *are* talking hundreds of email a day so I'd rather do it myself than barrage AT&Ts servers.

reply to technologiq
It was my understanding that they don't have a problem with someone on a business account running their own SMTP server on their network and sending out emails. That was the whole purpose of the port 25 unblocking.

All you have to do is get AT&T to do that, however it is done now days. I think there might have been some abuse of the old online form method.

reply to technologiq

I was thinking it is related to the domain. I don't think 'att.net' is recognized by the legacy SBC servers; only the nine legacy SBC domains. OTOH, I don't see why the legacy AT&T Worldnet servers wouldn't recognize the 'att.net' domain. Of course, one is then stuck with the requirements for access; i.e., if SSL is required.

Any SMTP message submission server which uses SMTP AUTH should not care about the originating IP address; but they would require an authorized login name. And the domain is a part of the login name on AT&T message submission servers.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

I don't think the non-SSL Worldnet SMTP servers use SMTP AUTH (they didn't years ago), but instead rely on ACLs. I'm guessing that adding the vast number of IP ranges of the SBCGlobal network to those Worldnet server ACLs was not a high-priority after the AT&T acquisition and has never been done since then. Heck, ATTIS has trouble keeping the ACLs of their own network up-to-date.

So it isn't likely that he could submit email to the non-SSL Worldnet servers with just an @att.net address.

reply to technologiq
Can any of you guys remove the port 25 block for me? I can submit the IP's I'm using at both locations.

Thanks!

reply to technologiq
PM your email ID (that you registered with AT&T at time of install). We block by the email ID (att.net,pacbell.net, sbcglobal.net etc) not by the IPs.