On Apr 5, 2004, at 6:47 PM, Michael Johnson wrote:
> On Apr 5, 2004, at 3:37 PM, Tor Slettnes wrote:
>
>>
>> On Apr 3, 2004, at 12:19, Michael Johnson wrote:
>>> I've set the part of my SA configuration for exim thusly:
>>> spamd_address = ###.###.###.### 783
>>
>> Ok. That's an option used by the 'spam' condition in Exiscan-ACL.
>
> I thought I had exiscan, but I may have screwed that up. It would
> appear so since when I comment out the router lines, it doesn't work.
Now, I know I've downloaded, patched exiscan, done make, and make
install. For some reason, it doesn't work. I've set it up to look at
the spamd_address on my other local server. I set it up as:
spamd_address - ip.num.of.svr 783
That's the same way it is on the other server except it's 127.0.0.1
instead of the real IP address.
If it is in fact scanning it, it's not putting the headers in showing
it was scanned. I have it set to in the ACL:
# Always add X-Spam-Score and X-Spam-Report headers, using SA
system-wide settings
# (user "nobody"), no matter if over threshold or not.
warn message = X-Spam-Score: $spam_score ($spam_bar)
spam = nobody:true
warn message = X-Spam-Report: $spam_report
spam = nobody:true
warn message = X-New-Subject: [***SPAM***] $h_subject:
spam = nobody
warn message = X-Virus-Scanned: Scanned with Clam AntiVirus
spam = nobody:true
warn message = X-Spam-Flag: YES
spam = nobody
>> - If it came via another MTA from a legitimate source, that other
>> MTA (presumably the sender's) would be able to send a bounce message
>> back to the sender (whose address is normally not forged).
>>
>> - If it came from spamware, no harm is done (spamware do not create
>> bounce messages).
>
> I'm guessing I need to recompile exim to do this.
Now, exim is recompiled. I'm not getting what I wanted. Where should
I start looking to find the fix?
-Michael
---------------------------------------
There will always be those who dare to take great risks. Rather than
mourn their loss, we should value their contributions.
--Jesse Brown
