Re: Slow lmtpd

From: Andre Nathan (no email)
Date: Wed Mar 07 2007 - 07:35:10 EST

  • Next message: Andre Nathan: "Re: Slow lmtpd"

    On Tue, 2007-03-06 at 13:11 +0100, wrote:
    > You should always limit your MTA(s) (Postfix) LMTP clients to match the
    > max number at your LMTP Server (Cyrus). Be sure to use a separate
    > transport for lmtp and use the lmtp_connection_cache and maybe raise
    > the max_use value. With this even small numbers of LMTP clients (<5)
    > will be able to saturate your Cyrus I/O so no need to get in trouble
    > with many hundreds LMTPs waiting for I/O slots.
    > I would start with 2 LMTP client connections per MTA and see what
    > happens. As said if you don't have long running sieve scripts this
    > should be enough to get near the max transferrate your Cyrus can handle.

    Thanks, I'll try that. I'm currently using lower values values for both
    the concurrency limit and the lmtpd process limit. At least the load
    average is lower now, and even if delivery may take some more time, it's
    less pain for the imap/pop3 users.


    Cyrus Home Page:
    Cyrus Wiki/FAQ:
    List Archives/Info:

  • Next message: Andre Nathan: "Re: Slow lmtpd"

    Hosted Email Solutions

    Invaluement Anti-Spam DNSBLs

    Powered By FreeBSD   Powered By FreeBSD