NFN Smith wrote:
Lawrence @ Rogers wrote:
Are you running it against an e-mail with a known match? Using
spamassassin -D -t sample-spam.txt and having sample-spam.txt contain
the complete e-mail including headers?
Yes, it's a known match. I can take a full copy of a received message
(with h
Lawrence @ Rogers wrote:
Are you running it against an e-mail with a known match? Using
spamassassin -D -t sample-spam.txt and having sample-spam.txt contain
the complete e-mail including headers?
Yes, it's a known match. I can take a full copy of a received message
(with headers, although m
On Fri, 29 Oct 2010, NFN Smith wrote:
I'm seeing some amount traffic with obfuscated content in To: lines,
where the display name is shown as a angled bracket. For example:
To: "<"
Just FYI, I have a rule for that in my sandbox. It hit six messages in the
current nightly masscheck spam c
On 29/10/2010 4:06 PM, NFN Smith wrote:
Lawrence @ Rogers wrote:
On 29/10/2010 3:32 PM, NFN Smith wrote:
header LR_OBSC_RECIPS To =~ /\"\<\"/
Is this rule being used standalone, or as part of a meta rule? Do you
have a score declared for it? If so, what is it?
Right now, I'm scor
Lawrence @ Rogers wrote:
On 29/10/2010 3:32 PM, NFN Smith wrote:
header LR_OBSC_RECIPS To =~ /\"\<\"/
Is this rule being used standalone, or as part of a meta rule? Do you
have a score declared for it? If so, what is it?
Right now, I'm scoring at 1.25 points. Thus, it's not a hid
On 29/10/2010 3:32 PM, NFN Smith wrote:
header LR_OBSC_RECIPS To =~ /\"\<\"/
Is this rule being used standalone, or as part of a meta rule? Do you
have a score declared for it? If so, what is it?
Does spamassassin --lint report any errors at the end of its output?
Cheers,
Lawrence
I'm seeing some amount traffic with obfuscated content in To: lines,
where the display name is shown as a angled bracket. For example:
To: "<"
I've been playing with a rule to identify this particular pattern (and
score in metas):
header LR_OBSC_RECIPS To =~ /\"\<\"/
When r
