Thanks for the help -

Now, although the Spam point value is working and I only get modified
subject line when it's over threshold, each and every message comes
through with the following - this is actualy from my confirmation note
to this list which had an X-Spam-Score of 0.3  (end cropped...)
---------
    X-Spam-Report:
                  Spam detection software, running on the system
"roadrunner.jlazyh.com", has
                  identified this incoming email as possible spam. The
original message has been
                  attached to this so you can view it ...
------------
    
It means that you have a global setting to add that report. Perhaps you
can adjust the intermediary program to add the header only if the score
is above the sitewide threshold?? I have no clue at all when it comes
to sendmail.
As I understand what Exim is trying to do, it is using 'spam' in the configure file to invoke spamassassin.  What is confusing me is that when I revert my system to sendmail, it still uses spamassasin 2.6 (obviously that's what I upgraded to), but the Spam-Report alters between the above and a more tame report that it's not spam.  
Aha, with Exim-4.24+Exiscan+spamd, you get a value called $spam_score_int
set for all mail that is passed through spamd.
Ok - and interestingly it looks like that is somehow different - Spamassasin used by sendmail reports a score of 497.3, whereass under Exim it comes back as 1000+.  Same default spam note that comes with spamassassin.  Any reason for why?
You can use that value to decide the report you want to add to the headers.

Something like


# Always add X-Spam-Flag, X-Spam-Score and X-Spam-Report headers, using SA system-wide
# settings (user "nobody"), if the message scores more than the system threshold (5.0)

warn  message        = X-Spam-Flag: Yes\n\
                       X-Spam-Score: $spam_score ($spam_bar)\n\
                       X-Spam-Report: $spam_report
      condition      = ${if >{$spam_score_int}{50}{1}{0}}
      spam           = nobody:true
Ok - does the "Yes\n\" option imply that it should respond with either a Yes or a No?   Before I just had YES, and it was affixed to each and every message that exim handled - even if the subject line was not altered, which only occured when it was true spam. (i.e. the modificiton to the subject line was the only apparent working feature.)

Do I have to set $spam_bar in the local.cf file for the application to know how to use it?


What I had was:
acl_check_data:
deny    message = This message contains malformed MIME ($demime_reason)
        demime = *
        condition = ${if >{$demime_errorlevel}{2}{1}{0}}

deny    message = This message contains wormish file extensions (.$found_extension)
        demime = scr:vbs:bat:lnk:pif

warn  message = X-Spam-Score: $spam_score ($spam_bar) {SCORE DOES VERY BASED ON SPAM OR HAM}
       condition = ${if <{$message_size}{80k}{1}{0}}
       spam = nobody:true

warn  message = X-Spam-Report: $spam_report   {ALWAYS SAYS PROBABLY SPAM}
       condition = ${if <{$message_size}{80k}{1}{0}}
       spam = nobody:true

warn  message = X-Spam-Flag: $spam_flag  {ALWAYS RETURNS AS YES}
       spam = nobody

warn  message = Subject: **SPAM -> $spam_score ** $h_subject {ONLY SPAM GETS FLAG AND POINTS AS EXPECTED}
       spam = nobody
accept

I do like local filters - have yet to try and set that up, as I should only have one thing screwed up at a time.   Have seen a few examples, but nothing that appeared plain and clear.

One other thing - is there a better way to start and stop exim rather than using the symbolic links to take over Sendmail?

Reply via email to