If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
unable to send or receive since att, yahoo upgrade reported error.
At&t insisted I upgrade my email to their shared yahoo servers and now cannot
send or receive, reported error code 0x80042108. I've tried all the posted advise for error code.. AT&T says it's Microsoft's problem.HELP |
#2
|
|||
|
|||
unable to send or receive since att, yahoo upgrade reported error.
"Synjun" wrote in message
... At&t insisted I upgrade my email to their shared yahoo servers and now cannot send or receive, reported error code 0x80042108. I've tried all the posted advise for error code.. AT&T says it's Microsoft's problem.HELP It's impossible for us to tell you what's wrong when you've posted no configuration data. Did you visit Yahoo's help pages and read how to define the account? http://help.yahoo.com/l/us/yahoo/mai...op/pop-06.html -- Brian Tillman [MVP-Outlook] |
#3
|
|||
|
|||
unable to send or receive since att, yahoo upgrade reported er
I have setup my Outlook 2002 to what this At&t support suggest. I use CA
security suite 2009, even turned it off. http://support.att.net/bellsouth/asp...2D3da4f13613b9 "Brian Tillman [MVP - Outlook]" wrote: "Synjun" wrote in message ... At&t insisted I upgrade my email to their shared yahoo servers and now cannot send or receive, reported error code 0x80042108. I've tried all the posted advise for error code.. AT&T says it's Microsoft's problem.HELP It's impossible for us to tell you what's wrong when you've posted no configuration data. Did you visit Yahoo's help pages and read how to define the account? http://help.yahoo.com/l/us/yahoo/mai...op/pop-06.html -- Brian Tillman [MVP-Outlook] |
#4
|
|||
|
|||
unable to send or receive since att, yahoo upgrade reported er
"Synjun" wrote in message
... I have setup my Outlook 2002 to what this At&t support suggest. I use CA security suite 2009, even turned it off. http://support.att.net/bellsouth/asp...2D3da4f13613b9 That didn't get me anywhere that describes Outlok 2002 settings. It just asked me for service type. Try this: http://support.att.net/bellsouth/asp/contentview.asp?ys_audience=uv&ys_service=nhsi&1=1 &sprt_cid=85ca7d0e-ef5b-4a1b-9333-3da4f13613b9&isbrowse=true&portalProvider=Yahoo&Us erType=DSL#Outlook2002 Make sure that you completely uninstall the CA security suite and reinstall it without any email scanning feature. Make sure the firewall allows Outlook to access the Internet. -- Brian Tillman [MVP-Outlook] |
#5
|
|||
|
|||
unable to send or receive since att, yahoo upgrade reported error.
I had the exact same problem - after 50 min on the phone with cust service,
the rep told me it is NOT mandatory to migrate your accounts to the yahoo servers. I have a primary bellsouth account and 5 subaccounts. After hassling and finally getting the primary & one sub account migrated, I am not doing the rest and the rep assured me it would not be a problem. She did tell me, however, that you have to click on the link to migrate and then when you get to the TOS, do NOT accept the terms, but rather click on Reject. That will leave it as before with no changes required to your Outlook. On the accounts that you have already starting migrating which do not work properly on Outlook, make sure that your email address is completely spelled out rather than just the email name ) not (name). That is the problem I was having. Also, the instructions for the Outlook settings have the port numbers in the reverse order that they show up on the account properties. Once I got those two things fixed, things are woking fine. Good luck. I feel your pain big time! "Synjun" wrote: At&t insisted I upgrade my email to their shared yahoo servers and now cannot send or receive, reported error code 0x80042108. I've tried all the posted advise for error code.. AT&T says it's Microsoft's problem.HELP |
Thread Tools | |
Display Modes | |
|
|