kfx,
> centos 5.2 x86_64, amavisd-new-2.6.1, postfix 2.5.2
> I went from amavis 2.3.3 to 2.5.2 and then, in my maillog I have plenty
> of this:
>
> Aug 14 19:32:53 myserver amavis[3117]: (03117-03) smtp resp to NOOP
> (idle 153.5 s): 250 2.0.0 Ok
> Aug 14 19:32:53 myserver amavis[3116]: (03116-02) smtp resp to NOOP
> (idle 170.4 s): 250 2.0.0 Ok
> Aug 14 19:36:01 myserver amavis[3115]: (03115-02) smtp resp to NOOP
> (idle 358.7 s): 421 4.4.2 myserver.lidil.univ-mrs.fr Error:
> timeout exceeded
> What's the meaning of this error ? postfix is making amavis waiting too
> long to get back the email after treatment ?
>
> sometime an "Error: timeout exceeded" happens, does that mean that the
> mail is discarded and not given back to postfix ?
Everything is normal, it is just a side effect of how the new smtp-session
caching feature works. I'll drop the log level to 3 (from 2) on these
messages for the next release to reduce log clutter.
amavisd-new-2.6.0 release notes:
- smtp client connection caching is a new feature which allows smtp client
code in amavisd to keep a SMTP session to MTA open after forwarding a
message or a notification, so that a next mail message that needs to be
sent by this child process can avoid re-establishing a session and the
initial greeting/EHLO (and TLS) handshake.
A current value of a global settings $smtp_connection_cache_enable
controls whether a session will be retained after forwarding a message
or not. Its default initial value is true.
A global setting $smtp_connection_cache_on_demand controls whether amavisd
is allowed to dynamically change the $smtp_connection_cache_enable setting
according to its estimate of the message frequency. The heuristics is
currently very simple: if time interval between a previous task completion
by this child process and the arrival of a current message is 5 seconds
or less, the $smtp_connection_cache_enable is turned on (which will affect
the next message); if the interval is 15 seconds or more, it is turned off.
The default value of the $smtp_connection_cache_on_demand is true, thus
enabling the adaptive behaviour.
On a busy server the connection caching can save some processing time.
Savings are substantial if client-side TLS is enabled, otherwise just a
few milliseconds are saved. On an idle server the feature may unnecessarily
keep sessions to MTA open (until MTA times them out), so one can disable
the feature by setting both controls to false (to 0 or undef).
To monitor the connection caching effectiveness, some SNMP-like counters
were added, so amavisd-agent may display something like:
OutConnNew 2764 319/h 98.2 % (OutMsgs)
OutConnQuit 2521 291/h 89.5 % (OutMsgs)
OutConnReuseFail 7 1/h 0.2 % (OutMsgs)
OutConnReuseRecent 21 2/h 0.7 % (OutMsgs)
OutConnReuseRefreshed 31 4/h 1.1 % (OutMsgs)
OutConnTransact 2816 325/h 100.0 % (OutMsgs)
Mark
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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/
