Andrew,
> for the default smtp-amavis the use max is set to 2 and overriddenby
> usemax=20 when the default max for any of these postfix transports is 100
What is usemax? Never heard of it.
> This was confusing .. seemingly postfix works on the lowest setting (2 in
> this case).
>
> I have a busy mail server that at times handles about 15000 mails in the
> queue ... 2 max processes for amavisd seems crazy to me ... the hardware is
> pretty good hardware raid 3.2 gig Prescot HT (2MB cache) intel server board
> 2 gig RAM etc. ...
>
> I pushed it up from the default 2 to 20 and it ticks over much better
> surely this will be a better default to save admins setting up servers from
> getting backlogged quese over night ... (I know I should probably look to
> more hardware etc but 20 seems safer than 2).
From README.postfix:
>>
The most important tuning knob is the number of concurrent content filtering
processes allowed. Too low a value does not fully utilize the host resources,
a somewhat high value wastes memory and gains no benefit to the aggregate
mail throughput, while a too high value causes system thrashing and the
total system mail throughput starts to drop. A useful starting value is 2,
a commonly useful range is perhaps up to 10 (or perhaps 20 on hosts with
1 GB of RAM or more, and SA with network tests such as Razor enabled),
but the exact value largely depends on host capabilities and the anti-virus
and anti-spam options in use.
It is imperative that both the Postfix and the amavisd-new use the same value.
Actually the amavisd setting may be higher that the Postfix, but this serves
no useful purpose and just wastes resources. The amavisd.conf parameter is
the $max_servers, the Postfix parameter is the maxproc field in the
'smtp-amavis' entry (file master.cf).
Instead of adjusting the maxproc field of the 'smtp-amavis' service,
one may prefer to leave it a the default '-', and use a main.cf option
for the same purpose:
smtp-amavis_destination_concurrency_limit = 2
<<
> On the next note ... amavisd-new is a great peice of software I plan to
> deploy for a lot of clients .... keep up the great work guys ...
>
> Thirdly ...without success I tried to set bypassing of scanning for a
> specific user on my domains.
>
> amavisd.conf as follows
> @bypass_virus_checks_maps = ('[EMAIL PROTECTED]');
> @bypass_spam_checks_maps = ('[EMAIL PROTECTED]');
> @bypass_banned_checks_maps = ('[EMAIL PROTECTED]');
> @bypass_header_checks_maps = ('[EMAIL PROTECTED]');
>
> Am no perl expert by any stretch however all seems in order ... however
> this seems to turn off scanning for all users as when I implemented it we
> did not reject one spam message or virus the entire day ...
> (usually about 3000 a day) ...
No wonder it doesn't catch anything, you have disabled all checks
unconditionally. Your only entry in each @_maps list is a constant
string, which matches everything and returns itself as a lookup result
(see README.lookups - "A CONSTANT"). Your setting is equivalent to
@bypass_spam_checks_maps = (1);
You probably wanted to use an array (acl) as a lookup table:
@bypass_spam_checks_maps = ( ['[EMAIL PROTECTED]'] );
Mark
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
