On Tuesday, November 2, 2004, 1:10:15 PM, Alden Levy wrote:
Last week, I upgraded my server to FC1 (from RH 7.3). Sendmail, Ensim,
and
perl also got upgraded (to 8.12.x, 4.02, 5.8.1, respectively.
Before the upgrade, everything worked well with SA 3.0.0 and MaliScanner 4.34. Now, SURBL doesn't work unless I do some really strange things.
I've
reinstalled SA, MS, and ClamAV, but no joy. I've since upgraded to SA
3.0.1,
MS 4.35.9 and Mail::ClamAV 0.13. I already had ClamAV 0.80 installed.
spamassassin -D --lint works fine, and when I test spamassassin with a
SURBL
URL, it gives the expected output. I don't get hits with MailScanner
running
unless I put the contents of 25_uribl.cf into my spam.assassin.prefs.conf (which has a link from local.cf).
And my mail logs look fine, i.e., no errors, no MS restarts, etc.
Did you remember to change your URIBL rules from header to body?
Yep. I did this (I, too, had hoped that this would fix my problem). Any other thoughts?
Thanks.
Important Note Regarding SpamAssassin 3.0.1 and later: When adding URIDNSBL rules, including SURBL or SBL ones using urirhsbl, urirhssub or uridnsbl, be sure to set the rule type to body. For example:
urirhssub URIBL_JP_SURBL multi.surbl.org. A 64 body URIBL_JP_SURBL eval:check_uridnsbl('URIBL_JP_SURBL') describe URIBL_JP_SURBL Has URI in JP at http://www.surbl.org/lists.html tflags URIBL_JP_SURBL net
score URIBL_JP_SURBL 4.0
This is a change from SpamAssassin 3.0.0, where body above was previously header. Here is the changelog reference:
r54022 | felicity | 2004-10-07 22:21:30 +0000 (Thu, 07 Oct 2004) | 1 line
bug 3734: uridnsbl rules work on body data, not header data, so change the rule type from header to body
Jeff C.
On Tuesday, November 2, 2004, 8:17:30 PM, alden alden wrote:
On Tuesday, November 2, 2004, 1:10:15 PM, Alden Levy wrote:
Last week, I upgraded my server to FC1 (from RH 7.3). Sendmail, Ensim,
and
perl also got upgraded (to 8.12.x, 4.02, 5.8.1, respectively.
Before the upgrade, everything worked well with SA 3.0.0 and MaliScanner 4.34. Now, SURBL doesn't work unless I do some really strange things.
I've
reinstalled SA, MS, and ClamAV, but no joy. I've since upgraded to SA
3.0.1,
MS 4.35.9 and Mail::ClamAV 0.13. I already had ClamAV 0.80 installed.
spamassassin -D --lint works fine, and when I test spamassassin with a
SURBL
URL, it gives the expected output. I don't get hits with MailScanner
running
unless I put the contents of 25_uribl.cf into my spam.assassin.prefs.conf (which has a link from local.cf).
And my mail logs look fine, i.e., no errors, no MS restarts, etc.
Did you remember to change your URIBL rules from header to body?
Yep. I did this (I, too, had hoped that this would fix my problem). Any other thoughts?
You may want to post your SA startup on the SA discussion list.
Jeff C. -- "If it appears in hams, then don't list it."
On Tue, Nov 02, 2004 at 08:33:25PM -0800, Jeff Chan wrote:
Before the upgrade, everything worked well with SA 3.0.0 and MaliScanner 4.34. Now, SURBL doesn't work unless I do some really strange things.
I've
reinstalled SA, MS, and ClamAV, but no joy. I've since upgraded to SA
3.0.1,
MS 4.35.9 and Mail::ClamAV 0.13. I already had ClamAV 0.80 installed.
You may want to post your SA startup on the SA discussion list.
We're likely to first answer that we can't help with MailScanner. Try "spamassassin -D < some_message > /dev/null" from the commandline, and see what happens. If SURBL works there, it's MailScanner. If it doesn't, the debug should give you some hints.
The two main issues I've heard about are: not using a supported Net::DNS version, the install (or third party tool, or ...) not using init.pre to load the URIDNSBL module.
-
alden＠engineno9inc.com -
Jeff Chan -
Theo Van Dinter