Tickets :: [#6899] broken address validation

6.0.0-beta1

7/4/25

Summary	broken address validation
Queue	IMP
Queue Version	HEAD
Type	Enhancement
State	Resolved
Priority	2. Medium
Owners	slusarz (at) horde (dot) org
Requester	adrieder (at) sbox (dot) tugraz (dot) at
Created	06/11/2008 (6232 days ago)
Due	06/11/2008 (6232 days ago)
Updated	06/16/2008 (6227 days ago)
Assigned	06/15/2008 (6228 days ago)
Resolved	06/16/2008 (6227 days ago)
Milestone
Patch	No

06/16/2008 02:36:22 PM	Chuck Hagenbuch	Comment #12	Reply to this comment
Right, and it is good to know that you are one of the authors of that package ;-) Still no reason not to use the correct bug tracker. Which this turned out to be in this case, but the point remains.

06/16/2008 07:51:46 AM	adrieder (at) sbox (dot) tugraz (dot) at	Comment #11	Reply to this comment
Fixed. We weren't quoting the display portion of the address string correctly if it contains a period (this wasn't required to be quoted by RFC 822, but is required under RFC 2822), so Mail_RFC822 was correctly reporting that the address was invalid. Thanks, it works now!

06/16/2008 07:23:11 AM	Michael Slusarz	Comment #10 Assigned to Michael Slusarz State ⇒ Resolved Priority ⇒ 2. Medium	Reply to this comment
Fixed. We weren't quoting the display portion of the address string correctly if it contains a period (this wasn't required to be quoted by RFC 822, but is required under RFC 2822), so Mail_RFC822 was correctly reporting that the address was invalid.

06/16/2008 07:21:04 AM	CVS Commit	Comment #9	Reply to this comment
Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/MIME/MIME.php?r1=1.139.4.35&r2=1.139.4.36&ty=u

06/16/2008 06:46:35 AM	CVS Commit	Comment #8	Reply to this comment
Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/MIME/MIME.php?r1=1.192&r2=1.193&ty=u

06/16/2008 06:20:59 AM	adrieder (at) sbox (dot) tugraz (dot) at	Comment #7	Reply to this comment
But the error is still coming from the PEAR package, not from Horde. Right, and it is good to know that you are one of the authors of that package ;-)

06/15/2008 05:04:46 PM	Chuck Hagenbuch	Comment #6 State ⇒ Feedback	Reply to this comment
But the error is still coming from the PEAR package, not from Horde.

06/15/2008 02:30:39 PM	Jan Schneider	Comment #5 State ⇒ Assigned	Reply to this comment
Same here, that patch didn't fix it.

06/15/2008 01:51:21 PM	adrieder (at) sbox (dot) tugraz (dot) at	Comment #4	Reply to this comment
This is a bug in PEAR::Mail, not in Horde or IMP. FWIW, I don't see this with PEAR::Mail from CVS (1.2.0a2+). This might have fixed things: http://pear.php.net/bugs/bug.php?id=9137 Strange, it doesn't work here. "a.a" nospam@tugraz.at -> works "a.a" <nospam@tugraz.at> -> fails

06/13/2008 06:06:08 AM	Michael Slusarz	Comment #3	Reply to this comment
This is a bug in PEAR::Mail, not in Horde or IMP. FWIW, I don't see this with PEAR::Mail from CVS (1.2.0a2+). This might have fixed things: http://pear.php.net/bugs/bug.php?id=9137

06/11/2008 08:24:09 PM	Chuck Hagenbuch	Comment #2 State ⇒ Rejected	Reply to this comment
This is a bug in PEAR::Mail, not in Horde or IMP.

06/11/2008 12:51:21 PM	adrieder (at) sbox (dot) tugraz (dot) at	Comment #1 Patch ⇒ No State ⇒ New Milestone ⇒ Queue ⇒ IMP Due ⇒ 06/11/2008 Summary ⇒ broken address validation Type ⇒ Enhancement Priority ⇒ 3. High	Reply to this comment
When trying to send a message to an address that has a dot in the name part which is not followed by a blank I get a address validation error: e.g. "a.a.a" <nospam@tugraz.at> There was an error sending your message: Validation failed for: a.a.a <nospam@tugraz.at> This should not happen, there is nothing wrong with the address. "a.a.a d" <nospam@tugraz.at> -> works "a.a.a d.d" <nospam@tugraz.at> -> works "a. a." <nospam@tugraz.at> -> works