OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: Additional headers when using pipe transport

From: Wietse Venema (wietseporcupine.org)
Date: Fri Mar 13 2009 - 06:52:48 CDT


Christian Ludwig:
> Hello,
>
> Wietse Venema:
> > Your original message looks like this:
> >
> > > |Content-Type: multipart/alternative;
> > > |boundary="----_=_NextPart_001_01C9A2F0.A8C3BC75"
> > > |Subject: Another test
> > > |Date: Thu, 12 Mar 2009 09:58:07 +0100
> > > |Message-ID: <DF498BD044718142BAoriginalmail.somewhere.com>
> > > |From: Somebody <somebodyanotherdomain.com>
> > > |To: <recipienttargetdomain.com>
> >
> > This is not a correctly formed message header. In particular,
> > the Content-Type: header is broken.
>
> Ah, I see. I double-checked the original message and it has a "." in
> front of "boundary" so that it says
>
> |Content-Type: multipart/alternative;
> |.boundary="----_=_NextPart_001_01C9A2F0.A8C3BC75"
>
> So this is another detail, which has changed from the original message
> when I get it piped from postfix. Thank you for pointing this out.

That looks like an improper implementation of the "initial dot
stuffing" algorithm of SMTP.

See RFC5321 for how this is done correctly.
http://tools.ietf.org/html/rfc5321#section-4.5.2

        Wietse