I switched to the mbox format and I have not had a connection error since. Not sure if this is apples vs. oranges.
The FAQ describes everything you need to do on the imapd side. The hardest part was getting procmail and dmail setup with all my email filters / recipes. > From: Arnt Gulbrandsen <[EMAIL PROTECTED]> > Date: Wed, 03 Apr 2002 14:09:03 +0200 > To: Marek Kowal <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Re: OUTLOOK 2K+ your imap server closed the connection error mes > sage > > Marek Kowal <[EMAIL PROTECTED]> >>> The problems are entirely at the Outlook end. The best way >>> to get them >>> resolved is to file problem reports with Microsoft. >> >> The other way, of course, is to patch the server sources with some >> interesting #define, i.e. MICROSOFT_BRAIN_DAMAGE, in which case it does not >> timeout after 30 minutes after IDLE command, but in 24 hours or so. There is >> something like NETSCAPE_BRAIN_DAMAGE in sources, why not acknowledge the >> Microsoft wisdom as well? > > Well, one one hand, it wouldn't even violate the protocol, which requres > that the timeout is _at_least_ 30 minutes. IIRC the uw server uses 31 > minutes, and could easily use 3100 minutes. > > But on the other hand, if a dialup machine hangs up the modem connection > without closing its TCP connections, an imapd or more would then hang > around for 3100 minutes. > > On the _third_ hand, the server could detect disappeared clients by > sending out an unsolicited OK every half hour during IDLE. > > On the _fourth_ hand (is this ridiculous yet?), IDLE-using clients may not > handle unsolicited OKs gracefully. > >> Seriously, it wouldn't be the big deal to do. > > Try some different timeout values on your site and let us know how bad the > problems with disappearing dialups are in reality ;) > > --Arnt
