On Friday, July 23, 2004, 6:26:33 AM, Gerry Doris wrote:
> I am running sa 2.63 and decided to try out SURBL. I used CPAN to
> install the URI and SpamCopURI modules. They installed without
> problems.
> However, when I run the spamassassin --lint command I get the following
> errors...
> Failed to parse line in SpamAssassin configuration, skipping:
> open_redirect_list_spamcop_uri snurl.com *.snurl.com
> Failed to parse line in SpamAssassin configuration, skipping:
> open_redirect_list_spamcop_uri snipurl.com *.snipurl.com
> Failed to parse line in SpamAssassin configuration, skipping:
> open_redirect_list_spamcop_uri tinyclick.com *.tinyclick.com
> Failed to parse line in SpamAssassin configuration, skipping:
> open_redirect_list_spamcop_uri babyurl.com *.babyurl.com
> Failed to parse line in SpamAssassin configuration, skipping:
> open_redirect_list_spamcop_uri lin.kz *.lin.kz
> Failed to parse line in SpamAssassin configuration, skipping:
> open_redirect_list_spamcop_uri *.v3.net
> Failed to parse line in SpamAssassin configuration, skipping:
> open_redirect_list_spamcop_uri shorl.com *.shorl.com
> Failed to parse line in SpamAssassin configuration, skipping:
> open_redirect_list_spamcop_uri tinyurl.com *.tinyurl.com
> Failed to parse line in SpamAssassin configuration, skipping:
> open_redirect_list_spamcop_uri xurl.us
You can ignore those. They are simply the redirection site
resolver being disabled by default.
> and...
> debug: running uri tests; score so far=2.077
> debug: uri tests: Done uriRE
> Failed to compile URI SpamAssassin tests, skipping:
> (syntax error at /etc/mail/spamassassin/surbl_uri.cf, rule
> SPAMCOP_URI_RBL, line 1, near "eval:"
> syntax error at /etc/mail/spamassassin/surbl_uri.cf, rule OB_URI_RBL,
> line 1, near "eval:"
> syntax error at /etc/mail/spamassassin/surbl_uri.cf, rule OB_URI_RBL,
> line 9, near "}
> }"
> )
> The rest of the --lint output is correct. Removing the surbl.cf file
> and rerunning --lint is error free.
> I'm using the following surbl.cf file...the eval lines have likely
> wrapped.
Yes, the lines have wrapped. De-wrap them as follows and they
should work (without the >s of course):
> # please see www.surbl.org for more information
> ######### ab.surbl.org #########
> uri AB_URI_RBL eval:check_spamcop_uri_rbl('ab.surbl.org','127.0.0.2')
> describe AB_URI_RBL URI's domain appears in ab.surbl.org
> tflags AB_URI_RBL net
> score AB_URI_RBL 5.0
> ######### sc.surbl.org #########
> uri SPAMCOP_URI_RBL
> eval:check_spamcop_uri_rbl('sc.surbl.org','127.0.0.2')
> describe SPAMCOP_URI_RBL URI's domain appears in spamcop database at
> sc.surbl.org
> tflags SPAMCOP_URI_RBL net
> score SPAMCOP_URI_RBL 3.0
> # open redirect resolution off by default
> # spamcop_uri_resolve_open_redirects 1
> open_redirect_list_spamcop_uri snurl.com *.snurl.com
> open_redirect_list_spamcop_uri snipurl.com *.snipurl.com
> open_redirect_list_spamcop_uri tinyclick.com *.tinyclick.com
> open_redirect_list_spamcop_uri babyurl.com *.babyurl.com
> open_redirect_list_spamcop_uri lin.kz *.lin.kz
> open_redirect_list_spamcop_uri *.v3.net
> open_redirect_list_spamcop_uri shorl.com *.shorl.com
> open_redirect_list_spamcop_uri tinyurl.com *.tinyurl.com
> open_redirect_list_spamcop_uri xurl.us
> # whitelist_spamcop_uri *.yahoo.com
> # blacklist_spamcop_uri *medz4cheap.com
> ######### ob.surbl.org #########
> uri OB_URI_RBL eval:check_spamcop_uri_rbl('ob.surbl.org','127.0.0.2')
> describe OB_URI_RBL URI's domain appears in ob.surbl.org
> tflags OB_URI_RBL net
> score OB_URI_RBL 4.0
> ######### ws.surbl.org #########
> uri WS_URI_RBL eval:check_spamcop_uri_rbl('ws.surbl.org','127.0.0.2')
> describe WS_URI_RBL URI's domain appears in sa-blacklist
> tflags WS_URI_RBL net
> score WS_URI_RBL 3.0
Jeff C.
--
Jeff Chan
mailto:[EMAIL PROTECTED]
http://www.surbl.org/
