On søn 24 okt 2010 22:33:21 CEST, "Lawrence @ Rogers" wrote
I am writing a rule that deals with spam that claims to be coming
from AOL's webmail client, where the e-mail has malformed HTML,
references to remote images, and a high ratio of images to content.
I guess I will have to find anothe
On 24/10/2010 9:27 PM, Martin Gregorie wrote:
On Sun, 2010-10-24 at 18:03 -0230, Lawrence @ Rogers wrote:
On 24/10/2010 5:44 PM, Karsten Bräckelmann wrote:
There are perfectly valid reasons to not have the actual recipient in
the To header. Ever sent a message with Bcc recipients? Ever received
On Sun, 2010-10-24 at 18:03 -0230, Lawrence @ Rogers wrote:
> On 24/10/2010 5:44 PM, Karsten Bräckelmann wrote:
> > There are perfectly valid reasons to not have the actual recipient in
> > the To header. Ever sent a message with Bcc recipients? Ever received a
> > post via a mailing list?
> >
> >
On 24/10/2010 5:44 PM, Karsten Bräckelmann wrote:
On Sun, 2010-10-24 at 16:26 -0230, Lawrence @ Rogers wrote:
Is there a quick way to compare 2 headers? I am seeing spam lately that
has an invalid e-mail address (one not hosted by us) set in the To:
header, but has the intended one in the Envelo
On Sun, 2010-10-24 at 16:26 -0230, Lawrence @ Rogers wrote:
> Is there a quick way to compare 2 headers? I am seeing spam lately that
> has an invalid e-mail address (one not hosted by us) set in the To:
> header, but has the intended one in the Envelope-To: header
>
> What I would like to do is
