AT&T Southeast → Re: Email anomaly

I knew you were going to ask that.

In past email discussions regarding the email servers, I mentioned that I was never able to get an inbound connection with the Yahoo/ATT servers pop.att.yahoo.com...no matter how I tried to configure it. mail.bellsouth.net port 110 no security for inbound always works, and I suspect it is rerouted to ATT.

Outbound is set for smtp.att.yahoo.com

Crazy, but what else is new?

One of your inbound servers is in an Ameritech(SBC) /22 block of IP addresses ...

C:\util>nslookup mail.bellsouth.net
Server:  homeportal
Address:  192.168.42.1
 
Non-authoritative answer:
Name:    mail.bellsouth.net
Addresses:  204.127.217.17
          207.115.11.17
 

... while outbound is to a Yahoo! block:

C:\util>nslookup smtp.att.yahoo.com
Server:  homeportal
Address:  192.168.42.1
 
Non-authoritative answer:
Name:    smtp1.sbc.mail.am0.yahoodns.net
Addresses:  98.138.31.74
          98.139.221.42
          67.195.15.66
          68.142.198.11
Aliases:  smtp.att.yahoo.com
          smtp-sbc.mail.yahoo.com
 

An old SBC SMTP server I used to use is in the same Ameritech /22 block:

C:\util>nslookup smtpauth.sbcglobal.net
Server:  homeportal
Address:  192.168.42.1
 
Non-authoritative answer:
Name:    smtpauth.sbcglobal.net
Address:  207.115.36.27
 

I can't guaranty it will work better (or even at all), but give, 'smtpauth.sbcglobal.net' a try. Port 25 should work, but I used to use port 587. Authentication is required; and the user name would be your complete email address.

Definitely answers to Telnet on port 25:

C:\util>telnet smtpauth.sbcglobal.net 25
Connecting To smtpauth.sbcglobal.net...
 
220 nlpi176.prodigy.net ESMTP Sendmail 8.14.4 smptauth/8.14.4; Tue, 18 Dec 2012
12:48:14 -0600
quit
221 2.0.0 nlpi176.prodigy.net closing connection
 
Connection to host lost.
 

Hey Burris,

Sent you a PM a while back - did you see it?

Thanks.

ttfg....

I'm sorry but I did not see it.

Anyway, I have given up with these 3347's as for me, they don't make sense for residential. More important, even though they can be set up as bridged, I don't care for the way it works. Just not stable for me in that mode.
Besides, in order to realy get into the unit, I think you have to telnet in. I've been through it, but why? Sure, it has plenty of stuff inside, but I don't need any more than I have now with my 2210-02-1006 that has been running bridged for years with no problems whatsoever.

Sorry I couldn't help..

No problem, I used to have the 2210, but it couldn't keep up after I was able to get 6meg, so I tried the 3347 and it's been great ever since. I even bought a backup when they were being sold for like $15, new and in the box (I think that's when I last talked to you, to let you know, lol). So far so good.

Be well, and best for the holidays.

Miss the fun in the usenet group.

We did have fun in those days, even though the newsgroup was a work in progress....as was the DSL then.

If the 2210 you had was before a certain serial number awhile back, it was one of those that kept overheating and burned out. I originally had a couple of those and they replaced them. As I said I had no problem since, except when AT&T needs to crank up their roto-rooter to clean their pipes.
Are you using your 3347 bundled or just as a bridge. I did try mine bundled and it did work, but I have my router loaded with DD-WRT and didn't want stacked routers if I went bridged with the 3347.

Happy Holidays to you as well..