------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=126025 bernhard intevation de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhard intevation de, | |adam kde org Severity|normal |major Status|RESOLVED |UNCONFIRMED Priority|NOR |HI Platform|Mandriva RPMs |unspecified Resolution|WORKSFORME | ------- Additional Comments From bernhard intevation de 2006-04-28 18:25 ------- I am am reopening the bug, because I think the =?us-ascii?Q?Surname=2C=20Name?= encoding already is a phrase, thus there cannot be further encoding around it. This makes the behaviour a failure with major severity as this affect interoperability with other email clients that send this correct encoding (and have no other choice with non-ascii names). Here the reference to the interpretation: rfc2882 (proposed standard) 3.2.6. Miscellaneous tokens [..] word = atom / quoted-string phrase = 1*word / obs-phrase [..] 3.4. Address Specification [..] mailbox = name-addr / addr-spec name-addr = [display-name] angle-addr [..] display-name = phrase rfc2047 (draft standard) 5. Use of encoded-words in message headers [..] (3) As a replacement for a 'word' entity within a 'phrase', for example, one that precedes an address in a From, To, or Cc header. The ABNF definition for 'phrase' from RFC 822 thus becomes: phrase = 1*( encoded-word / word ) As you can see from the syntax definition above: phrase can have several words and encoded words. But only words can be quoted-strings with DQUOTE (") characters around them. encoded-words MUST not be enclosed by DQUOTE characters. _______________________________________________ KMail developers mailing list KMail-devel@kde.org https://mail.kde.org/mailman/listinfo/kmail-devel