| Summary | MIME::bareAddress Issue |
| Queue | Horde Base |
| Queue Version | 3.1 |
| Type | Bug |
| State | Resolved |
| Priority | 3. High |
| Owners | |
| Requester | skennedy (at) vcn (dot) com |
| Created | 03/22/2006 (7107 days ago) |
| Due | |
| Updated | 03/24/2006 (7105 days ago) |
| Assigned | |
| Resolved | 03/24/2006 (7105 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ MIME::bareAddress Issue
Queue ⇒ Horde Base
lib/Horde/MIME.php not checking the result of
$parser->parseAddressList() (line 655) to make sure it's not a PEAR
error object.
I've been able to get the RFC822::parseAddressList() function to
return a PEAR object when feeeding it a recipient like this:
"Some Name" <Some Name <some@email.com>>
This is a problem because if a recipient string like the above is
typed into the "To:" field of an email in IMP, IMP will accept it and
it ends up delivering the message with a blank To: header.