From: Victor Duchovni (no email)
Date: Wed Aug 11 2004 - 13:51:51 EDT
On Wed, Aug 11, 2004 at 01:19:05PM -0400, Wietse Venema wrote:
> Nicolas Riendeau:
> > Hi Mr Venema!
> >
> > Wietse Venema wrote:
> > > Why do you believe this is the case? Just provide a template file
> > > with the proper Content-Type: header.
> > >
> > > Of course no-one is going to figure out what the template should
> > > look like if it contains non-ASCII content.
> > >
> > > Wietse
> > >
> >
> > My patch is essentially ready (just have to write a little something to describe its
> > use) but what you said above got me thinking.
> >
> > Should The non-ASCII content in the template file be typed in quoted-printable or
> > should it be 8-bit characters (which I believe Postfix is able to convert to
> > quoted-printable if the other server doesn't support 8 bit (8BITMIME?).
>
> As long as the MIME attributes are specified correctly, then it
> will work.
>
> However, I am worried that most people will not know what MIME info
> to specify, and that Postfix will have to actively inspect for
> obvious bogosity. But it would never be able to figure out charset
> violations.
>
Leaving the content at 8bit is fine though somewhat limiting (splitting
long lines, portability problems with buggy intermediate MTAs, ...), the
key is to use a charset that includes ASCII as an identity encoded subset.
I would personally recommend quoted-printable for 8bit text, but this is
optional, so long as the charset is correct. Note that including an 8bit
text/plain entity contained in a multipart/report, requires a content
transfer encoding of "8bit" also for the enclosing multipart/report
message.
-- 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:?body=unsubscribe%20postfix-users>
|
|
|