Mark, there was a lengthy discussion of this issue in the newsgroup
microsoft.public.windows.live.mail.desktop, see the thread
"How can I stop forcing APOP?"
WLM currently has the same APOP problem as WM.
The only workaround is to use a different email client
like Outlook or Thunderbird for that account.
A Microsoft rep named David made the following comments:
"As it is right now, there is no way to stop WLM from trying APOP when it
sees a time stamp (for example: <
[email protected]>) in the POP3
server's greeting.
If a user has clear text selected but a time stamp is found, WLM will try
APOP. If APOP fails, WLM will then try to authenticate using clear text on
the same session. The problem is that some servers are closing the session
after sending back the negative reply to APOP."
Which he later supplemented with:
"We'll definitely look at this problem for future releases.
We'd hoped that if a POP3 server appeared to support APOP by the presence of
a time stamp in the POP3 greeting we could send APOP and make the session
that much more secure for users (APOP doesn't send a user's password in
clear text). The thought was that if a server rejected the APOP command but
the user had clear text selected in WLM, WLM would then try to authenticate
in clear text. If you turn on POP3 logging in WLM, you'll probably see this
behavior just before the session is terminated.
Unfortunately, we're now seeing that servers are rejecting APOP and then
terminating the session. The RFCs say that either a rejected APOP or USER
command should leave the session in the authorization state with the client
free to try again, so this situation with POP3 servers abruptly terminating
sessions following the APOP command is a little confusing."
Apparently Microsoft will rethink this issue for the next iteration of WLM.
Gary VanderMolen
When I used Outlook Express I had no problem accessing my Voicenet mail. When I upgraded to Windows Live Mail (which I like
better) I can no longer read mail. I get the following error:
Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or
a long period of inactivity. Account: 'Arcticairinc (cusumano)', Server: 'popmail.voicenet.com', Protocol: POP3, Port: 110,
Secure(SSL): No, Error Number: 0x800CCC0F
These settings worked fine under Outlook Express.
Just an update. I checked the logs and for some reason it is trying to use APOP to authenticate even though clear text is
selected. There is one anomaly with this account. The username is NOT the same as the first part of the address. The username
is arctic05. I'm wondering if WLM assumes if the username and the address do not match that APOP must be used (which is not the
case for voicenet). In either case it should not override my settings. Any ideas?
