Hi, >> When using amavisd-new, shouldn't the number of processes match the >> number of smtpd processes? > > When using amavisd-new as a content_filter, the number of postfix > smtp->amavisd feeder processes should be equal to (or maybe one less > than for monitoring) the number of amavisd processes. This is > independent of the number of smtpd input processes.
I think I may be still a bit confused. Can you confirm that this is the relevant section I should be adjusting to prevent timeouts connecting to port 25: smtp inet n - n - - smtpd -o receive_override_options=no_address_mappings I also increased the number of amavisd feeder processes to 24 today, and it seemed to handle the load: smtp-amavis unix - - n - 24 smtp -o smtp_data_done_timeout=1200 -o smtp_send_xforward_command=yes -o disable_dns_lookups=yes -o max_use=20 127.0.0.1:10025 inet n - n - 24 smtpd -o content_filter= -o smtpd_delay_reject=no -o smtpd_client_restrictions=permit_mynetworks,reject -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions=permit_mynetworks,reject -o smtpd_data_restrictions=reject_unauth_pipelining -o smtpd_end_of_data_restrictions= -o smtpd_restriction_classes= -o mynetworks=127.0.0.0/8 -o smtpd_error_sleep_time=0 -o smtpd_soft_error_limit=1001 -o smtpd_hard_error_limit=1000 -o smtpd_client_connection_count_limit=0 -o smtpd_client_connection_rate_limit=0 -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks,no_milters -o local_header_rewrite_clients= Thanks again, Alex