RFC 2047 encoding of mlmmj mails

RFC 2047 encoding of mlmmj mails

[Marcelo E. Magallón]

Hi,

first and foremost, thank you! mlmmj is really a joy!

I just finished translating my list/text/ files to Spanish (I can
contribute the translations if someone else is interested), and I ran
into a little problem.  The subject lines contain non-ASCII
characters, like this:

    Subject: Moderación requerida para $listaddr$

According to RFC 2047 that should read something like:

    Subject: =?UTF-8?Q?Moderaci=C3=B3n=20requerida=20para=20$listaddr?=

The problem is that after expanding $listaddr, the string will contain
full stop and at characters ("." and "@"), which is not allowed by
said RFC.

The second problem is with the body, since it needs to be encoded,
too.  My guess, after reading the source, is that writing:

    Subject: some subject
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable
    Content-Disposition: inline

    Some text...

takes cares of the problem, but I haven't tested this yet.

Thanks again,

Marcelo

Re: RFC 2047 encoding of mlmmj mails

[Csillag Tamás]

Hi,

On 06/22, Marcelo E. Magallón wrote:
> Hi,
> 
> first and foremost, thank you! mlmmj is really a joy!
> 
> I just finished translating my list/text/ files to Spanish (I can
> contribute the translations if someone else is interested), and I ran
> into a little problem.  The subject lines contain non-ASCII
> characters, like this:
> 
>     Subject: Moderación requerida para $listaddr$
> 
> According to RFC 2047 that should read something like:
> 
>     Subject: =?UTF-8?Q?Moderaci=C3=B3n=20requerida=20para=20$listaddr?=

You can solve this problem this way:
=?utf8?Q?Moderaci=C3=B3?=??=?utf8?Q?n?= requerida para $listaddr$
(this the way my mailer does)

AFAIK you do not need to encode the entire line.

-- 
Boy, backups sure are a lot faster since I linked /dev/st0 to /dev/null...

cstamas