From: Victor Duchovni (Victor.DuchovniMorganStanley.com)
Date: Tue Feb 27 2007 - 15:43:05 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, Feb 27, 2007 at 01:35:43PM -0800, Shain Miley wrote:

> Hello everyone,
> I have an issue with postfix that I cannot seem to resolve...I have done a bit of looking around but have been unable to find a solution.
>
> We recently switched from using sendmail to postfix on our mail server....after this switch we started seeing some odd characters show up in some of our mail. So far we are seeing the characters '=20' at the end of some lines...can anyone tell me why we are seeing these all the sudden, and does anyone know of a way of getting rid of them...I thought about trying to strip them out...but on the off chance that there really is a legit '=20' in some messages...I would rather not do that, instead I want to fix the problem before it occurs.
>

RFC 2045 describes MIME fundamentrals qnd the quoted-printable and Base64
Content Transfer Encoding. RFC 1652 describes 8bitmime handling with ESMTP:

   Once a server SMTP supporting the 8bit-MIMEtransport service extension
   accepts a content body containing octets with the high- order (8th)
   bit set, the server SMTP must deliver or relay the content in such
   a way as to preserve all bits in each octet.

   If a server SMTP does not support the 8-bit MIME transport extension
   (either by not responding with code 250 to the EHLO command, or by
   not including the EHLO keyword value 8BITMIME in its response), then
   the client SMTP must not, under any circumstances, attempt to transfer
   a content which contains characters outside the US-ASCII octet range
   (hex 00-7F).

   A client SMTP has two options in this case: first, it may implement
   a gateway transformation to convert the message into valid 7bit
   MIME, or second, or may treat this as a permanent error and handle
   it in the usual manner for delivery failures. The specifics of the
   transformation from 8bit MIME to 7bit MIME are not described by this
   RFC; the conversion is nevertheless constrained in the following ways:

      (1) it must cause no loss of information; MIME transport
           encodings must be employed as needed to insure this is the
           case, and

      (2) the resulting message must be valid 7bit MIME.

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomopostfix.org?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]