[Tickets #1352] 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
 Updated By         | Michael Slusarz <slusarz at mail.curecanti.org>
 Summary            | MIME::encodeAddress() (implicitly) enforce RFC822 format checking before RFC2047 encoding
 Queue              | Horde Framework Packages
-State              | Bogus
+State              | Accepted
-Priority           | 2. Medium
+Priority           | 1. Low
 Type               | Bug
 Owners             | Horde Developers, Michael Slusarz
-----------------------------------------------------------------------


Michael Slusarz <slusarz at mail.curecanti.org> (2005-04-04 22:38) wrote:

You are probably correct - we should handle an error returned from
Mail_RFC822 much cleaner in MIME::encodeAddress().  Namely, we should return
a PEAR_Error from encodeAddress() if an error is encountered. 
MIME::encodeAddress() is used all over the place, though, so there's quite a
bit of code to patch.  Additionally, this might break BC since, when before
MIME::encodeAddress() was returning an empty string, now it will be
returning a PEAR_Error.  I think I need to think about this a bit more.