OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Victor.Duchovni_at_morganstanley.com
Date: Tue Aug 06 2002 - 09:45:43 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    On Mon, 5 Aug 2002, Vivek Khera wrote:

    > VD> This is not right. The 50 sets the total transport concurrency. Because
    > VD> the transport is only used for a single destination, one needs to set a
    > VD> higher destination concurrency if that is desired. *BUT* one should NOT
    > VD> set a high concurrency for destinations that are notunder one's control.
    >
    > So as long as default_destination_concurrency is higher than the
    > transport process limit in master.cf, it is sufficient. If you want
    > higher conecurrency than the default, then you need to increase the
    > XXX_destination_concurrency to match the number in master.cf.
    >

    The default value of default_destination_concurrency is 10. This should
    not IMHO be changed if Postfix sends mail to the Internet. Transport
    process limits are typically 50 or more. So while you are right, the
    premise is usually false. For single destination transports the transport
    process limit might as well be 10 (or whatever the destination concurrency
    is set to). Again I think that setting high concurrency for a third
    party destination is anti-social without prior arrangement.

    -- 
    	Viktor.
    

    - To unsubscribe, send mail to majordomopostfix.org with content (not subject): unsubscribe postfix-users