Re: [Declude.JunkMail] Bad header question

[Matthew Bramble]

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 fail BADHEADERS: -----Global.cfg----- LOOSENSPAMHEADERS    ON That ought to help a little. Matt Joshua Levitsky wrote: 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 209.182.0.220 [209.182.0.220] by mail.prudentialrand.com   (SMTPD32-7.15) id AED620400B4; Wed, 17 Sep 2003 22:56:22 -0400 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_106382928816106116372" MIME-Version: 1.0 X-Mailer: MIME::Lite 3.01 (F2.6; A1.17; B2.20; Q2.20) Date: Wed, 17 Sep 2003 20:08:08 UT From: RIS Media <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: [SPAM]Housing Starts Fall in August X-Streamsendid: 3+1+135073+10+lists.streamsend.com Message-Id: <[EMAIL PROTECTED]>