Thanks for the explanation, Scott. To get really specific, did Declude "fix up" the e-mail by adding in the missing Date: header, or did IMail? It sounds like a Good Thing(tm) but I'm looking for the law of unintended consequences.
My bet is that you won't modify any content in the header, but you might amend it by adding a missing required RFC line, or by fixing up the blank line spacing the header, MIME header and body... And yes, I do whitelist abuse@ and postmaster@, so there was no mystery about receiving this message. Andrew 8) -----Original Message----- From: R. Scott Perry [mailto:[EMAIL PROTECTED]] Sent: Monday, January 13, 2003 5:23 AM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] Mimeserver and MIME encoding problems? >here, off the list, and submit a message I received this weekend. What is >unusual about it is that the header has all the X- entries before the date >entry. The Date: header appeared at the end of the E-mail because it was sent without a Date: header. As for why you received the spam, it's because you whitelisted it. If you take a look at all your WHITELIST entries, you'll see that it is whitelisted (it looks like you are whitelisting all E-mail to [EMAIL PROTECTED]). -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.
