When I start evolution with a mailto url (as might happen when it is
started by a program sucha s mozilla when clicking on mailto urls),
evolution fails to decode the url correctly and also fails to _encode_ the
header on send.
Example:
evolution "mailto:chicia@sathoid.com?Subject=%3D%3Fiso-8859-1%3Fq%3FTest%3D20%3DFC%3DF6%3DE4%3D20hal%3F%3D%0D%0A%09%3D%3Fiso-8859-1%3Fq%3Fl%3DF6chen%3D3F%3D20oi%3D20yes%3D3F%3D20[Ticket%3D20103]%3F%3D"
This is simply a mailto: url for chicia@sathoid.com with a subject of
"Test üöä hallöchen? oi yes?"
Then evolution fails to decode the Subject header, and presents me with a
subject of (verbatim):
=?iso-8859-1?q?Test=20=FC=F6=E4=20hal?=
=?iso-8859-1?q?l=F6chen=3F=20oi=20yes=3F=20[Ticket=20103]?=
The two components are separated by \015\012\011, CRLF-Tab. The tab
is displayed as a space, while CRLF are displayed as boxed "0D" "0A"
characters (i.e. verbatim CRLF as displayed by pango).
When sending the mail, evolution fails to _encode_ the header
correctly. The mail looks like this:
Mime-Version: 1.0
Subject: =?iso-8859-1?q?Test=20=FC=F6=E4=20hal?=
=?iso-8859-1?q?l=F6chen=3F=20oi=20yes=3F=20[Ticket=20103]?=
That is, the subject line is copied verbatim into the RFC message,
including the control characters. Unfortunately, as the header happens to
be a valid mime header, any receiving program will correctly decode the
message header and end up with "Test üöä hallöchen? oi yes?", which is
not the content of the Subject field upon sending the mail.
So evolution fails to correctly "escape" at least the subject mail header
when sending mime mails.
I've got to say that this is the firts case of two mostly unrelated bugs
that cancel each other out, except for a display problem :)