[Dovecot] problem with charset and encoding

[Steffen Kaiser]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 6 Mar 2013, Héctor Moreno Blanco wrote:

> We are having some troubles since we updated dovecot from 2.0.10 to 2.1.6.

Did you upgraded the mail storage, too?

> With 2.0.10 with messages with this headers:
>
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
>
> Showed the special characters fine. However, with this new version, there are special characters that are not correctly showed.
>
> For example:
>
> "Su c=F3digo de activaci=F3n "   must be "Su código de activación ", but in all email clients, even in webmail, is showed like the first way without decoding it.

Do the messages look wired in other ways, e.g. do they have header lines 
at top?

> Maybe some configuration or libraries I missed?

No, I don't think so. The client renders the message, Dovecot should not 
alter its content.

Do this happen for new accounts, too? If not, maybe you need to remove the 
old cache files.

What mail storage do you use? With Maildir you could easily create a new 
mailbox and drop a file with:

==== START
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Test
Message-ID: <test2344434 at localhost>

Su c=F3digo de activaci=F3n
====END

there then view it with a client.

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEVAwUBUThefF3r2wJMiz2NAQJ9vQgAri6lB/a7UhtzgLQKG7TykMWV+4ZXBRRj
7KKozbAwD123QDfTpKC+TsD93XMENz4tQ6qTN6fjrUTV6nZfp74FfHu7XVki1XeU
x52J4msbU6al6kc/BVboaUXB88WYUVX1DTFPQuLtyowkV9EJibRPRFtx/TnyHBfz
phWGnGL4p4HgnljnJSJe1cM9k4m/tsSu+Ts2PMBFU0cewBRcSDzY9QkBvxjTkKZ0
g3q+NSDaCKBW2AS1kIhuBW0Yg0yMKARgcAKy2O2LBY2YKnzVnl4rcgscvn5z90H6
M7HIdx6uUW0CnqGTYzz0FzmkMY9QYr+GHt/bcncC8dVkbm3fsHVmXA==
=94XE
-----END PGP SIGNATURE-----