Ronald F. Guilmette:
>
> Pretend I'm an idiot. (For most people who know me this won't be hard.)
>
> Could somebody please explain to me... in a way that takes into account
> my idiocy... what this "strict_mime_encoding_domain" option actually does,
> i.e. if you turn it on?
It stops some malformed email: legitimate mail that is sent by
broken software, and junk that is sent by "ratware".
> What exactly constitutes "invalid Content-Transfer-Encoding: information
> for the message/* or multipart/* MIME content types" ?
Anything that does not say 7bit or 8bit.
The reason is that the MIME headers/boundaries INSIDE message/* or
multipart/* must not be obscured by some quoted-printable or base64
encoding.
Generally, any MIME type that triggers recursion MUST have
Content-Transfer-Encoding: of 7bit or 8bit; it can't be something
that corresponds to a transformation.
> Separate but perhaps related question:
>
> Assume that an incoming message includes the following header, either
> right in the initial headers, or else in the headers of some MIME subpart:
>
> Content-Transfer-Encoding: 7bit
>
> Assume further than one or more characters in the relevant MIME part
> actually have their high bits set. Does Postfix have any option that
> would cause the message in question to be either (a) rejected or else
> (b) flagged in some way?
That would be strict_8bitmime_body, or strict_8bitmime.
Wietse
