| Summary | email address validation |
| Queue | IMP |
| Queue Version | 3.2.3 |
| Type | Enhancement |
| State | Resolved |
| Priority | 2. Medium |
| Owners | |
| Requester | trent.hornibrook (at) gmail (dot) com |
| Created | 09/14/2004 (7680 days ago) |
| Due | |
| Updated | 09/20/2004 (7674 days ago) |
| Assigned | |
| Resolved | 09/15/2004 (7679 days ago) |
| Milestone | |
| Patch | No |
usually cover a few pages of code.
IMP *does* check for the return status or the mailer. If you don't get
an error message, it's rather a fault of PEAR's Mail class not
returning an error.
isnt informed if the status of pears mail returns false (rejected by server).
In Turba, there isnt any validation on the email field to ensure that
the pattern matches
a+(.a+)*@a+.a+(.a+)*
which i believe would be useful
Trent
State ⇒ Resolved
might be invalid for your system might syntactically still be a valid
address.
It's the MTA's job anyway to bounce messages with wrong recipient addresses.
State ⇒ New
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Summary ⇒ email address validation
Queue ⇒ IMP
the nicest)
to the compose page as well as turba's address book.
Currently, we are able to save an invalid email address and *send a
mail to it* - the end user isnt aware that the address is invalid and
hence is not aware that the smtp server rejected it.