said by Tier2
Since you are using email client, even though you have the correct email configuration in your Outlook it wont work because you need to be migrated first then you can send/receive with no problem as long as the settings in the OE is correct.
To migrate your account access this site »https://attreg.att.net/PortalMigrationTool/entry.do
now if there is an error call techsupport tier2 to help you out.
Thats simple but sometimes we encounter any error messages that we dont know then AT&T Tier2 will help you.
[/BQUOTE :Inever migrated and my old email client settings still works:
server settings
server name: mail.bellsouth.net port: 110
user name: xxx@bellsouth.net
outgoing server ( smtp)
server name: mail.bellsouth.net port: 25
user name: xxx@bellsouth.net
reply
Tier2 @ 9th Nov 08:25AM:Re: [General] Yahoo email.....That is true to you...
Meaning to say that your email account has not been detected by the system to let you do the "force migration" process and i assume you can still access your web email through www.webmail.bellsouth.net
Even if your account has been migrated to yahoo the POP3 server settings for your old settings will still work.
If you cant send using smtp.att.yahoo.com/465 SSL===
you can use mail.bellsouth.net/25 without SSL and vice versa
If you cant receive using pop.att.yahoo.com/995 SSL===
you can use mail.bellsouth.net/110 without SSL and vice versa
reply
Tier2 @ 9th Nov 08:43AM:Re: [General] Yahoo email.....If you know your username and password log on to
www.mail.yahoo.com
If there is a verification code under the password make sure you type it in and hit sign in, if none click sign in to continue...
It will then redirected you to fill out your informations with security questions etc...
After you successfully migrated you focus with your email client-OE6, Winmail, Macmail and check your email client configuration settings.
Incoming mail server: pop.att.yahoo.com
Outgoing mail server:smtp.att.yahoo.com
Incoming server port number: 995 with SSL
Outgoing server port number: 465 with SSL
Note: if you cant send using smtp.att.yahoo.com, use mail.bellsouth.net with outgoing port num 25 without SSL
if you cant receive using pop.att.yahoo.com, use mail.bellsouth.net with incoming port num 110 without SSL
If there is difficulty for you then call tier2 support for remote access and i guess this would resolve your issue!
reply
NormanS @ 10th Nov 06:37AM:Re: [General] Yahoo email.....said by Tier2 :
Since you are using email client, even though you have the correct email configuration in your Outlook it wont work because you need to be migrated first then you can send/receive with no problem as long as the settings in the OE is correct.
Why do people insist on using "Outlook" and "Outlook Express" interchangeably? They are not interchangeable. "Outlook" is to "Outlook Express" as "grape" is to "grapefruit".
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drumreply
stombujotz @ 10th Nov 09:58AM:Re: [General] Yahoo email.....Have done all this......am now getting this error msg...There may be a problem with the mail server or network. Verify the settings for account “bellsouth.net” or try again.
The server returned the error: The attempt to read data from the server “pop.att.yahoo.com” failed.
reply
NormanS @ 10th Nov 07:46PM:Re: [General] Yahoo email.....You mentioned, "iMac", and "Leopard"; out of curiosity, which email application? (I'm not familiar with Apple products.)
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drumreply
stombujotz @ 12th Nov 09:54PM:Re: [General] Yahoo email..... It is the standard mail program that comes with the Mac OS X...
reply
stombujotz @ 12th Nov 09:57PM:Re: [General] Yahoo email.....These error msgs. do not occur all the time...but they do occur on a daily basis and sometimes I cannot retrieve mail from the bellsouth/ATT/Yahoo server.....they are always the same.....telling me to check my settings....but eventually I am able to get the mail.....but it can take awhile...
reply
Tier2 @ 13th Nov 10:19AM:Re: [General] Yahoo email.....Call us @ 888-321-2375 and ask for tier2 to do remote access in you computer and we'll see what we can do....
diagnose the issue if it is with AT&T yahoo server or your client email.... :)
If this doesn't work you have to download other email client or contact your OEM, try using the web email for the mean time... ;)
Goodluck! :D
reply
wdsnls @ 13th Nov 05:16AM:Re: [General] Yahoo email.....said by stombujotz :
These error msgs. do not occur all the time...but they do occur on a daily basis and sometimes I cannot retrieve mail from the bellsouth/ATT/Yahoo server.....they are always the same.....telling me to check my settings....but eventually I am able to get the mail.....but it can take awhile...
I began having this same problem several weeks ago. I have four accounts and 90% of the time one account will not authenticate. It can be any one of them. If I immediately try to receive that account again it will work.
reply
stombujotz @ 19th Nov 08:59AM:Re: [General] Yahoo email.....You know, I hate to get on my soap box...but to put it bluntly...AT&T sucks....I am now without email totally....using their ATT/Yahoo server...I understand this is a system wide outage.......forget about trying to use online chat.....#39.......we will be with you shortly.....these are all the reasons why I dislike AT&T......I have spent literally months trying to get this straightened out.....what an utter waste of time.......This is getting to be just like Earthlink....terrible tech support.....cant talk with a real person without going thru phone tree for ten minutes....and then you are #39 in the queue.......unreal...gonna have to rethink this ......
reply
mikes60 @ 19th Nov 10:01AM:Re: [General] Yahoo email.....Just got my annual bill from 1and1.com.
$20.87 per year, including my own domain. That's less than $.06 per day.
Stop complaining and take charge of your own email. AT&T will never-ever, get it right.
Quote from Alber Einstein:
"The definition of insanity is doing the same thing over and over again and expecting different results."
--
No good deed goes unpunished.reply
NetFixer @ 19th Nov 03:19PM:Re: [General] Yahoo email.....said by stombujotz :
You know, I hate to get on my soap box...but to put it bluntly...AT&T sucks....I am now without email totally....using their ATT/Yahoo server...I understand this is a system wide outage.......
I don't know who told you that there was a system wide outage, but it is not true. I run my own in-house email server, and it polls a number of external mailboxes every five minutes (including several AT&T accounts) using the fetchmail daemon in order to merge those external accounts into the user's local inbox. I have seen no evidence that there is any kind of system wide outage for AT&T email. The current fetchmail log restarted three days ago (and I am too lazy to extract the older logs from the archive to check further back), and the only "failures" it reports is three authentication failures over those three days (which were caused by a delayed response which disappeared when a retry was done).
FYI, if you are having some sort of problem with the *.att.yahoo.com email servers, you can also still use the old mail.bellsouth.net server. This is not widely publicized because AT&T wants you to use the Yahoo servers, but the servers are mirrored and you can still receive and send using either the *.att.yahoo.com servers or the mail.bellsouth.net server.
The *.isp.att.net servers are also still available for your use:
SMTP: fmailhost.isp.att.net, SSL, port 465
POP3: fpostoffice.isp.att.net, SSL, port 995
EDIT: On second thought, AT&T has been doing some network infrastructure changes that may be effecting some users more than others.
These traceroutes show what I mean:
Tracing route to pop.att.yahoo.com [68.142.206.218]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms dcs-gw1.dcs-net [192.168.10.1]
2 10 ms 10 ms 9 ms 68.216.204.212
3 29 ms 10 ms 9 ms 68.216.204.37
4 12 ms 10 ms 10 ms 65.83.237.110
5 11 ms 9 ms 9 ms 65.83.238.90
6 14 ms 12 ms 10 ms 65.83.238.150
7 30 ms 30 ms 30 ms cr2.nsvtn.ip.att.net [12.123.129.94]
8 30 ms 29 ms 29 ms cr2.attga.ip.att.net [12.122.1.241]
9 29 ms 30 ms 29 ms cr83.dlstx.ip.att.net [12.123.18.109]
10 35 ms 47 ms 48 ms gar8.dlstx.ip.att.net [12.122.139.9]
11 29 ms 30 ms 30 ms 12.86.20.18
12 30 ms 30 ms 29 ms ae2-p110.msr2.mud.yahoo.com [216.115.104.109]
13 29 ms 30 ms 30 ms te-9-1.fab1-a-gdc.mud.yahoo.com [209.191.78.135]
14 30 ms 29 ms 30 ms ten-8-1.bas2.mud.yahoo.com [68.142.193.27]
15 31 ms 30 ms 30 ms pop2.sbc.mail.vip.mud.yahoo.com [68.142.206.218]
Trace Complete.
Tracing route to mail.bellsouth.net [204.127.217.17]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms dcs-gw1.dcs-net [192.168.10.1]
2 10 ms 9 ms 10 ms 68.216.204.65
3 12 ms 11 ms 12 ms 68.216.204.37
4 11 ms 13 ms 11 ms 65.83.237.122
5 12 ms 11 ms 11 ms 65.83.238.104
6 10 ms 15 ms 11 ms 65.83.238.150
7 75 ms 76 ms 76 ms cr1.nsvtn.ip.att.net [12.123.129.54]
8 75 ms 75 ms 74 ms cr1.sl9mo.ip.att.net [12.122.28.62]
9 73 ms 75 ms 74 ms cr2.sffca.ip.att.net [12.122.28.57]
10 75 ms 75 ms 73 ms cr1.sffca.ip.att.net [12.122.3.69]
11 74 ms 74 ms 75 ms 12.83.59.5
12 76 ms 73 ms 74 ms 151.164.38.28
13 74 ms 75 ms 74 ms ded2-p8-0.snfcca.sbcglobal.net [151.164.95.113]
14 77 ms 75 ms 77 ms attsi-2of2-san-francisco-1155380.cust-rtr.pacbell.net [64.172. 39.78]
15 77 ms 76 ms 76 ms 207.115.16.50
16 * * * Request timed out.
17 75 ms 76 ms 76 ms mail.bellsouth.net [204.127.217.17]
Trace Complete.
Tracing route to fpostoffice.isp.att.net [207.115.11.18]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms dcs-gw1.dcs-net [192.168.10.1]
2 10 ms 10 ms 10 ms 68.216.204.65
3 13 ms 10 ms 12 ms 68.216.204.37
4 11 ms 12 ms 10 ms 65.83.237.104
5 11 ms 10 ms 11 ms 12.83.10.122
6 10 ms 13 ms 11 ms 65.83.238.150
7 76 ms 75 ms 74 ms cr1.nsvtn.ip.att.net [12.123.129.38]
8 74 ms 77 ms 74 ms cr1.sl9mo.ip.att.net [12.122.28.62]
9 75 ms 76 ms 77 ms cr2.sffca.ip.att.net [12.122.28.57]
10 75 ms 78 ms 75 ms cr1.sffca.ip.att.net [12.122.3.69]
11 78 ms 74 ms 78 ms 12.83.59.17
12 74 ms 74 ms 146 ms 151.164.38.28
13 75 ms 75 ms 72 ms ded2-p13-0.snfcca.sbcglobal.net [151.164.243.62]
14 79 ms 76 ms 76 ms attsi-1of2-san-francisco-1155377.cust-rtr.pacbell.net [64.172. 39.62]
15 78 ms 76 ms 78 ms 207.115.16.54
16 * * * Request timed out.
17 76 ms 75 ms 77 ms fpostoffice.isp.att.net [207.115.11.18]
Trace Complete.
Interestingly, mail.bellsouth.net and fpostoffice.isp.att.net which used to be hosted in GA and TX respectively, now appear to have been relocated to CA. If some routers have not been properly updated, that could present problems for users of those routers.
--
History does not long entrust the care of freedom to the weak or the timid.
-- Dwight D. Eisenhower
The tree of liberty must be refreshed from time to time with the blood of patriots and tyrants.
-- Thomas Jeffersonreply
scubasteve @ 19th Nov 04:22PM:Re: [General] Yahoo email.....said by stombujotz :
You know, I hate to get on my soap box...but to put it bluntly...AT&T sucks....I am now without email totally....using their ATT/Yahoo server...I understand this is a system wide outage.......
Actually the yahoo email servers were up. You just had to connect to them via webmail for a few hours. I couldn't connect with outlook, but I could with webmail. The issue only lasted a short while here. I didn't bother calling support as it wasn't an issue long enough to warrant that frustrating call.
Everything else was working fine - at least from central Florida
Cheers
Steve
reply
NormanS @ 19th Nov 06:06PM:Re: [General] Yahoo email.....said by stombujotz :
...I understand this is a system wide outage.......
Really. I am in this system:
5 password errors in 369 polling cycles. Damn! This is serious!
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drumreply
stombujotz @ 22nd Nov 08:58PM:Re: [General] Yahoo email.....I should have been more specific...it was a system wide outage for the south florida area.....at least that is what the recording said on the phone......
reply
NormanS @ 22nd Nov 09:56PM:Re: [General] Yahoo email.....Ah. Troubles have also been posted from AT&T Midwest and AT&T Southwest. I don't recall seeing any reported from AT&T West, and only one report from AT&T Northeast. So I figure it is somewhat localized.
Also, not everybody in every region reporting trouble.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drumreply
Thank you for using lo-fi dslreports.com - report bugs
© 99-2009 silver matrix LLC
[General] Yahoo email.....