Re: [Declude.JunkMail] malformed message-id

[Matt]

Looks like an IMail inserted Message-Id header, so in part it is their problem.  I suspect that the trigger though is the sender having an invalid HELO, which IMail is then mishandling.  It could have also been a hickup unless it is repeatable with the same source. The HELO, MAIL FROM and RCPT TO should all have only US-ASCII printable characters (excluding space).  Anything beyond that is invalid on it's own, and IMO, the MTA should issue a 5xx error when received indicating as much. Matt Harry Vanderzand wrote:   I am having a problem where the message-id is malformed which trips up some clients. see: Message-Id: <200606131300275.SM04448@ > X-Declude-Sender: [EMAIL PROTECTED] [216.16.233.16] Notice the the closing bracket is on a separate line. This causes the headers to become part of the body for some of my clients. Has anyone seen this before?  Is it an imail issue or a declude issue? Harry Vanderzand inTown Internet & Computer Services 11 Belmont Ave. W., Kitchener, ON,N2M 1L2 519-741-1222   --- 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. --- 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.