We're wandering a bit far from procmail now, but:
On 5/29/06, Gary Funck <gary(_at_)intrepid(_dot_)com> wrote:
... I vagurely remember that the UW
package would hang or be non-responsive to an Outlook client, and
dovecot was much faster and more reliable.
Outlook (and OE, though the latter less aggressively so) tends to open
multiple connections on the same mailbox, which in mbox format is a
no-no; because it's a flat file, the entire thing has to be locked
during any (non-read-only) access. As a consequence, when Outlook
does this, it forces one or the other of the servers to exit and
relinquish the lock to the remaining one. This can seriously confuse
This is not a problem with the UW server as much as it is a problem
with Outlook's assumption that the only servers it needs to
interoperate with are those that behave exactly like Exchange.
It's all a matter of what's important to you. RFC compliance and
working mbox folders? Choose UW, and make your users either live with
Outlook being confused or switch to some other client. Happy Outlook
users? Pick another server; maybe that's Courier, though last I
looked Courier wanted everything in "maildir" format, so your mbox
users are out of luck.
procmail mailing list Procmail homepage: http://www.procmail.org/