On Mon, 12 Jul 2010, Michelle Konzack wrote:
From: Coupon Dept. CouponDeptdOS_V`CcOP
IW^GIdATOn2PbJK_/v...@perezcentral.com
I realize that the spammers will soon recognize that you are filtering
them, but for the moment, why not score heavily on the 'unusual'
characters inside these coded
header LOC_WEIRD_FROM From =~ /[...@\]*[\^\`\ ]...@\]*@/
# note: the '[...@\]*' confines the match to within a local address part
Using From:addr instead is better and more accurate. That RE is more
complicate than it needs to, yet might even match the real name. From is
not From:raw.
But I
On Mon, 12 Jul 2010, Karsten Bräckelmann wrote:
header LOC_WEIRD_FROM From =~ /[...@\]*[\^\`\ ]...@\]*@/
# note: the '[...@\]*' confines the match to within a local address part
Using From:addr instead is better and more accurate.
Provided the spammer doesn't use more than one address on the
On 11/07/10 16:04, Karsten Bräckelmann wrote:
On Sun, 2010-07-11 at 15:53 +0100, Cedric Knight wrote:
[nothing but 3 spam samples attached]
Uhm, dude!? I hope that was an accidental address auto-completion. Do
NOT send spam samples to the list.
Grovelling apologies. It was Thunderbird
On Tue, 2010-07-13 at 01:26 +0100, Cedric Knight wrote:
On 11/07/10 16:04, Karsten Bräckelmann wrote:
[nothing but 3 spam samples attached]
Uhm, dude!? I hope that was an accidental address auto-completion. Do
NOT send spam samples to the list.
Grovelling apologies. It was
