Scott Moseman writes:
Someone with an Outlook 2003 client gets an error when checking their
IMAP accounts, and this is what I see in the logs:
Nov 28 15:27:19 imapd: Connection, ip=[x.x.x.x]
Nov 28 15:27:19 imapd: Connection, ip=[x.x.x.x]
Nov 28 15:27:19 imapd: LOGIN, user=user1, ip=[x.x.x.x], protocol=IMAP
Nov 28 15:27:19 imapd: LOGIN, user=user2, ip=[x.x.x.x], protocol=IMAP
Nov 28 15:27:23 imapd: DISCONNECTED, user=user2, ip=[x.x.x.x], h, b, t
Nov 28 15:27:53 imapd: LOGOUT, user=user1, ip=[x.x.x.x], h, b, t
It appears the DISCONNECTED message fits into the time he had the
problem. All of the other entries in the logs show LOGOUT for each
IMAP check. Is this a message brought about by the server? Could it
be caused by the client?
This message is logged when the client terminates the connection to the
server without using a formal logout command.
And, importantly, what can I do to further troubleshoot or debug this
problem? Apparently it's a frequent problem for a particular
workstation. I'm curious if there's anything I can do on the server
side to get a better idea what's going on at the time it "crashes" on
them.
Add IMAPDEBUGFILE=debug.dat to the imapd configuration file and restart.
This will create debug.dat in _every_ maildir that anyone happens to log
into while this setting is in effect.
You will likely discover, after examining the relevant log file, the same
thing: the client craps out and shuts down the IMAP connection unexpectedly.
The standard advice applies, whenever you are getting buggy behavior from
Microsoft E-mail software: turn off any antivirus software, and try again;
turn it back on, update the virus definitions, do a full virus scan, and try
again; install a random service pack, and try again; reformat the hard
drive, reinstall Windows, and try again.
3 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Client or Server ...
