| Summary | Incorrect parsing of email address fields in compose |
| Queue | IMP |
| Queue Version | 3.2.6 |
| Type | Bug |
| State | Not A Bug |
| Priority | 3. High |
| Owners | Horde Developers (at) |
| Requester | postmaster (at) eng (dot) uts (dot) edu (dot) au |
| Created | 11/20/2004 (7612 days ago) |
| Due | |
| Updated | 12/08/2004 (7594 days ago) |
| Assigned | 11/25/2004 (7607 days ago) |
| Resolved | 12/08/2004 (7594 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
addresses.
The problem is that imp just excepts it, copies the message to the
Sent folder,
ie acts like the message has been sent, but in all reality none of the mail
rcpts get the message.
Like you said, because you can't guess what a user wanted it can't really be
fixed on the PEAR side, IMP needs to check that there is a matched
number of <>
bracekts, and if not report an error via java script, like is done when no
email addresses are supplied. Well, that is what I thought would be a
reasonable solution.
State ⇒ Not A Bug
Do a wild guess what he intended?
It's Mail_RFC822 from PEAR's Mail package that's causing this anyway,
so try to file a bug there if you still think that this not the
desired behaviour.
State ⇒ Assigned
State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Incorrect parsing of email address fields in compose
Queue ⇒ IMP
When email addresses with mismatched <> are passed to
MIME::encodeAddress an empty string is returned. When this mail is
sent it gets mailed to ""@localhost, which in my site makes it to
postmaster. We have added in some debuging code in compose which logs
the values of key varibles to findout the cause. An example of a
malformed address would be: joe.bloggs@eng.uts.edu.au> or
<joe.bloggs@eng.uts.edu.au