Possible Bug - Outlook not logging out via POP

E

epiphani

For lack of a better forum to post this in.. sorry if this is the incorrect
location.

Here's the short version - in certain cases, we can reproducably see
Outlook 2003 (11.8010.8036) SP2 failing to close a session with a quit
command, and as a result repeatedly downloading messages through POP3.

Here's the specifics of the case:

We have multiple access methods to our email platform. One of those
methods leaves messages stored on the server in a flagged-for-deletion
state. This isnt common, however it does happen.

As a result, if the user accesses the mailbox through POP, we provide a
list/uidl/stat that treats the message as flagged for deletion within the
POP session. The STAT does not include it in its count; the LIST and UIDL
skip that record number.

When Outlook POPs, it seems to follow this ok, skipping the missing
message in its RETR list, but it stops one short of the last message and
then disconnects without sending a QUIT. This results is nothing being
cleaned from the mailbox, and every subsequent POP will download all the
messages again.

Here is a breakdown of what I am seeing in a session with Outlook:

<connect>
Server: +OK [Banner]
Client: USER [[email protected]]
Server: +OK
Client: PASS [pass]
Server: +OK
Client: STAT
Server: +OK 10 1536748
Client: UIDL
Server: +OK
Server: 1 1156343126.25390.mail1,S=5354
Server: 2 1157049567.1842.mail1,S=1399
Server: 3 1157049597.1855.mail1,S=2065
Server: 5 1157134725.9242.mail1,S=2169
Server: 6 1157142324.10202.mail1,S=1074
Server: 7 1158088990.15493.mail1,S=34153
Server: 8 1158088990.15495.mail1,S=957
Server: 9 1158089181.15524.mail1,S=14848
Server: 10 1158089296.15536.mail1,S=2596
Server: 11 1158090132.15644.mail1,S=1261
Server: .
Client: LIST
Server: +OK
Server: 1 5455
Server: <... see above, except in LIST format>
Server: 11 1359
Server: .
(For the following section, I'll skip the server responces)
Client: RETR 1
Client: RETR 2
Client: RETR 3
Client: RETR 5
Client: RETR 6
Client: RETR 7
Client: RETR 8
Client: RETR 9
Client: RETR 10
<Disconnect>

Does this make sense - do you need any more information? Am I looking at
a Outlook bug here? I can code around it, but I thought I should make
sure my diagnosis is correct.

Either way, thanks for your time.


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...1db3f1d31&dg=microsoft.public.outlook.general
 
E

epiphani

Sorry - I should reflag this as a general question - how can i do this?

epiphani said:
For lack of a better forum to post this in.. sorry if this is the incorrect
location.

Here's the short version - in certain cases, we can reproducably see
Outlook 2003 (11.8010.8036) SP2 failing to close a session with a quit
command, and as a result repeatedly downloading messages through POP3.

Here's the specifics of the case:

We have multiple access methods to our email platform. One of those
methods leaves messages stored on the server in a flagged-for-deletion
state. This isnt common, however it does happen.

As a result, if the user accesses the mailbox through POP, we provide a
list/uidl/stat that treats the message as flagged for deletion within the
POP session. The STAT does not include it in its count; the LIST and UIDL
skip that record number.

When Outlook POPs, it seems to follow this ok, skipping the missing
message in its RETR list, but it stops one short of the last message and
then disconnects without sending a QUIT. This results is nothing being
cleaned from the mailbox, and every subsequent POP will download all the
messages again.

Here is a breakdown of what I am seeing in a session with Outlook:

<connect>
Server: +OK [Banner]
Client: USER [[email protected]]
Server: +OK
Client: PASS [pass]
Server: +OK
Client: STAT
Server: +OK 10 1536748
Client: UIDL
Server: +OK
Server: 1 1156343126.25390.mail1,S=5354
Server: 2 1157049567.1842.mail1,S=1399
Server: 3 1157049597.1855.mail1,S=2065
Server: 5 1157134725.9242.mail1,S=2169
Server: 6 1157142324.10202.mail1,S=1074
Server: 7 1158088990.15493.mail1,S=34153
Server: 8 1158088990.15495.mail1,S=957
Server: 9 1158089181.15524.mail1,S=14848
Server: 10 1158089296.15536.mail1,S=2596
Server: 11 1158090132.15644.mail1,S=1261
Server: .
Client: LIST
Server: +OK
Server: 1 5455
Server: <... see above, except in LIST format>
Server: 11 1359
Server: .
(For the following section, I'll skip the server responces)
Client: RETR 1
Client: RETR 2
Client: RETR 3
Client: RETR 5
Client: RETR 6
Client: RETR 7
Client: RETR 8
Client: RETR 9
Client: RETR 10
<Disconnect>

Does this make sense - do you need any more information? Am I looking at
a Outlook bug here? I can code around it, but I thought I should make
sure my diagnosis is correct.

Either way, thanks for your time.


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...1db3f1d31&dg=microsoft.public.outlook.general
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top