On Wed, Feb 08, 2006 at 08:21:42AM -0500, Simon Jester wrote: > >The standard solutions to these sorts of problems are: > >(1) install Thunderbird/Sylpheed/etc on the client and don't use Outlook; > >or > >(2) install MS Exchange on the server and don't use a free IMAP server > > And the standard answer to arrogant responses like this is: > > "Thanks, I'll go find another free solution that is at least interested > in *trying* to provide a working solution even for semi-broken Clients - > *especially* one that has the largest installed base in the (business) > world - as long as it can be done without breaking the server for > compliant clients." > > Dovecot, here I come.
OK - it just amazes me that people come here saying "I can demonstrate that there's a bug in Microsoft Outlook. What can I do to courier-imap to fix it?" IMO it's also pretty arrogant to assume that the developer of a standards-compliant IMAP server is going to bend over backwards to (a) analyse, and (b) work-around, all the brokenness in one particular IMAP client[*], when it's so easy to obtain and install a working client. Outlook is also the main vector for E-mail viruses and worms, so you can justify the overhead of installing something else on security grounds alone. Regards, Brian. [*] This being an IMAP client from a vendor who sells a proprietary E-mail server backend, and has a vested interest in the client *not* interoperating with free servers. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
