A pre-release of amavisd-new-2.5.1 is available at:
http://www.ijs.si/software/amavisd/amavisd-new-2.5.1-pre1.tar.gz
The 2.5.1 is primarily intended to be a bug fix release over 2.5.0,
with one small new feature.
NEW FEATURE
- introduced a variation of a message release from a quarantine, allowing
a releaser to choose between forwarding a message to the back-end MTA
port as usual (avoiding re-checking of a message), or to send it to MTA
on its incoming port (normally 25) and let the message be rescanned,
which might be useful after adjusting spam rules or antivirus database.
It is implemented by:
* adding a configuration variable $requeue_method (also a member
of policy banks), with a default value: 'smtp:[127.0.0.1]:25'
* extending the AM.PDP protocol with a 'request=requeue' attribute
which can be used in place of a 'request=release',
* enhancing the 'amavisd-release' utility program to choose between
sending 'request=release' and 'request=requeue' based on its
program name, i.e. by making a soft or hard link to amavisd-release
(or its copy) named 'amavisd-requeue', the utility will send
a 'request=requeue' in place of the usual 'request=release', e.g.:
# ln -s amavisd-release amavisd-requeue
$ amavisd-requeue spam/k/kg2P0rP9Lpu3.gz
* enhancing amavisd daemon to choose between forwarding a released
message either to $release_method or to $requeue_method destination
based on a 'request' attribute value in an AM.PDP request;
BUG FIXES
- fixed quarantining to a SQL database of messages with a null envelope
sender address (broken in 2.5.0, causing such messages to tempfail);
reported by Markus Edholm, Vahur J<F5>esalu and Michael Scheidell;
- fixed parsing of certain broken 'From' header fields, which would
result in a temporary failure and the following logged error:
check_init2 FAILED: parse_address_list PANIC1 53
at /usr/local/sbin/amavisd line 3292
reported by Michael Scheidell;
- avoid encoding nonprintable characters in X-Envelope-From and X-Envelope-To
header fields in a quarantined message even if envelope mail addresses
contain such invalid characters, so that a quarantine release is possible;
(RFC 2047 allows encoding of a 'phrase' in From, To, and similar headers,
as well as in comments, but not in the address specification);
- avoid unnecessarily RFC 2047 -encoding of 8-bit characters in those
lines of inserted X-Spam-Report (and similar) multiline header fields
which only contain ASCII characters; also avoid encoding of newlines;
reported by Anant Nitya;
- properly recognize PostgreSQL error code 'S8006' and reconnect to
a disconnected server right away; thanks to Brian Wong;
- call $mail_obj->finish after a SA call to allow for garbage collection
and removal of SA temporary files; see:
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5444
- avoid nonstandard SMTP status code 254 on discarded malware;
on discarding turn status 554 into a 250 instead; violation
of a SHOULD in RFC 2822 pointed out by Alexander Bergolth;
- an informational log message was reported inappropriately:
INFO: truncated ... header line(s) longer than 998 characters
it didn't reflect reality, it was always reported together with the:
INFO: unfolded 1 illegal all-whitespace continuation lines
- when a SMTP option BODY=8BITMIME (RFC 1652) is not given on mail
reception, avoid turning it on while forwarding even if mail body
contains 8-bit characters; following a garbage-in-garbage-out
principle, this doesn't break anything that isn't already broken,
but might prevent later conversion to 7-bit quoted-printable MIME
by some downstream MTA, possibly preventing signature invalidations
(DKIM, S/MIME, PGP, ...) - at a risk that some overzealous firewall
might block a mail transfer;
- fixed a couple of documentation typos/bugs in README.customize,
thanks to Mike Cappella;
OTHER
- modified code for checking each eval {} status: it turns out that eval
is able to capture certain error conditions (e.g. certain I/O errors)
but without setting the $@ variable, leaving it empty; use new idiom
throughout for proper error handling and more informative reporting,
showing errno in such cases;
- setting $bypass_decode_parts to true now also disables MIME decoding,
not just decoders/dearchivers listed in a @decoders list, and also
implicitly retains full original message for virus checking, equivalent
to having a regular expression /^MAIL$/ in a @keep_decoded_original_maps
list; prompted by Bill Landry;
- provide checking of a number of archive members against $MAXFILES quota
even when just listing an archive directory, providing some additional
protection (besides a time limit) against runaway dearchivers;
- modified syslog writing to check the (undocumented) status in errno
after calling Unix::Syslog::syslog, and to retry a couple of times
in case of a failure; this should prevent or at least minimize loss
of logged messages after syslogd daemon is restarted; unfortunately
the system routine syslog(3) returns no value according to documentation,
so its completion status can not be tested; problem reported by Paul;
- collect and report statistics on logging, amavisd-agent now also reports:
LogLines ... number of calls to syslog or direct writes to a log file
LogRetries ... number of times a failed syslog call needed to be retried
TimeElapsedLogSleep ... elapsed time in sleep between syslog retries
- updated AV entry for ESET NOD32 Linux Mail Server - command line
interface (nod32cli), version 2.7, thanks to Simon;
- updated AV entry for Sophos sweep, adding options -mime and -oe ;
- uncomment some debugging printouts in p0f-analyzer.pl and land them
under control of a $debug variable;
Mark
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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/