[Tickets #1352] RESOLVED: 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         | rafan at csie.org
 Summary            | MIME::encodeAddress() (implicitly) enforce RFC822 format checking before RFC2047 encoding
 Queue              | Horde Framework Packages
 State              | Bogus
 Priority           | 2. Medium
 Type               | Bug
 Owners             | Horde Developers, Michael Slusarz
-----------------------------------------------------------------------


rafan at csie.org (2005-04-04 08:02) wrote:

I agree with you. I found an example that should be work, but not.
Suppose I have a contact named ``foo <bar> <email>'' where bar is not
his/her
email, but part of the name. This fails in Mail_RFC822::parseAddressList()
because <bar> is parsed as email, where <email> is the real one.

I think it is not easy to fix all situations since email list can be from
hand typing
or selecting from contact. But letter case can be solved by store a real
name/email
in somewhere and display them (IIRC, there is some discussion in the
mailing).

At least, MIME::encodeAddress() SHOULD handle parsing error when calling
RFC822::parseAddressList() instead of do nothing. In this way, user will
assume
their mail sent out, but in fact not. IMP's compose.php should also handle
this.