List Info

Thread: did I miss Passed SPAMMY?




did I miss Passed SPAMMY?
user name
2006-06-28 13:45:04
Did I miss something in the notes?
amavisd-new 2.4.1?

I see lots of these in the maillog:

'Passed SPAMMY'

What is SPAMMY? and why is it different then 'Passed
SPAM'?

I suppose logs that grep for 'Passed|Blocked SPAM' will be
ok, but not 
if they look for 'Passed|Blocked SPAM\s'



-- 
Michael Scheidell, CTO
SECNAP Network Security / www.secnap.com
scheidellsecnap.net  / 1+561-999-5000, x 1131


Using Tomcat but need to do more? Need to support web
services, security?
Get stuff done quickly with pre-integrated technology to
make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on
Apache Geronimo
http://sel.as-us.falkag.net/
sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.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/
did I miss Passed SPAMMY?
user name
2006-06-28 15:32:15
Michael,

> Did I miss something in the notes?
> amavisd-new 2.4.1?
> I see lots of these in the maillog: 'Passed SPAMMY'
> What is SPAMMY? and why is it different then 'Passed
SPAM'?

SPAM is above kill level. It is usually blocked, unless
spam destiny is D_PASS or recipient is a spam lover.

SPAMMY is above tag2 level (and below kill level).
It is usually passed (but need not be), and gets X-Spam-*
header fields inserted, and ***SPAM*** in the Subject.

It was introduced in 2.4.1 to overcome an inconsistency
introduced in 2.4.0 by contents categories concept.
The 2.4.1 (and 2.4.2) is consistent with 2.3.3,
the 2.4.0 had an anomaly.



amavisd-new-2.4.1 release notes

INCOMPATIBLE CHANGE WITH 2.4.0:

- notification templates incompatibility with 2.4.0 (but not
with versions
  2.3.3 or older): major contents category numbers are
renumbered due to a
  newly inserted category CC_SPAMMY; it affects the use of
macro ccat_maj
  in templates (one field added), and only affect users
which provide
  non-default templates based on 2.4.0 templates; older
templates (2.3.3
  or earlier) are unaffected as they do not use macro
ccat_maj;


OTHER CHANGES:

- revert a change introduced with 2.4.0, which was adding
address extensions
  at CC_SPAM, i.e. when score exceeds kill level. Previously
(2.3.3) address
  extensions were inserted at tag2 level. Implemented by a
new mechanism:
  a new major contents category CC_SPAMMY is inserted just
below the CC_SPAM,
  where CC_SPAMMY is controlled by tag2_level and CC_SPAM
continues to be
  selected at kill_level. Also spam defanging (if enabled)
is now activated
  at CC_SPAMMY and no longer at CC_SPAM (which was on a TODO
list for some
  time); undesired change in 2.4.0 reported and changes
tested by Mario Liehr;

Mark

Using Tomcat but need to do more? Need to support web
services, security?
Get stuff done quickly with pre-integrated technology to
make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on
Apache Geronimo
http://sel.as-us.falkag.net/
sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.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/
[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )