You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Mike Hogsett <ho...@csl.sri.com> on 2004/05/28 20:06:33 UTC
Message-ID format
I have observed the following format for the Message-ID in 350 of 5992
spam messages (5.84%) and 0 of 3523 non-spam.
'<[A-Z]{21}@'
e.g.
[beast] [hogsett] [~/Mail/spam]
--> egrep '<[A-Z]{21}@' * | head -n 20
1029:Message-Id: <SK...@aol.com>
1029:Message-ID: <SK...@aol.com>
1055:Message-Id: <WP...@cool.ne.jp>
1055:Message-id: <WP...@cool.ne.jp>
1067:Message-Id: <GP...@stieykpn.ac.id>
1067:Message-ID: <GP...@stieykpn.ac.id>
1068:Message-Id: <AD...@hotmail.com>
1068:Message-ID: <AD...@hotmail.com>
1124:Message-Id: <JM...@msn.com>
1124:Message-ID: <JM...@msn.com>
1168:Message-Id: <EA...@tbwt.com>
1168:Message-ID: <EA...@tbwt.com>
1172:Message-Id: <FN...@sdr5f5.com>
1172:Message-ID: <FN...@sdr5f5.com>
1184:Message-Id: <HF...@hotmail.com>
1184:Message-ID: <HF...@hotmail.com>
1199:Message-Id: <TD...@msn.com>
1199:Message-id: <TD...@msn.com>
1200:Message-Id: <CF...@msn.com>
1200:Message-ID: <CF...@msn.com>
Are any of you seeing similar behaviour? I may install this as a SA
rule, but would like to hear feedback first.
- Mike
Re: SpamCopURI+ --lint
Posted by Jeff Chan <je...@surbl.org>.
On Saturday, May 29, 2004, 3:11:32 AM, Cami Cami wrote:
> I'm using the SA Mail-SpamAssassin-SpamCopURI-0.17 plugin,
> (i've installed the packages required) and i'm getting the
> following errors when running spamassassin --lint:
> [spamwall12][/root]# spamassassin --lint
> Failed to parse line in SpamAssassin configuration, skipping:
> spamcop_uri_resolve_open_redirects 1
> Failed to parse line in SpamAssassin configuration, skipping:
> open_redirect_list_spamcop_uri drs.yahoo.com
[...]
> Failed to parse line in SpamAssassin configuration, skipping:
> open_redirect_list_spamcop_uri xurl.us
> Failed to compile URI SpamAssassin tests, skipping:
> (syntax error at /etc/mail/spamassassin/spamcop_uri.cf, rule
> WS_URI_RBL, line 1, near "eval:"
> syntax error at /etc/mail/spamassassin/spamcop_uri.cf, rule
> SPAMCOP_URI_RBL, line 1, near "eval:"
> syntax error at /etc/mail/spamassassin/spamcop_uri.cf, rule
> SPAMCOP_URI_RBL, line 6, near "}
> }"
> )
> Is this something to worry about? (i thought --lint should
> not return any errors..)
Hi Cami,
This may be a result of the open redirect resolution being
disabled by default, but you may want to ask it on the SURBL
discussion list, where Eric Kolve, the author of SpamCopURI,
and other SpamCopURI users can respond to it.
Also I'd suggest using the 0.18 version of SpamCopURI, which
has a bug fix or two.
Jeff C.
--
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/
SpamCopURI+ --lint
Posted by Cami <ca...@mweb.co.za>.
Hi All,
I'm using the SA Mail-SpamAssassin-SpamCopURI-0.17 plugin,
(i've installed the packages required) and i'm getting the
following errors when running spamassassin --lint:
[spamwall12][/root]# spamassassin --lint
Failed to parse line in SpamAssassin configuration, skipping:
spamcop_uri_resolve_open_redirects 1
Failed to parse line in SpamAssassin configuration, skipping:
open_redirect_list_spamcop_uri drs.yahoo.com
Failed to parse line in SpamAssassin configuration, skipping:
open_redirect_list_spamcop_uri rd.yahoo.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 google.com *.google.com
Failed to parse line in SpamAssassin configuration, skipping:
open_redirect_list_spamcop_uri xurl.us
Failed to compile URI SpamAssassin tests, skipping:
(syntax error at /etc/mail/spamassassin/spamcop_uri.cf, rule
WS_URI_RBL, line 1, near "eval:"
syntax error at /etc/mail/spamassassin/spamcop_uri.cf, rule
SPAMCOP_URI_RBL, line 1, near "eval:"
syntax error at /etc/mail/spamassassin/spamcop_uri.cf, rule
SPAMCOP_URI_RBL, line 6, near "}
}"
)
Is this something to worry about? (i thought --lint should
not return any errors..)
Regards,
Cami
Re: Message-ID format
Posted by Robert Menschel <Ro...@Menschel.net>.
Hello Mike,
Friday, May 28, 2004, 11:06:33 AM, you wrote:
MH> I have observed the following format for the Message-ID in 350 of 5992
MH> spam messages (5.84%) and 0 of 3523 non-spam.
MH> '<[A-Z]{21}@'
MH> e.g.
MH> --> egrep '<[A-Z]{21}@' * | head -n 20
MH> 1029:Message-Id: <SK...@aol.com>
MH> 1029:Message-ID: <SK...@aol.com>
I did my egrep on: Message-ID:\s+<[A-Z]{17,}\@
Hit 196 spam (0.4% of my corpus), the most recent being this afternoon,
the oldest from April 6. Hit no ham.
Bob Menschel