Error Retrieving E-Mail

[Guest]

Hello --

I use Outlook 2003, and am receiving this message when I try to download my
e-mail:

Task 'pop.sbcglobal.yahoo.com - Receiving' reported error (0x80042110) :
'Your POP3 server is providing inconsistent information. The number of
messages returned by the STAT command does not match the number of items
returned by the UIDL or LIST commands. Contact your POP3 or Internet service
provider.'

I have communicated with SBC Yahoo, and their first solution (so far) was to
delete my profile and create a new one. I did that, and it did not work. I
am still working on this with SBC Yahoo, but wanted to see if any of you had
any ideas on what was causing this problem.

Thanks!

Tom Mighell

 

[Guest]

I would want to turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and post
the OPMLog.log file after you get this error, so we can see what Outlook is
complaining about.

 

[Vanguard]

Hello --

I use Outlook 2003, and am receiving this message when I try to download
my
e-mail:

Task 'pop.sbcglobal.yahoo.com - Receiving' reported error (0x80042110) :
'Your POP3 server is providing inconsistent information. The number of
messages returned by the STAT command does not match the number of items
returned by the UIDL or LIST commands. Contact your POP3 or Internet
service
provider.'

I have communicated with SBC Yahoo, and their first solution (so far) was
to
delete my profile and create a new one. I did that, and it did not work.
I
am still working on this with SBC Yahoo, but wanted to see if any of you
had
any ideas on what was causing this problem.

Other users have been reporting similar problems. Their mail server is
****ed up. LIST and UIDL commands do not provide an aggregate total of the
number of non-deleted mail items and their size. They simply *list* the
mail items. The STAT command only gives the aggregate number of mail items
and their aggregate size. I don't know why Outlook bothers to send the STAT
command since obviously it already sends the UIDL command and LIST commands
and could simply total up the number of items and their sizes to get
aggregate counts. Could be Outlook is using the STAT command as a
double-check but Yahoo's mail server is screwed up. All three of those
commands should *NOT* included delete-marked items. You'll have to turn on
logging in Outlook to see what their server is returning when Outlook sends
those commands. However, you can't do anything to fix their server other
than report their screwup to them.

 

[Guest]

Okay, here's what the log says:

2005.12.16 17:37:15 <<<< Logging Started (level is LTF_TRACE) >>>>
2005.12.16 17:37:15 pop.sbcglobal.yahoo.com: Synch operation started (flags
= 00000001)
2005.12.16 17:37:15 pop.sbcglobal.yahoo.com: UploadItems: 0 messages to send
2005.12.16 17:37:15 pop.sbcglobal.yahoo.com: Synch operation completed
2005.12.16 17:37:15 pop.sbcglobal.yahoo.com: Synch operation started (flags
= 00000030)
2005.12.16 17:37:15 pop.sbcglobal.yahoo.com: DoPOPDownload(flags = 00000030,
max msg = ffffffff): full items
2005.12.16 17:37:15 POP3 (pop.sbcglobal.yahoo.com): Begin execution
2005.12.16 17:37:15 POP3 (pop.sbcglobal.yahoo.com): ========= Initial blob
=========
2005.12.16 17:37:15 POP3 (pop.sbcglobal.yahoo.com):
===================================
2005.12.16 17:37:15 POP3 (pop.sbcglobal.yahoo.com): Port: 110, Secure: no,
SPA: no
2005.12.16 17:37:15 POP3 (pop.sbcglobal.yahoo.com): Finding host
2005.12.16 17:37:15 POP3 (pop.sbcglobal.yahoo.com): Connecting to host
2005.12.16 17:37:15 POP3 (pop.sbcglobal.yahoo.com): Connected to host
2005.12.16 17:37:15 POP3 (pop.sbcglobal.yahoo.com): <rx> +OK hello from
popgate(2.33.3) [ISafe POP3 Proxy]
2005.12.16 17:37:15 POP3 (pop.sbcglobal.yahoo.com): Authorizing to server
2005.12.16 17:37:15 POP3 (pop.sbcglobal.yahoo.com): [tx] USER
(e-mail address removed)
2005.12.16 17:37:15 POP3 (pop.sbcglobal.yahoo.com): <rx> +OK password
required.
2005.12.16 17:37:15 POP3 (pop.sbcglobal.yahoo.com): [tx] PASS *****
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> +OK maildrop ready,
23 messages (329958 octets) (331650 2147483648)
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): Authorized to host
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): Connected to host
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): [tx] STAT
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> +OK 23 329958
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): [tx] UIDL
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> +OK 23 messages
(329958 octets)
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 1
ef0ad3edcf0401314a447eaa32248e21
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 2
07903e1c962e95bdbabe790c8a0454fc
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 3
42a80093d7709f39224f7ed00c590643
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 4
14da8272f566759df2f78fd23b70ff40
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 5
86e66a77e1a6ae7659edcfcc193a5a52
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 6
0f1ec19325e6702887456eda32ec6515
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 7
b74540bc13d3706999f70a3df0b74057
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 8
6744a6279d732bf7ef4704708095547e
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 9
19e72e36834eb149e1dab1fa5149e448
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 10
9eee6c26347d924dc7443e408e4fd998
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 11
d32e6b8bd8110682018a2fc3bd2e424c
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 12
2acf7e7b8bdb167447e427a870d81176
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 13
6f421965f9864dc5a93afcedb96e1046
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 14
438dd55507502f1dbf92af1ed8419f67
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 15
697ab32d4a8cda9f18d53385a290d0fd
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 16
be768c694708d39f848d1d1f20403a7f
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 17
d52857fc4d9f7361d138fb21c650361a
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 18
f3f343f753f62193e64d06d01216cb21
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 19
35d60846d8b277b0b3eb5741120ba96c
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 20
c57540b69607acf0557536a5575ff6e7
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 21
1171599498854feb9bd29ec83e05ebb6
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 22
980995205b90ff6881b87b0bdd3eba3c
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> .
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): [tx] LIST
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> +OK 22 messages
(329958 octets)
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 1 8801
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 2 7149
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 3 5046
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 4 30256
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 5 18193
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 6 2797
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 7 2854
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 8 1859
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 9 7626
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 10 32073
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 11 21004
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 12 4582
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 13 15819
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 14 18481
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 15 14945
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 16 18578
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 17 74107
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 18 2959
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 19 1471
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 20 3823
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 21 10241
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> 22 7387
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): <rx> .
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): ==== Comparing server
and local blobs ====
2005.12.16 17:37:16 POP3 (pop.sbcglobal.yahoo.com): End execution
2005.12.16 17:37:16 pop.sbcglobal.yahoo.com: ReportStatus: RSF_COMPLETED, hr
= 0x80042110
2005.12.16 17:37:16 pop.sbcglobal.yahoo.com: Synch operation completed
2005.12.16 17:37:31 pop.sbcglobal.yahoo.com: Synch operation started (flags
= 00000001)
2005.12.16 17:37:31 pop.sbcglobal.yahoo.com: UploadItems: 0 messages to send
2005.12.16 17:37:31 pop.sbcglobal.yahoo.com: Synch operation completed
2005.12.16 17:37:31 pop.sbcglobal.yahoo.com: Synch operation started (flags
= 00000030)
2005.12.16 17:37:31 pop.sbcglobal.yahoo.com: DoPOPDownload(flags = 00000030,
max msg = ffffffff): full items

FYI -- the problem has not resolved, and SBC Yahoo (not surprisingly) has
not responded to my latest e-mail. Any suggestions?

Tom Mighell

 

[Vanguard]

From your log output:

[tx] STAT
<rx> +OK 23 329958

So the mail server is reporting there are 23 non-deleted items in the
mailbox with an aggregate size of 329,958 bytes (octets).

[tx] UIDL
<rx> +OK 23 messages

Okay, looks like it is the same as reported by the STAT command ... except
then go count the number of returned items. Only items 1 to 22 are listed.
So STAT says there are 23 messages and so does the "status" returned by UIDL
but then UIDL only lists 22 messages.

[tx] LIST
<rx> +OK 22 messages

So the LIST command says there are 22 messages. This is different than the
23 reported by STAT. This is different than the status line returned by
UIDL but matches how many mails are actually listed by STAT and LIST.

So, yeah, your mail provider is screwing up what their server is returning
from the STAT, UIDL, and LIST commands. You can't do anything about their
****up. You will have to report the problem to them and they will have to
fix the problem. It is Yahoo's screwup, not Outlook's. Report the problem
to them and wait until whenever they fix their mail server.