Frank wrote:

> There are no errors in the 0.log file and some hits:

>  pts rule name              description
> ---- ---------------------- --------------------------------------------------
>  0.0 UNPARSEABLE_RELAY      Informational: message has unparseable relay lines
>  0.2 MISSING_HEADERS        Missing To: header
>  2.9 NO_PRESCRIPTION        BODY: No prescription needed
>  0.1 DRUGS_ERECTILE         Refers to an erectile drug
>  1.4 MISSING_MIMEOLE        Message has X-MSMail-Priority, but no X-MimeOLE
>  0.1 TO_CC_NONE             No To: or Cc: header

Looks good.

> Another thing I found is that if mails have a score above 5 and therefore
> get marked as spam the subject gets not changed to *** SPAM *** as defined
> with $sa_spam_subject_tag, the subject will be SPAM FROM.

> It seems that Amavis or SpamAssassin are ignoring the $sa_* settings in the
> configuration files, no matter what I change.

> Regards,
>   Frank

Then I suspect you have a procmail recipe or other program calling spamassassin
after it leaves amavisd-new.

grep 'SPAM FROM' /etc/spamassassin/local.cf

Is spamd running? It should not be if you are using amavisd-new for
spam scanning. If it is running it may indicate some program has been
using it.

in /etc/default/spamassassin spamd should be turned off:
# Change to one to enable spamd
ENABLED=0

and spamd should be stopped:
/etc/init.d/spamassassin stop

> May 11 00:19:03 asterix amavis[20852]: (20852-01) Passed CLEAN, 
> [213.165.64.20]
> [84.158.46.189] <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>, Message-ID:
> <[EMAIL PROTECTED]>, mail_id: ay+4oblmBj1B, Hits: 0., 10227 ms

I admit I'm not sure what is happening here (Hits: 0.) but something
is broken. You should test send a message and capture the output of
'amavisd-new debug-sa' to see what amavisd-new has to say.

amavisd-new stop
amavisd-new debug-sa >/var/lib/amavis/1.log 2>&1 &
wait 15 seconds
send a test message (not gtube) and wait about 40 seconds
amavisd-new stop
amavisd-new start

less /var/lib/amavis/1.log

Are you running amavisd-new chrooted?
grep daemon_chroot_dir /etc/amavis/conf.d/*

I suggest you also set:
@debug_sender_maps = ( ['[EMAIL PROTECTED]'] );
and the first message you send to yourself after amavisd-new is
started up will log at level 5. This is a handy way to have a verbose
log without having to flip your log_level back and forth. Simply
reload amavisd-new to try again.

You should check for any amavisd-new errors in your mail.log:
grep '!' /var/log/mail.log

Gary V



-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to