[Tickets #1352] NEW: MIME::encodeAddress() (implicitly) enforce RFC822 format checking before RFC2047 encoding

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1352
-----------------------------------------------------------------------
 Ticket     | 1352
 Created By | rafan at csie.org
 Summary    | MIME::encodeAddress() (implicitly) enforce RFC822 format checking before RFC2047 encoding
 Queue      | Horde Framework Packages
 State      | Unconfirmed
 Priority   | 2. Medium
 Type       | Bug
 Owners     | 
-----------------------------------------------------------------------


rafan at csie.org (2005-02-10 09:55) wrote:

When composing mail in IMP, eventually  imp/lib/Compose.php
calls MIME::encodeAddress() which has the following code segment:

        require_once 'Mail/RFC822.php';
        $parser = &new Mail_RFC822();
        $addr_arr = $parser->parseAddressList($text, $defserver, false,
false);

The code segment above is BEFORE it does RFC2047 encoding.
The problem is Mail_RFC822's parseAddressList() will enforce
strict RFC822 format checking. For some multibyte characters, like Big5,
there is \ or ' in chatacter. So, these characters can not fulfill RFC822
format.

This has been discussed in imp mailing (2004 Aug to Oct) with the
thread: " [imp] address book -> compose window ". 

Yes, it's a long time ago, but I was too busy that time, so here is the
ticket.

By the way, I just found that long time ago there already a _rfc822explode
like function called 'rfc822Explode()' in MIME.php (imported in rev 1.78, 2
years ago). So, I think this is a point that we can start from.