You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "Hackworth, Keith A" <Ke...@BELLSOUTH.COM> on 2004/05/05 14:18:04 UTC

Bug in Spamcop's surbl add-on module

I found a problem with SpamCop's surbl lookup add-on.  I was installing
a new mail server and testing the surbl lookups, but my test kept
getting through not being marked as spam.  The test I was using was
http://e.1asphost.com - this is on the be.surbl.org list.  After
tinkering around a bit, and reinstalling the surbl add-on with no
success, I finally figured out what's going on.  My logs show that the
system is looking up 1asphost.com, which is NOT on the list.  For some
reason, it stripped off the "e."

It seems that spamcop's surbl doesn't handle subdomains at all.  Anyone
else seeing this?

Thanks,
Keith Hackworth

*****
"The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material.  Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.  If you received this in error, please contact the sender and delete the material from all computers."  113


Re: failed to parse line

Posted by Matt Kettler <mk...@comcast.net>.
At 03:20 PM 5/5/04 +0200, milari@enter.it wrote:

>debug: Failed to parse line in SpamAssassin configuration, skipping: 
>report_header^I0
>debug: Failed to parse line in SpamAssassin configuration, skipping: 
>defang_mime^I0
>debug: Failed to parse line in SpamAssassin configuration, skipping: spam_fwd
>debug: Failed to parse line in SpamAssassin configuration, skipping: 
>spam_enabled^I1
>debug: Failed to parse line in SpamAssassin configuration, skipping: 
>spam_trash^I0
>
>the structure table and parameters are correct and there aren't
>strange chars in the strings.

Regardless of strange characters, none of those are legal config options.

defang_mime and report_header are deprecated, see report_safe.

spam_fwd, spam_enabled and spam_trash have, as far as I know, never been SA 
config options.



failed to parse line

Posted by mi...@enter.it.
hi all
i recently activated spamassassin with sql userpref but every time it
takes rules from db I receive this error:

debug: retrieving prefs for xxxxx@xxx.xxx from SQL server
debug: Failed to parse line in SpamAssassin configuration, skipping: report_header^I0
debug: Failed to parse line in SpamAssassin configuration, skipping: defang_mime^I0
debug: Failed to parse line in SpamAssassin configuration, skipping: spam_fwd
debug: Failed to parse line in SpamAssassin configuration, skipping: spam_enabled^I1
debug: Failed to parse line in SpamAssassin configuration, skipping: spam_trash^I0

the structure table and parameters are correct and there aren't
strange chars in the strings.

someone can help me?

thanks


Re: Bug in Spamcop's surbl add-on module

Posted by Jeff Chan <je...@surbl.org>.
On Wednesday, May 5, 2004, 5:18:04 AM, Keith Hackworth wrote:
> I was installing
> a new mail server and testing the surbl lookups, but my test kept
> getting through not being marked as spam.  The test I was using was
> http://e.1asphost.com - this is on the be.surbl.org list. ...
> My logs show that the
> system is looking up 1asphost.com, which is NOT on the list.  For some
> reason, it stripped off the "e."

> It seems that spamcop's surbl doesn't handle subdomains at all.  Anyone
> else seeing this?

Hmm, it is indeed in BigEvil with the e. :

bigevil.cf:uri BigEvilList_181     /\b(?:extreme-rapes\.com|excaliburproducts\.c
om|evansezmoney\.estarnetwork\.com|enjoyadvanced097\.org|emedorders\.com|email\.
homemadesimple\.com|ehostzzz\.net|e-g\.com|efreedomweb\.net|ecredibledeals\.com|
echofrompeople\.com|e\.1asphost\.com)\b/i

and it's therefore making it into be.surbl.org with the e. :

bigevil.domains:e.1asphost.com

However we should be taking off the subdomain before it goes into
the SURBL form.  I'll need to check with Chris on how we can
handle that.

BTW, SURBL is not a SpamCop project, although we are using
SpamCop URI domains as a data source in the sc.surbl.org list.

Jeff C.
-- 
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/