[EMAIL PROTECTED] wrote--
>I could certainlly post my config, and everything I'm doing/done if
that would help.  Let me know, and I can write that up.
>
>As you can see from my statistics page, Beyesian is catching most of
the stuff, but it's also catching valid emails.  Since >I'm in test
mode, it's not a problem, and we can report NOTSPAM to ASSP on those,
but once we pull out of test mode, those >good "spams" will not be seen.
If the answer is to leave Beyesian test mode on, it seems I need to get
the other setting 
>to block the majority of our spam.


I personally would not stay in test mode forever.  We ran in test mode
for about 30 days.  During which time I made it known that it was
important that users report misidentified spam/ham so that ASSP would be
trained as to what is SPAM for our organization.  Incorporate, training
the Bayesian system, with the other checks, (RBL, SPF) as well as
putting things such as newsletters, mailing lists, out-of-office
replies, etc. on the redlist or no-processing list, depending on what
they are and also when you get a better handle on what kind of spam you
are seeing you can then incorporate some attachment blocking and regex
blocking for spam bomb etc. 

Once the training period is done take it out of test mode.  ASSP is made
to do Bayesian checks and is quite good at learning what is spam and
what is not.  If you have been diligent during the training period it
should be really accurate.  In order to handle the occasional false
positive, modify the 550 error message(Under "SPAM Control -> SPAM
Error" in the configuration page) that ASSP sends to the originating
mail server when it drops a spam connection. This will usually alert
sender that their email was marked as SPAM. Create an email address that
is on the no-processing list that they can then send an email to and ask
to be whitelisted.

 Ours reads as follows;
        550 5.7.7 YOUR EMAIL WAS NOT DELIVERED BECAUSE YOUR -- YOUR
EMAIL APPEARED TO BE SPAM -- If you feel this is incorrect,     send
error reports to [EMAIL PROTECTED] with #ERROR-REPORT# in the subject
line.

Then you can send them an email telling them they are whitelisted (or
ignore them if they were blocked for good reason) That way you stop the
spam from ever getting to your users email client which saves them time
and your company money.

That is my $0.02 worth.

Ged 

-------------------------------------------------------------------------
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
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to