I should have mentioned that the addresses in the input are the sort you'd find in the 821 envelope on a RCPT TO, not the full generality of what 822 allows. -- bc
On Tue, Jun 7, 2016 at 12:50 PM, Paul Gilmartin <paulgboul...@aim.com> wrote: > On 2016-06-07, at 10:27, Bob Cronin wrote: > > > > I've got an input stream containing a comma-delimited list of all the > email > > addresses for a given person (in Internet-standard form, i.e. > > localpart@domain). However, the process that collects these addresses > > doesn't have very effective data validation and all sorts of input issues > > creep through (e.g. addresses with no at-sign, addresses with embedded > > blanks, addresses with characters outside the allowable set for > dot-atoms, > > etc.). The first address in the comma-delimited list is supposed to be > the > > person's preferred address, but if it is invalid, I'd like to choose the > > first address in the list that is not invalid. > > > And RFC 822 allows practically any ASCII (UTF-8?) character in the > local-part > if it appears between quotation marks. And recently domain names are > allowed > to contain non-ASCII characters. > > And the informal name may appear as a comment in the address. It's a > courtesy to retain that. (See the From: line in your own message.) > > > -- gil >
