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

Hi,

after Marc fixed Bug#30036 I read a little bit in RFC 2047 and I think 
I found a violation of this RFC in KMail.

The RFC says in section "5. Use of encoded-words in message headers":
- -----
+ An 'encoded-word' MUST NOT appear within a 'quoted-string'.
- -----

And it section 7. we have the following:
- -----
7. Conformance
 
   A mail composing program claiming compliance with this specification
   MUST ensure that any string of non-white-space printable ASCII
   characters within a '*text' or '*ctext' that begins with "=?" and
   ends with "?=" be a valid 'encoded-word'.  ("begins" means: at the
   start of the field-body, immediately following 'linear-white-space',
   or immediately following a "(" for an 'encoded-word' within '*ctext';
   "ends" means: at the end of the field-body, immediately preceding
   'linear-white-space', or immediately preceding a ")" for an
   'encoded-word' within '*ctext'.)  In addition, any 'word' within a
   'phrase' that begins with "=?" and ends with "?=" must be a valid
   'encoded-word'.
- -----

But currently
	"foobär" <foobaer@localhost>
is encoded as
	"=?iso-8859-1?q?foob=E4r?=" <foobaer@localhost>
while according to the RFC it must be encoded as
	=?iso-8859-1?q?=22foob=E4r=22?= <foobaer@localhost>
where the =22s are the encoded double quotes.

Regards,
Ingo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7Zx4QGnR+RTDgudgRAuKMAKCqfvpWFMM8cDYUplc/tf0XFrak6gCfapcF
nidJ11emZHKm2JI82ArMH/c=
=fRim
-----END PGP SIGNATURE-----
_______________________________________________
Kmail Developers mailing list
Kmail@master.kde.org
http://master.kde.org/mailman/listinfo/kmail