Yes, good point - I'd noticed that that situation is currently broken
(file a bug if you want), and I was thinking about rewriting the parser
to deal with it (pulling off "tokens" instead of splitting on ',' first)
- I don't know that I need to do that for the current crop of tasks, but
might anyway.
...Bryan
Reid Ellis wrote:
On Jan 31, 2007, at 21:55, Bryan Stearns wrote:
Brian Kirsch wrote [comments on my decoupling proposal] (thanks!):
However, you are correct that the only time a email address really
needs to be valid is the moment before a send. We could refactor so
that right before
calling the mail service to send the item the detail view checks
validity via the EmailAddress.isValidEmailAddress on each string
token in the 'to' field (cc? bcc?).
I don't think the detail view can know: your SMTP server might accept
"bkirsch" by itself; all the detail view could really do is check for
gross structural errors (odd numbers of doublequotes, etc.), and
since the SMTP server's gonna do that anyway, why bother?
One reason to bother about basic parsing (like quotes) is that we need
to know where one email address ends, and another begins. e.g. "Edward
Affluent, the Third" <[EMAIL PROTECTED]> is an email address, not two email
addresses. This is used in the "+N" code to show the number of
non-displayed addresses.
Reid
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
