We have a few users (say 20-30 out of 8000+) who have reported that
their email doesn't work from home the last year.
The common denominator for these users is microsoft outlook (not outlook
express). Pine/alpine works fine as does thunderbird and our webmail
(squirrelmail, with imapproxyd to take some load off the ldap server).
When I look at the server, they have lots of imap processes, and when I
kill them (the processes, not the users), everything goes back to
normal. But once the get home and start outlook the problem is back. The
only effective solution has been to make them a switch to thunderbird.
I know about Microsoft's aggressive way of starting imap connections, but
they shouldn't deadlock.
There are several other users who use outlook without any problems.
For a few years, I used imap-2004e with mbx folders and didn't hear of
this problem. It didn't occur until I upgraded to
imap-2006e.DEV.SNAP-0701181849 and started the mix conversion.
The problem occurs for both mbx and mix users, so it shouldn't be the
mbx deadlock problem discussed here last month.
A few weeks ago, I switched to a new server which is running
imap-2006k.DEV.SNAP-0709051605. Since then no one has reported anything,
but as you can see from the numbers above, I didn't exactly get daily
reports before the upgrade either.
The current server runs debian etch (kernel 2.6.18), the old one used
debian sarge (2.6.8). It both cases, it is the 32-bit intel version.
Has the latest upgrade solved this problem, or is it maybe related to
certain outlook versions since some users don't have any problems?
Sorry if this is a faq. I don't always have the time to keep up
with the mailing list.
/Per
_______________________________________________
Imap-uw mailing list
Imap-uw@u.washington.edu
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
