> On Sat, 2006-12-16 at 08:28 +0200, Tomas Kuliavas wrote: > >> > >> > A real example: >> > =?iso-8859-1?Q?H=E5vard_Hegre=2C_UIO?= <[EMAIL PROTECTED]> >> >> SquirrelMail stores address in encoded form, but has to decode it in >> compose. When address is decoded, it no longer follows rfc 2822. >> > > So, are you saying that this is not anything that should be fix? > > Why all the other e-mail clients decode this address like this (1 > address)?: > TO: "Håvard Hegre, UIO" <[EMAIL PROTECTED]> > > and squirrelmail does this (2 addresses)? : > TO: "Håvard" Hegre, "UIO" <[EMAIL PROTECTED]>
String is not quoted in your example. When string is Q encoded, it is one word with encoded comma. When SquirrelMail decodes it, it becomes 'Håvard Hegre, UIO <[EMAIL PROTECTED]>'. If name is not quoted, comma splits it into two address entries. Fix is complex enough and requires review of deliver and mime classes -- Tomas ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- squirrelmail-users mailing list Posting Guidelines: http://www.squirrelmail.org/wiki/MailingListPostingGuidelines List Address: [email protected] List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
