RE: [Declude.JunkMail] malformed message-id

[Andy Schmidt]

Harry,   how does ASPMail submit the messages? To "localhost" (like the IIS SMTP service of that web server) - or does it specify your Imail Server directly?   If it goes through the IIS SMTP service first, then you'll be able to see log information in the IIS log that might help.   If he specified your Imail Server in his ASPmail object (or if it's the system default for ASPmail), then I suggest looking at the Imail Log.   As Matt stated, the Message-ID line looks like one that Imail would have constructed by using it's own unique ID followed by a "@" and the name of the host in the HELO string.  By checking the Imail log, you should be able to SEE the HELO verb and whatever information is included with it.   I would NOT at all be surprised if ASPmail does NOT generate the Message-ID header be default.    Best Regards Andy Schmidt Phone:  +1 201 934-3414 x20 (Business) Fax:    +1 201 934-9206   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harry Vanderzand Sent: Thursday, June 15, 2006 04:10 PM To: declude.junkmail@declude.com Subject: RE: [Declude.JunkMail] malformed message-id Thanks Matt   This message comes straight from a form submission on one of my servers.  I think aspmail is being used.  My programmer says that it can't be caused by that and is blaming the SMTP server it is submitted to, which is my imail server   Harry Vanderzand inTown Internet & Computer Services 519-741-1222   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Thursday, June 15, 2006 3:27 PM To: declude.junkmail@declude.com Subject: Re: [Declude.JunkMail] malformed message-id 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. --- 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.