From: Nicolas Riendeau (no email)
Date: Sat Aug 07 2004 - 12:48:15 EDT
Hi Victor!
Victor Duchovni wrote:
> On Wed, Aug 04, 2004 at 10:38:05PM -0400, Nicolas Riendeau wrote:
>
>
>>Hi Mr Venema!
>>
>>Wietse Venema wrote:
>>
>>>This text should also have provision for content-type and character
>>>set information if that is needed. It should not provide other MIME
>>>headers so as not to mess up the DSN message format.
>>
>>I have one (small?) problem with this...
>>
>>Everything generated by Postfix (including any $ macros) assume a
>>normal (7 bit?) character set.
>
>
>
> Content-Type: text/plain; charset=iso-8089-1
> Content-Transfer-Encoding: quoted-printable
>
> Testing, =31, =32, =33...
(-; (-; (-;
You know that wasn't what I meant (or maybe you didn't?). Anyway, that was pretty
funny...
Even though this in encoded in quoted-printable, the characters used to encode are
still ASCII characters...
>
>
>
>>The ouput of bounce_recipient_log() is in the same "part" as
>>bounce_boilerplate()
>>which means *I think* that it must be in the same character set? How should
>>I
>>handle this? Should I put it in another part if character set is specified
>>(or
>>do I do that always) or is there another trick I could use?
>
>
> The multipart/report MIME type consists of *exactly* three parts, with the
> first a text/plain.
>
> The charset that contains the error message must contain ASCII as an
> identity encoded subset. To encode asian character sets, ... you must use
> utf-8 rather than gb2332 or shift-jis, ...
>
Thanks!!! That was the part I was missing (that's why I said something along the lines
of "is there any trick I should use?" in one of my previous messages).
I have not played with utf-8/Unicode before so I didn't know about its backward ASCII
compatibility.
Thanks and have a nice day!
Nick
|
|
|