David,
> > TimeElapsedReceiving is the ...
>
> Ah, OK. So basically this a value that describes more
the behaviour of
> the SMTP clients than the performance of the content
scanner.
Yes. Actually this time is dominated by the tight loop which
unfortunately
needs to read input line-by-line to do dot-destuffing, and
to reset
a watchdog timer with each line, as expected for a SMTP
server.
A CHUNKING support on the Postfix client-side would improve
the
transfer rate, although it is not too bad as it is.
Interestingly, the sending side (smtp from amavisd to MTA)
is an order of magnitude faster, due to the use of large
buffers (avoiding line-by-line I/O). The pipelining brings
its benefits there too.
> I understand. log_level=2 is not really an option for
us, however,
> because we don't want to log that much for every mail.
I can live with
> it though 
We keep three log files for amavisd at different syslog
priorities:
user.notice /var/log/amavisd.log
user.info /var/log/amavisd-info.log
user.debug /var/log/amavisd-debug.log
The compact amavisd.log is kept for long times and
archived.
The amavisd-info.log (corresponds to log level 2) is kept
for
a week or two, and consulted for problem and timing
analysis,
then is discarded.
The amavisd-debug.log is kept for few days and is used for
analysis of problems which might have occurred in the last
few days, and sometimes for selective displaying of some
particular log entry, e.g.
tail -f /var/log/amavisd-debug.log |
pcregrep 'SA dbg: dkim: |_WARN:|_DIE:|TROUBLE'
The $log_level is set to 5, and the log level to syslog
priority
mapping is as described in 2.6.0-pre3 release notes:
The following table shows mapping of SpamAssassin log
levels to amavisd
log levels, and for completeness also shows mapping of
amavisd log levels
to syslog priorities (which has not changed since previous
version):
SA amavisd syslog
----- ------- -----------
-3 LOG_CRIT
-2 LOG_ERR
error -1 LOG_WARNING
warn 0 LOG_NOTICE
info 1 LOG_INFO
2 LOG_INFO
dbg 3 LOG_DEBUG
4 LOG_DEBUG
5 LOG_DEBUG
One needs to make sure the syslogd does not sync a log file
to disk
on every write (a default on Linux).
Mark
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
AMaViS-user mailing list
AMaViS-user lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/
|
