Exim/Spamassassin

[flamewalker]

Hello,

I recently updated Exim and Perl, and since then, for some reason I can't seem to get the whitelist_domains file to work right. I have a domain I have entered in the /etc/virtual/whitelist_domains file in the format domain.com on each line, and now, for some reason, it seems to completely ignore it, and scans it with spamassassin (which thinks it's spam).

Any ideas where to look?

Any help greatly appreciated!
TIA,
Jamey

 

[nobaloney]

Did you also update your exim.conf file? Which one are you using? Show us top ten lines of exim.conf if you're not sure.

Jeff

 

[flamewalker]

I just updated to your spamblocker 4.2 and the latest (v15) of exim.pl to try to fix it. I checked the ownership of whitelist_domains and it's mail:mail, which appears to be correct.

I'm on the latest spamassassin as well.

Thanks,
Jamey

 

[flamewalker]

This is the spamassassin spam log:

Jan 30 09:46:37 vps spamd[7657]: spamd: result: Y 3 - AWL,HTML_IMAGE_ONLY_28,HTML_MESSAGE,HTML_MIME_NO_HTML_TAG,MIME_HTML_ONLY,MIME_QP_LONG_LINE,RP_MATCHES_RCVD,T_REMOTE_IMAGE scantime=9.3,size=3858,user=[domainuser],uid=503,required_score=2.5,rhost=localhost.localdomain,raddr=127.0.0.1,rport=34158,mid=<[email protected]>,bayes=0.208470,autolearn=no

I've whitelisted the ip in whitelist_hosts_ip, and tried variations of cjponyparts.com, zerolag.com, cjponyparts.ml.zerolag.com, but no matter what I do, it always scans it (and SA thinks it's spam).

spamassassin --lint doesn't show any errors.

I've tried google and the search here. Any guidance appreciated
Jamey

 

[nobaloney]

I read the the thread more carefully this time.

The whitelist file works only for SpamBlocker. Not for SpamAssassin. To whitelist through SpamAssassin you need to make settings at SpamAssassin at DirectAdmin user level.

Jeff

 

[flamewalker]

I read the the thread more carefully this time.

The whitelist file works only for SpamBlocker. Not for SpamAssassin. To whitelist through SpamAssassin you need to make settings at SpamAssassin at DirectAdmin user level.

Jeff

I thought the /etc/virtual/whitelist_* files were designed to make it skip essentially all checks, including spamassassin checks? I could have sworn it worked that way before?

 

[nobaloney]

Not since I wrote it. I suppose you could modify the code somehow to set a flag, and then based on that flag add enough positive score to end up whitelisting based on the flag, but it would require a separate change to SpamAssassin which would need to be maintained. Or perhaps a change to avoid running through SpamAssassin if the flag was set.

But it was my original design decision to keep SpamBlocker and SpamAssassin totally separate.

Jeff