Way To Check POP3 Accounts SEQUENTIALLY?

[spdy]

Is there a setting in the registry somewhere that I can set so that
Outlook 2003 checks pop3 accounts sequentially, rather than
concurrently? Reason I ask is I THINK it has something to do with the
INFAMOUS bug I am now working with.

When I start Outlook 2003 and immediately hit Send/Receive SOMETIMES
(most times), Outlook will check one or two email accounts (I've got 3
setup to check) and the third one will just sit there until it times
out. Then, if I close it down and start it back up and hit
send/receive it might work fine. If I close it, start it, and check
email it might check only 1 of the three...or the next time 2 others
of the 3 will work.

It's not a bad server, because all 3 of them will exhibit these
symptoms.

I was thinking that if Outlook would pop the mail from the servers in
a sequential order that it might work better.

Anyone have any input on this?

-- spdy

PS, my laptop (which I am using the SAME pst file on) does NOT exhibit
these symptoms. I can start Outlook and hit send/receive and it will
check all the 3 accounts just fine.

 

[BillR [MVP]]

the methods of checking email were debated prior to release. I think Outlook
will check sequentially for multiple POP3 accounts with the same server
only.

 

[spdy]

Thanks for the reply Bill.

Any idea why I am having these problems with O2K3? I also disabled
all my ad-ins (PGP, and exchange forms or something), and turned off
my filters (3 of them). Nothing helped.

Sometimes it will check mail fine, but most times it will timeout on
one or 2.

Thanks,
spdy

 

[Brian Tillman]

Sometimes it will check mail fine, but most times it will timeout on
one or 2.

Increase your server timeout values on the Advanced tab of the accounts'
properties pages.

 

[Jeff Stephenson [MSFT]]

Could you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and post
the OPMLog.log file (preferably as an attachment) after this happens? I'd
like to see if there's any obvious reason for this happening...

 

[spdy]

I don't have it set to check automatically. I check the mail
manually.

-- spdy

 

[spdy]

Here you go (my OPMLog.log file is attached). This time it checked my
mail from my personal server (on the Internet). It errored on my
Verizon email, and my local mail server (Linux server at my house).
Error was 8004210A. I then quit logging, shut outlook down and
started it back up and it checked mail just fine.

-- spdy

 

[Brian Tillman]

I don't have it set to check automatically. I check the mail
manually.

That's irrelevent. Timeouts can occur with either manual or automatic
send/receives.

 

[spdy]

That's irrelevent. Timeouts can occur with either manual or automatic
send/receives.

Sorry, thought you meant increase the period between checking email.

Anyhoo, increasing my server timeout doesn't help either. It seems to
be some bug in Outlook and my hardware. Although this problem just
started about a month ago. Sometimes it works fine, other times it
hangs. Even canceling the send/receive and trying to send/receive
doesn't do any better. If I shut down outlook then restart sometimes
it will work like it should.

-- spdy

 

[BillR [MVP]]

I suspect this has to do with your Linux Server. You can test by removing
accounts and see if the problem is corrected.

 

[spdy]

Tried removing everything but one server and it did the same thing.
So added a different server and removed the others...same thing. No
matter what server was all by itself it still occurred. This is a
pain too. I hate bugs that never do the same thing twice
(intermittent).

-- spdy

 

[BillR [MVP]]

beats me. see if Jeff has some ideas.

Tried removing everything but one server and it did the same thing.
So added a different server and removed the others...same thing. No
matter what server was all by itself it still occurred. This is a
pain too. I hate bugs that never do the same thing twice
(intermittent).

-- spdy

I suspect this has to do with your Linux Server. You can test by removing
accounts and see if the problem is corrected.

Here you go (my OPMLog.log file is attached). This time it checked my
mail from my personal server (on the Internet). It errored on my
Verizon email, and my local mail server (Linux server at my house).
Error was 8004210A. I then quit logging, shut outlook down and
started it back up and it checked mail just fine.

-- spdy

On Wed, 13 Oct 2004 11:31:45 -0700, "Jeff Stephenson [MSFT]"

Could you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and
post
the OPMLog.log file (preferably as an attachment) after this happens?
I'd
like to see if there's any obvious reason for this happening...

 

[Jeff Stephenson [MSFT]]

Could you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and post
the OPMLog.log file (preferably as an attachment) after you encounter the
problem?

 

[spdy]

Here is the OPMLog.log file. I attached it to a previous message, but
maybe it didn't go through. Trying again.

This time it checked mail from my Verizon account, and my Linux
server, but not my Internet mail server.

As I said before, one time it might not check my Linux server, but it
will the other two. Another time it might check all three, and
another time it might check one and not the other two. It's not set
on which ones it has trouble with.

I've also noticed that when it has trouble checking mail on a server,
if I cancel the send/receive and try to check mail on that server only
it NEVER even tries to connect to the server. It just sits there with
'Send/Receive 50% Complete' or something. I know it's not trying to
connect to the server because I setup a packet sniffer to watch what
it is doing, and it never tries to connect.

Thanks,
spdy

 

[spdy]

I *THINK* I found the problem! I installed a program called
'NetLimiter' a few months ago and I was doing some digging today and
ran msinfo32. I then checked the Protocols tab for network and saw
some weird additions to the protocols. Such as NL RSVP and other 'NL'
stuff. I was asking myself 'what the heck is this NL garbage'??? I
did some googling and nuthin. Then I started looking elsewhere and
saw 'NetLimiter' and it clicked. This program will limit the download
speed (or upload speed) of any program you want it to. It works
really well too.

So I uninstalled NetLimiter and it got rid of those extra 'NL' things
in the protocols tab of msinfo32.

I ran Outlook and it checked all 3 accounts. I then did this about 5
times and so far it has checked them without any trouble.

So it *looks* like I found the culprit! NETLIMITER! Guess I'll have
to wait until an update is available or find a better program that
does what NL does.

I will post back in a couple days to (hopefully) bring this thread to
a close with a final conclusion.

Thanks for all the MVP's help.

TTYL,
spdy

 

[Jeff Stephenson [MSFT]]

Your previous message still did not have the attachment, but that appears to
be moot. Hope your discovery proves to work for you!

 

[spdy]

It's official! My problem has been solved by removing NetLimiter
v1.30.

Thanks for all your help. Hopefully I won't need it again, but if I
do I'll be back

-- spdy

 

[BillR [MVP]]

arghhh, 3rd party application interference.

It's official! My problem has been solved by removing NetLimiter
v1.30.

Thanks for all your help. Hopefully I won't need it again, but if I
do I'll be back

-- spdy