Josh is right. Declude doesn't like seeing IP addresses in Message ID
headers.
Just to clarify, there were two problems with this E-mail:
[1] The Message-ID: header wasn't present when the E-mail was sent (it was
added by IMail after the E-mail was received). This caused the E-mail to
fail
Thanks a bunch for the clarification. It's just unfortunate that
programs that make the mistake of using an IP as a hostname and not
including a message ID end up failing so many important tests. I
recently been seeing about 2 different senders each week that will FP
for this reason (but no
Matt,
Do you have an updated version of your tests.
Thanks.
Fred
- Original Message -
From: Matthew Bramble [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 9:27 AM
Subject: Re: [Declude.JunkMail] Bad header question
Thanks a bunch for the clarification
After looking up the code, and then looking at the RFC
http://www.faqs.org/rfcs/rfc2822.html (which I hope is the right place)
I can't figure out what is bogus about the following header. What is
wrong with it? Was it inserted by IMAIL after the fact? If it was how
could I tell? I'd like to work
I believe that Message-ID: header was added by your IMail because the
email didn't have it. It failed the test because it should have had it
prior to IMail getting the email.
-Josh
On Sep 17, 2003, at 11:55 PM, Marc Catuogno wrote:
This E-mail has a bogus Message-ID: header.
Received: from
, September 17, 2003 11:55 PM
To: [EMAIL PROTECTED]
Subject: [Declude.JunkMail] Bad header question
After looking up the code, and then looking at the RFC
http://www.faqs.org/rfcs/rfc2822.html (which I hope is the right place)
I can't figure out what is bogus about the following header. What is
wrong
Josh is right. Declude doesn't like seeing IP addresses in Message ID
headers. I see FP's from BADHEADERS for the same. There's another
issue though...SPAMHEADERS get's triggered for exactly the same
reason. I found something buried in the release notes though that
allows you to make this only
