Hi!

I noticed a problem with non ASCII chars in a Subject of a message,
which is automatically answered by sieve/vacation.
Vacation reuses the original Subject line, but decodes the MIME in it
and sends out the decoded (8bit) subject without reencoding it.

So a message with "Subject: =?iso-8859-1?Q?T=E4st?=" (correct quoted
printable MIME encoding) is answered with "Subject: Täst" (8bit
without any MIME encoding).

Wouldn't it be better to simply reuse the original Subject without any
decoding?  Otherwise the decoded Subject needs to be newly MIME
encoded, doesn't it?

Tschoeeee

        Roland

Reply via email to