Tom,

| I'm trying to get SA 2.50 working under the amavisd-new release.
| It's working, I think.  At least according to the logs.
| Between the two, there is a marked increase in performance.
| Very nice!

| But there is no WhiteList.
| Any suggestions on how to get this turned on?

Turning on SA auto whitelists is presently not useful
with amavisd-new. There is a fundamental problem in that
SpamAssassin is geared to work fine with one-recipient-
-at-a-time messages, and amavisd-new tries to process
multi-recipient messages in one go if at all possible
(and tries very hard to be efficient even when different
headers need to be inserted for different recipient groups).

For example there is no provision for the caller to pass
envelope recipients and envelope sender to SpamAssassin.

Fortunately, the Bayesian spam/ham classification
brought-in by SpamAssassin 2.50 (when well trained)
more than compensates for the lack of AWL.
I don't think the lack of AWL is a serious drawback.

| Unfortunately the debug lines are screaming by so fast I can't 
| capture much out of the and '| more' doesn't affect it.
| I guess I'm just not sure if this is actually working 100%.
| amavis log output provided just in case...

Looks ok (but you didn't show the complete transaction).
Now you may run it without the 'debug' option, and let it
log only important events to syslog (preferred over
directly logging to a file).

  Mark


-------------------------------------------------------
This SF.NET email is sponsored by:  The Best Geek Holiday Gifts!
Time is running out!  Thinkgeek.com has the coolest gifts for
your favorite geek.   Let your fingers do the typing.   Visit Now.
T H I N K G E E K . C O M        http://www.thinkgeek.com/sf/
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to