What is a better solution & easier?? using MICROSOFT_BRAIN_DAMAGE or adjusting the timeout. can anyone easily point me to the place in the docs that explains both of these options ... I am running redhat on this particular server and I am afraid if i recompile I will break everything for too long (server is accessed 24/7)....
Sorry for the questions guys, Redhat is making it hard to adjust things easily.... -- Alex Esselstein ABE Technology Support Services http://www.abetss.com 614.581.2539 Voice 614.444.3568 Fax [EMAIL PROTECTED] Text Messaging Disclaimer: This e-mail will be of no force of effect and will not be binding on ABE Technology Support Services, unless a hard copy of this e-mail, signed by an authorized official of the company, has been sent to the recipient of this message. ----- Original Message ----- From: "Marek Kowal" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, April 03, 2002 5:55 AM Subject: RE: OUTLOOK 2K+ your imap server closed the connection error message > > 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? > > Seriously, it wouldn't be the big deal to do. And also, many people would be > happy with it. Let's face it - more than 90% of mail readers out there are > Outlook and Outlook Express. > > m.
