SpamAssassin Doesn't Appear to be working

[JasonHirsh <hi...@att.net>]

I have a freebsd 7.0 RC3  server running postfix amavisd-new clamavd and
SpamAssassin...  Having just upgraded ports I believe they are all current
releases

In this set up I am lead top believe that Amavisd-new handles the SA config 
but I did not see a process for spamd so i enabled in rc.conf.    I am not
seeing any x-spam related headers in the long message header but the GTUBE
test message was discarded so it appears to be working

my amavisd config for SA  is

$sa_tag_level_deflt  = 2.0;  # add spam info headers if at, or above that
level
$sa_tag2_level_deflt = 6.31; # add 'spam detected' headers at that level
$sa_kill_level_deflt = 4.0; # triggers spam evasive actions
$sa_dsn_cutoff_level = 10;   # spam level beyond which a DSN is not sent
# $sa_quarantine_cutoff_level = 20; # spam level beyond which quarantine is
off
# $penpals_bonus_score = 5;  # (no effect without a @storage_sql_dsn
database)
# $penpals_threshold_high = $sa_kill_level_deflt; # don't waste time on hi
spam

$sa_mail_body_size_limit = 400*1024; # don't waste time on SA if mail is
larger
$sa_local_tests_only = 0;    # only tests which do not require internet
access?
$sa_spam_subject_tag = '***SPAM*** ';
# SpamAssassin settings


@bypass_banned_checks_maps = (
['.sanddollarbonaire.com','habitatbonaire.com',
'.constantcontact.com','.att.net'] );
# $sa_local_tests_only is passed to Mail::SpamAssassin::new as a value
# of the option local_tests_only. See Mail::SpamAssassin man page.
# If set to 1, no SA tests that require internet access will be performed.
#
$sa_local_tests_only = 0;   # only tests which do not require internet
access?
#$sa_auto_whitelist = 1;    # turn on AWL in SA 2.63 or older (irrelevant
                            # for SA 3.0, its cf option is
use_auto_whitelist)

any thoughts as to what happened to the headers and should i even care?


thanks

jason




-- 
View this message in context: http://www.nabble.com/SpamAssassin-Doesn%27t-Appear-to-be-working-tp22341459p22341459.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: SpamAssassin Doesn't Appear to be working

[Mark Martinec <Ma...@ijs.si>]

Jason,

> Got it  tweaked the settings
> set $sa_tag_level_deflt = 9999;

Good.

> and the header now shows... I feel better even if it was working before

Thanks for figuring out the solution by yourself.

The $sa_tag_level_deflt controls the spam score at which
X-Spam-* header fields start to be inserted. The default
setting is undef, meaning these are always inserted
(for local recipients). A low value (e.g. 2) is often used
to avoid cluttering the header for ham.

  Mark

Re: SpamAssassin Doesn't Appear to be working

[JasonHirsh <hi...@att.net>]

Got it  tweaked the settings


set

$sa_tag_level_deflt = 9999;


and the header now shows... I feel better even if it was working before 


-- 
View this message in context: http://www.nabble.com/SpamAssassin-Doesn%27t-Appear-to-be-working-tp22341459p22355132.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: SpamAssassin Doesn't Appear to be working

[JasonHirsh <hi...@att.net>]

>> In this set up I am lead top believe that Amavisd-new handles the SA
>> config
>> but I did not see a process for spamd so i enabled in rc.conf.
> 
> There is no need for a spamd process in this setup - think of amavisd
> proces as an equivalent of spamd (in that it calls a SpamAssassin library
> of perl modules), but speaks a different protocol: amavisd speaks SMTP,
> spamd speaks spamc/spamd protocol.
> 
> 
Ahh ok I understand that portion.. I was not aware



> 
> The most likely reason for absence of X-Spam-* header fields is that
> the recipient was not considered local - check your setting of 
> @local_domains_maps (or %local_domains or @local_domains_acl).
> X-Spam-* header fields are not inserted for outbound mail (i.e. when
> recipient is not considered local). Check the log (possibly at elevated
> log level) to make sure.
> 
> 

Not sure what I am looking for in log  I can see the rejection but not sure
what I am looking for relative
to the xspam  I am logging at level 4  I am going to bump up top 5

I have this in the config 

 @local_domains_maps = ( read_hash("/usr/local/etc/postfix/virtual_domains")
); # using hash


so my local domains should be recognized


thanks


jason

 


-- 
View this message in context: http://www.nabble.com/SpamAssassin-Doesn%27t-Appear-to-be-working-tp22341459p22350544.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: SpamAssassin Doesn't Appear to be working

[Mark Martinec <Ma...@ijs.si>]

Jason,

> I have a freebsd 7.0 RC3  server running postfix amavisd-new clamavd and
> SpamAssassin...  Having just upgraded ports I believe they are all current
> releases
>
> In this set up I am lead top believe that Amavisd-new handles the SA config
> but I did not see a process for spamd so i enabled in rc.conf.

There is no need for a spamd process in this setup - think of amavisd
proces as an equivalent of spamd (in that it calls a SpamAssassin library
of perl modules), but speaks a different protocol: amavisd speaks SMTP,
spamd speaks spamc/spamd protocol.

> I am not  seeing any x-spam related headers in the long message header
> but the GTUBE test message was discarded so it appears to be working
> any thoughts as to what happened to the headers and should i even care?

The most likely reason for absence of X-Spam-* header fields is that
the recipient was not considered local - check your setting of 
@local_domains_maps (or %local_domains or @local_domains_acl).
X-Spam-* header fields are not inserted for outbound mail (i.e. when
recipient is not considered local). Check the log (possibly at elevated
log level) to make sure.

  Mark