A release candidate 1 of amavisd-new-2.5.1 is available at:
http://www.ijs.si/software/amavisd/amavisd-new-2.5.1-rc1.tar.gz
The 2.5.1 is primarily intended to be a bug fix release over 2.5.0.
Changes since 2.5.1-pre1:
- new AV entry: ArcaVir for Linux and Unix, see:
http://www.arcabit.pl/
http://www.arcabit.com/download_product.html?product=ArcaVirLinux2007
http://www.arcabit.com/products_arcavir_for_unix_2006.html
the entry was kindly provided by Michal Seremak;
- a new macro 'supplementary_info' gives access to some additional information
provided by content scanners, such as a provided by SpamAssassin API
routine get_tag. The macro takes two arguments, the first is a tag name
(a name of some attribute which is expected to provide an associated
value), the second argument is a sprintf format string and is optional,
if missing a %s is assumed. Currently the only available attributes are
AUTOLEARN, SC, SCRULE, SCTYPE, and RELAYCOUNTRY. These are nonempty only
when an associated SpamAssassin plugin or function is enabled.
- avoid repeatedly reporting the same set of modules by a log entry
'extra modules loaded:', only report it on changes to the list;
repeated reports could be misinterpreted that modules were loaded
with each mail task, where actually missing modules were only loaded
once within each child process;
- avoid reporting 'BOUNCE' in a SMTP response text when a bounce (i.e.
a nondelivery status notification) was actually suppressed, such as
is usually the case with infected mail or when spam score exceeds
spam_dsn_cutoff_level. Previously the SMTP response text only reflected
the setting of a final_*_destiny, which could mislead mail administrators
into believing that excessive unconditional backscatter was being
generated. The new text looks like:
250 2.5.0 Ok, id=67685-15, DISCARD(bounce.suppressed)
instead of previous:
250 2.5.0 Ok, id=67685-15, BOUNCE
- dspam options changed with version 3.8.0, replacing option --feature
with --tokenizer; reported by Jim Knuth;
- removed retries on syslog calls, there is no reliable way to
know whether a call failed; nevertheless, provide some
statistics on errno values after syslog calls
Feedback and testing is most welcome.
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/
