Passing Through
@sbcglobal.net | reply to John_E
Re: Email Problem
On sending attempts I am getting notices that the address I am using is not valid. A 533 error out of Yahoo's system.
Then I turn around and look a couple minutes later and the email is finally sent. |
|
John_E
Premium
join:2004-02-03
Florissant, MO | reply to ReneeRC
Yep, I thought it was fixed, too. Wrong! Have had 3 incidents like Renee's (incoming only) since 2:00PM CDT.
John in STL |
|
ReneeRC
join:2002-08-08
Ballwin, MO
1 edit | reply to Traxless
Traxless, I wasn't having any problems with my SMTP server/sending emails because my user email name is the same, etc, as you said. What was happening to me and others, was that, when my Email client would try to Retrieve email from the server, the CONNECTION to the server would take place, but then the server would stall, and a message saying "the server has timed out" would appear. This didn't happen often, but it did happen.
I just experienced another "timed out" mishap so perhaps this thing isn't quite over with yet.  |
|
Traxless
Premium
join:2005-02-16
USA
 ·AT&T Southwest
 ·Cbeyond
| reply to ReneeRC
Is the User email name exactly the same as the incoming and outgoing login name? Secondly, are you using a SMTP server OTHER than the AT&T server? Third ... what are the Server Port settings?
We have had this same issue on several computers and all issues resolved when we reviewed these three (3) areas.
--
I tried being reasonable, I didn't like it. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to ReneeRC
said by ReneeRC  :Is anyone who was having "timed out" problems still having them? I didn't have any yesterday that I noticed, and so far there haven't been any this morning. Hope it's fixed. I never saw them. Checked my MTA logs, and only saw about 2 POP3 errors for every 24 POP3 polls.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
ReneeRC
join:2002-08-08
Ballwin, MO | reply to ReneeRC
Is anyone who was having "timed out" problems still having them? I didn't have any yesterday that I noticed, and so far there haven't been any this morning. Hope it's fixed. |
|
ReneeRC
join:2002-08-08
Ballwin, MO | reply to ReneeRC
David, are you wanting me to post all the logs from this thread into Direct as well or is the link to this thread that I posted in Direct good enough?
Lemme know.  |
|
David
No,there is another.
Premium,VIP
join:2002-05-30
Granite City, IL
clubs:
 ·DIRECTV
·magicjack.com
·AT&T Midwest
| reply to katarina
hey guys & gals,
With the e-mail errors and time outs you are getting can you post these in the direct forum?
Just need the following
• The ID's affected
• the errors that each id is getting, if say ID-a is getting a different error than id-b, that would be a difference.
• Does webmail work?: Note: a simple verify and yes or no will work here.
• E-mail client you are using
• DSL number if you have one or account number, for Uverse the BAN (Billing Account Number) will be it.
Then in a direct post please select [e-mail prob] and post away.
Thanks
David
--
If you have a topic in the direct forum please reply to it or a post of mine, I get a notification when you do this.
Koetting Ford, Granite City, illinois... YOU'RE FIRED!!
|
|
katarina
join:2003-09-07
Houston, TX
| reply to ReneeRC
I've been having email access problems for the past several days as well. This is what I get:
The connection to the server has failed. Account: 'SBC Global', Server: 'pop.att.yahoo.com', Protocol: POP3, Port: 995, Secure(SSL): Yes, Socket Error: 10060, Error Number: 0x800CCC0E
I'm also getting the annoying email about using unsecure settings again. I know the settings are right, but it is really aggravating for them to send out an email specifically stating that they noticed that you are using unsecure settings. |
|
ReneeRC
join:2002-08-08
Ballwin, MO
| reply to ReneeRC
Thanks d_l. Yep, like you said, more of the same stuff that happens every so often when the servers are overloaded. Normally, I'm able to get my mail with no problems whatsoever, and on those occasions when I do have problems I notice that others are having the same ones. And we're all using different email software so that pretty much says it all right there, for me. |
|
d_l
Barsoom
Premium,MVM
join:2002-12-08
Reno, NV
| reply to ReneeRC
This may not be your problem, but I think some of the Yahoo email servers are overloaded again. This has happened periodically in the last few years. I don't know if they load balance the servers, but it seems that they should.
Sometimes to fix these problems all you need is the IP address of an unloaded server. Then you would substitute that IP address for pop.att.yahoo.com or smtp.att.yahoo.com in your email client. |
|
ReneeRC
join:2002-08-08
Ballwin, MO
| reply to ReneeRC
Btw, today for the 1st time, I received one of those Warning email notices that says I'm accessing email using non-secure settings in my email software. They asked me to enable SSL, and I've already done so. I posted about this in another thread, but thought I ought to mention it here as well.
I'm glad to see the spam emails gone, but sheesh! These email problems needed to be fixed asap, please. |
|
ReneeRC
join:2002-08-08
Ballwin, MO
| reply to ReneeRC
And again, another time out:
CONNECTED Mar 30 10:31:53[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e7d700 -- thread:0x4e35910
CONNECTED Mar 30 10:33:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e9c160 -- thread:0x4e58670
READ Mar 30 10:33:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e9c160 -- thread:0x4e58670
+OK hello from popgate 2.38.7 on pop106.sbc.mail.mud.yahoo.com
WROTE Mar 30 10:33:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e9c160 -- thread:0x4e58670
USER myaccount@swbell.net
========================>
And again....
CONNECTED Mar 30 10:41:44[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e97650 -- thread:0x4e96540
CONNECTED Mar 30 10:45:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4ea1020 -- thread:0x4e2f070
CONNECTED Mar 30 10:47:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e8f7f0 -- thread:0x4e213c0
READ Mar 30 10:47:43[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e8f7f0 -- thread:0x4e213c0
+OK hello from popgate 2.38.7 on pop101.sbc.mail.mud.yahoo.com
WROTE Mar 30 10:47:43[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e8f7f0 -- thread:0x4e213c0
USER myaccount@swbell.net
========================>
And here we see it happening again:
CONNECTED Mar 30 11:01:39[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4eaf700 -- thread:0x4eaea90
CONNECTED Mar 30 11:02:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e8a5d0 -- thread:0x4e54940
CONNECTED Mar 30 11:04:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e52040 -- thread:0x4a13060
AND SO ON.... |
|
ReneeRC
join:2002-08-08
Ballwin, MO
| reply to ReneeRC
Okay, this is still happening. I am NOT having any problems SENDING emails, only Receiving them. I am not getting any "error" messages either, only timing out. Here are some more examples from today. You can see below that the first time my email program connected it ended up timing out.
CONNECTED Mar 30 09:50:56[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e688f0 -- thread:0x4e4a190
CONNECTED Mar 30 09:52:41[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x3542320 -- thread:0x4e4ec90
READ Mar 30 09:52:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x3542320 -- thread:0x4e4ec90
+OK hello from popgate 2.38.7 on pop111.sbc.mail.mud.yahoo.com
WROTE Mar 30 09:52:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x3542320 -- thread:0x4e4ec90
USER myaccount@swbell.net
READ Mar 30 09:52:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x3542320 -- thread:0x4e4ec90
+OK password required.
WROTE Mar 30 09:52:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x3542320 -- thread:0x4e4ec90
PASS ******
READ Mar 30 09:52:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x3542320 -- thread:0x4e4ec90
+OK maildrop ready, 0 messages (0 octets) (0 3702259712)
WROTE Mar 30 09:52:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x3542320 -- thread:0x4e4ec90
STAT
READ Mar 30 09:52:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x3542320 -- thread:0x4e4ec90
+OK 0 0
WROTE Mar 30 09:52:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x3542320 -- thread:0x4e4ec90
QUIT
READ Mar 30 09:52:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x3542320 -- thread:0x4e4ec90
+OK server signing off.
==========================>
Here, you can see that it took several "tries" before the server stopped timing out, and allowed my email program to retrieve my emails:
CONNECTED Mar 30 09:56:44[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e504f0 -- thread:0x3521590
CONNECTED Mar 30 09:59:02[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4e52840 -- thread:0x35ed0a0
CONNECTED Mar 30 10:00:44[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x3502080 -- thread:0x35ff600
CONNECTED Mar 30 10:02:41[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x354dee0 -- thread:0x4e90120
READ Mar 30 10:02:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x354dee0 -- thread:0x4e90120
+OK hello from popgate 2.38.7 on pop109.sbc.mail.mud.yahoo.com
WROTE Mar 30 10:02:42[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x354dee0 -- thread:0x4e90120
USER myaccount@swbell.net
AND SO ON... |
|
stardotstar
join:2000-12-13
Barker, TX | reply to ReneeRC
I'm not getting those but others. SOmone needs to WAKE up at ATT and get Yahoo to fix this! |
|
ReneeRC
join:2002-08-08
Ballwin, MO
1 edit | reply to ReneeRC
Here is another example from my log. I was able to retrieve my email just fine this time, but I notice that it always shows me as having 1 email on the server even though I don't.
===== Saturday, March 29, 2008 6:46:20 PM US/Central =====
CONNECTED Mar 29 18:51:10[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x353ff70 -- thread:0x3521a90
READ Mar 29 18:51:10[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x353ff70 -- thread:0x3521a90
+OK hello from popgate 2.38.7 on pop105.sbc.mail.mud.yahoo.com
WROTE Mar 29 18:51:10[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x353ff70 -- thread:0x3521a90
USER myaccount@swbell.net
READ Mar 29 18:51:10[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x353ff70 -- thread:0x3521a90
+OK password required.
WROTE Mar 29 18:51:10[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x353ff70 -- thread:0x3521a90
PASS ******
READ Mar 29 18:51:10[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x353ff70 -- thread:0x3521a90
+OK maildrop ready, 1 message (25337 octets) (25337 3699376128)
WROTE Mar 29 18:51:10[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x353ff70 -- thread:0x3521a90
STAT
READ Mar 29 18:51:10[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x353ff70 -- thread:0x3521a90
+OK 1 25337
WROTE Mar 29 18:51:10[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x353ff70 -- thread:0x3521a90
UIDL
READ Mar 29 18:51:10[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x353ff70 -- thread:0x3521a90
+OK 1 message (25337 octets)
1 ACJl/NgAAFK3R8hI7QD/1mk4pI4
.
WROTE Mar 29 18:51:10[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x353ff70 -- thread:0x3521a90
QUIT
READ Mar 29 18:51:10[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x353ff70 -- thread:0x3521a90
+OK server signing off.
EDITED TO ADD that the phantom email is now gone. |
|
ReneeRC
join:2002-08-08
Ballwin, MO
|  For about the last 7 to 10 days I've been experiencing email problems. For the most part, my Mail program gets the mail (POP) from the server with no problems. Then, out of the blue, my Mail program will try to access the server, and it eventually times out. I don't get any pop up messages or anything. I just don't get my mail. Apparently, I'm not the only one with this problem:
»Slow access to email via pop
Okay, here is an example (from my log) of what happens when this happens to me. I try to get my mail and:
===== Saturday, March 29, 2008 4:50:53 PM US/Central =====
CONNECTED Mar 29 16:50:59[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x35cdf50 -- thread:0x35c99b0
And I connect to the server. Then, it just stays like this for a while until my email program quits trying to retrieve my mail. If I check to see WHY my email finally quit trying it gives me this message:
**There may be a problem with the mail server or network. Check the settings for account "POP:myinfohere@...swbell.net" or try again.
The server error encountered was: The connection to the server "pop.att.yahoo.com" timed out.**
I'll post an example of what happened (from my log) below. Notice that my Mail program connected to the server, never did anything else, and then when I tried to get my mail again, it did just fine:
===== Saturday, March 29, 2008 4:50:53 PM US/Central =====
CONNECTED Mar 29 16:50:59[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x35cdf50 -- thread:0x35c99b0
CONNECTED Mar 29 16:55:07[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4f79990 -- thread:0x4f793a0
READ Mar 29 16:55:08[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4f79990 -- thread:0x4f793a0+OK hello from popgate 2.38.7 on pop106.sbc.mail.mud.yahoo.com
WROTE Mar 29 16:55:08[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4f79990 -- thread:0x4f793a0USER myaccount@swbell.net
READ Mar 29 16:55:08[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4f79990 -- thread:0x4f793a0+OK password required.
WROTE Mar 29 16:55:08[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4f79990 -- thread:0x4f793a0PASS ******
READ Mar 29 16:55:08[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4f79990 -- thread:0x4f793a0+OK maildrop ready, 1 message (25337 octets) (25337 3699376128)
WROTE Mar 29 16:55:08[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4f79990 -- thread:0x4f793a0STAT
READ Mar 29 16:55:08[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4f79990 -- thread:0x4f793a0+OK 1 25337
WROTE Mar 29 16:55:08[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4f79990 -- thread:0x4f793a0UIDL
READ Mar 29 16:55:08[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4f79990 -- thread:0x4f793a0+OK 1 message (25337 octets)1 ACJl/NgAAFK3R8hI7QD/1mk4pI4.
WROTE Mar 29 16:55:08[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4f79990 -- thread:0x4f793a0QUIT
READ Mar 29 16:55:08[kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x4f79990 -- thread:0x4f793a0+OK server signing off.
BTW, this said I had 1 message, but I didn't receive it. When I went to the server on the web it didn't show a message. I don't know if that matters or not. Thanks for any help with this. |
|
