Ouch... So the HELOBOGUS will apply the same logic and NO longer check for "BOGUS" host names?
If not - then why doesn't the same logic apply? Frankly, I rather prefer to have a test that does it advertises to do (e.g., check for "BAD HEADERS"), and then let ME decide via "weights", how highly I want to rate this. Remember: Nobody is forced to use the BADHEADERS test - but those who do should be able to 'rely' on it discovering non-compliancy. E.g., I might choose to use is as a NEGATIVE test, where I give email credit for having valid, compliant headers! For all other purposes you have the SPAMHEADERS test that is designed/advertised to be "flexible" and which is expected to "adopt" based on occurrence of certain issues in the "wild" - so THERE it would make sense to leave the MessageID FQDN check out of SPAMHEADERS. Best Regards Andy Schmidt H&M Systems Software, Inc. 600 East Crescent Avenue, Suite 203 Upper Saddle River, NJ 07458-1846 Phone: +1 201 934-3414 x20 (Business) Fax: +1 201 934-9206 http://www.HM-Software.com/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of R. Scott Perry Sent: Tuesday, June 03, 2003 03:34 PM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] Non-unique MessageID vs. BADHEADERS ? >Shouldn't this message ID cause a "BADHEADERS" failure: > >Message-ID: ><<mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED] n> > >since "athlon" is not guaranteed to be a unique occurrence (because >it's >not a FQDN)? Technically, it should. :) We used to have the BADHEADERS test check for this. However, the problem is that probably at least 1/2 of all mail clients are not RFC-compliant, in that they use a non-fully-qualified hostname ("athlon" rather than "athlon.example.com"). I just checked the last 3 personal E-mails I received, and all 3 had Message-ID: headers with a non-fully-qualified hostname. Although we normally like to push people into compliance, this is a war we won't be able to win. -Scott --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
