OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: postfix and content_filter

From: Noel Jones (njonesmegan.vbhcs.org)
Date: Mon Jan 01 2007 - 15:51:12 CST


At 12:51 PM 1/1/2007, Pavel Urban wrote:

>>>>127.0.0.1:10025 inet n - n - 80 smtpd
>>>> -o content_filter=
>>>> -o
>>>> receive_override_options=no_unknown_recipient_checks,no_header_body_check
>>>>s,no_address_mappings
>>>> -o local_recipient_maps=
>>>> -o relay_recipient_maps=
>>>> -o smtpd_restriction_classes=
>>>> -o smtpd_client_restrictions=
>>>> -o smtpd_helo_restrictions=
>>>> -o smtpd_sender_restrictions=
>>>> -o smtpd_recipient_restrictions=permit_mynetworks,reject
>>>> -o mynetworks=127.0.0.0/8
>>>> -o strict_rfc821_envelopes=yes
>>>> -o smtpd_use_tls=no
>>>> -o smtp_use_tls=no
>>>>
>>>>in my master.cf. It works, but slowly. The strange thing is this:
>>>>
>>>>[rootantivir6 ~]# ps -ef|grep amavisd|wc -l
>>>>66
>>>>[rootantivir6 ~]# ps -ef|grep lmtp|wc -l
>>>>22
>>>>
>>>>Load: 4.05, 4.18, 4.36
>>>>
>>>>Main postfix:
>>>>------------------------------------------------------------
>>>>Incoming: 2
>>>>Active: 4506
>>>>Deferred: 0
>>>
>>>Is the queue congested before or after the content filter?
>>Before, as far as I can say from headers in files in active queue.
>
>That's strange - I've tried to increase number of lmtp processes and
>there are still exactly 22. Is there some hardcoded limit for this?
>It's quite annoying, because I just cannot saturate amavisd-new
>childs this way and active query keeps filling up...
>
>smtp-amavis unix - - n - 100 lmtp
> -o lmtp_data_done_timeout=1200
> -o disable_dns_lookups=yes
>
>[rootantivir5 ~]# ps -ef|grep lmtp|wc -l
>22

# main.cf
smtp-amavis_destination_concurrency_limit = 100

Caution: If postfix attempts to make more than the amavisd.conf
$max_servers connections to amavisd-new, performance will suffer horribly.
http://www.postfix.org/TUNING_README.html#rope

--
Noel Jones