A pre-release of amavisd-new-2.5.0 is available at:
http://www.ijs.si/software/amavisd/amavisd-new-2.5.0-pre1.tar.gz
COMPATIBILITY WITH 2.4.5
The 2.5.0 is upwards compatible with 2.4.* versions.
Nevertheless, default notification and logging templates are
enhanced to take advantage of new macros and new concepts,
so it is prudent to update templates if defaults are overridden,
e.g. $log_templ, $notify_*_admin_templ, ...
NEW FEATURES AT A GLANCE
- phishing fraud as returned by ClamAV is treated as spam, no longer
as a virus;
- new concept: blocking contents category;
- enhancements to amavisd-nanny;
- extended AM.PDP protocol with an attribute 'policy_bank' which may be used
in a client's request to require loading additional policy banks...
NEW FEATURES
- make it possible for a virus scanner to contribute its opinion on
spam: new configuration variable @virus_name_to_spam_score_maps,
also member of policy banks, can turn a virus name into a spam score.
Its default setting is:
@virus_name_to_spam_score_maps =
(new_RE( [ qr'^HTML\.Phishing\.Bank-' => 10 ],
[ qr'^HTML\.Phishing\.Pay-' => 11 ] ));
and can be replaced in amavisd.conf. When a virus scanner returns
names of viruses, and all provided names are matched by the
@virus_name_to_spam_score_maps, and no other virus scanner has
anything more sinister to report, then a message is _not_ flagged
as a virus, but a corresponding spam score is contributed to other
spam results as returned by a normal spam scan by SA. All the usual
spam rules are followed as usual, phishing fraud as indicated by
ClamAV is treated as spam, and no longer as a virus.
The log shows entries like:
amavis[25453]: (25453-01-2) Turning AV infection into a spam report:
score=14, AV:HTML.Phishing.Bank-1035
amavis[25453]: (25453-01-2) adding SA score 47.21 to existing 10
from an earlier spam check
- added a new concept of a 'blocking contents category', which in most cases
corresponds to a familiar 'main contents category' (the highest ranking
category of contents pertaining to a message, e.g. virus, blocked, spam,
spammy, bad header ...). The difference between the two arises when
recipients are declared to be 'lovers' of some higher-ranking contents,
or when a higher ranking contents category has its *_destiny set to D_PASS.
For example: a message contains a banned part, but is also spam
and may even have a bad header. Its contents categories are (simplified):
CC_BANNED, CC_SPAM and CC_BADH, in this order. The main contents
category of a message is CC_BANNED, which usually is also a reason
for blocking a message, yielding a blocking ccat to also be CC_BANNED.
But if some recipient is banned_files_lover (or if $final_banned_destiny
is set to D_PASS), then the main ccat remains to be CC_BANNED, but the
blocking ccat is CC_SPAM, i.e. the next in the list which is responsible
for actually blocking the mail. If recipient would also be a spam lover,
the blocking ccat might be CC_BADH (if $final_bad_header_destiny were
not D_PASS);
If a message is not being blocked, the 'blocking contents category'
(i.e. a blocking_ccat attribute of a per-message or a per-recipient object)
remains empty (undefined). For convenience some internal routines
and some new macros fall back to showing the main contents category
in this case.
Almost all processing decisions, DSN, notification assembling, quarantining,
logging etc. is now based on 'blocking contents category' when a message
is being blocked, and on 'main contents category' (as before) when a
message is not being blocked.
[...]
- amavisd-nanny enhanced and new process-state instrumentation added to
amavisd daemon; previously only busy/idle states of child processes were
shown in amavisd-nanny output, now a more detailed process state can be
shown by setting a new verbosity control configuration variable
$nanny_details_level to a higher than a default value of 1, e.g. to 2;
The following characters in amavisd-nanny bars represent amavisd child
process states as follows, in the shown order of events:
A accepted a connection
b begin with a protocol for accepting a request
m 'MAIL FROM' smtp command started a new transaction in the same session
d data transfer from MTA to amavisd
= content checking just started
D decoding of mail parts
V virus scanning
S spam scanning
P pen pals database lookup and updates
r preparing results
Q quarantining and preparing/sending notifications
F forwarding mail to MTA
. content checking just finished
[...]
Please see RELEASE_NOTES for detail.
Mark
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
