Hmmm...Where does the problem lie, Declude or IMail? Has it been fixed in
post-1.75 Declude or post-8.01 IMail?
These account for about half of the 6% of spam that slips through my
current weighting. The rest I don't currently have tests for, but fixing
this alone would improve my results
]
Sent: Wednesday, January 28, 2004 11:19 PM
Subject: Re: [Declude.JunkMail] Strange message not marked as SPAM:
I don't think Declude will create a Subject header where none exists,
and if it won't create it, it won't append to it.
Matt
Rick Baranowski wrote:
Wanted to see if anybody could make
PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, January 28, 2004 11:19 PM
Subject: Re: [Declude.JunkMail] Strange message not marked as SPAM:
I don't think Declude will create a Subject header where none exists,
and if it won't create it, it won't append to it.
Matt
Rick Baranowski wrote:
to 97%.
Darin.
- Original Message -
From: Matt
To: [EMAIL PROTECTED]
Sent: Monday, February 02, 2004 12:03 AM
Subject: Re: [Declude.JunkMail] Strange message not marked as
SPAM:
Darin,Scott corrected me shortly after my post.
Declude does create a Subject line when none is found
I don't think Declude will create a Subject header where none exists, and
if it won't create it, it won't append to it.
Actually, Declude JunkMail is designed to add the Subject: header if it
does not exist. Although it does in our testing, we have had a few reports
of it not being added. We
Wanted to see if anybody could make any sense of this email that came
through. It had no subject, no from and no recipient. We have Declude
set to mark the subject with SPAM: if a weight of 20 is reached.
Didn't mark it at all. We have been received a couple of these over the
last couple of weeks.
