I missed that, sorry, indeed, that's not valid. Norman Franke Answering Service for Directors, Inc. www.myasd.com
On May 18, 2012, at 2:52 PM, Ray Nicholus wrote: > Having a plus in the domain of your email address is effectively not valid > as this type of a domain is not allowed by DNS. Character with an accent > are also not allowed in email addresses. See RFC 5322 section 3.2.3 > (mirrored at http://tools.ietf.org/html/rfc5322#section-3.2.3). Quotes are > also not allowed in this case as this is not allowed by DNS (see the quote > after the domain). > > On Fri, May 18, 2012 at 10:01 AM, Norman Franke <nor...@myasd.com> wrote: > >> Having a + is valid. Some email systems allow users to filter based on >> stuff after the +, so joe+...@bar.com would still go to j...@bar.com, but >> he could then filter it into folders. I used to do this in college. >> >> See: http://en.wikipedia.org/wiki/Email_address >> >> The format of email addresses is local-part@domain where the local-part >> may be up to 64 characters long and the domain name may have a maximum of >> 253 characters - but the maximum 256 characters length of a forward or >> reverse path restricts the entire email address to be no more than 254 >> characters.[1] The formal definitions are in RFC 5322 (sections 3.2.3 and >> 3.4.1) and RFC 5321 - with a more readable form given in the informational >> RFC 3696[2] and the associated errata. >> [edit] >> Local part >> The local-part of the email address may use any of these ASCII characters >> RFC 5322 Section 3.2.3, RFC 6531 permits Unicode beyond the ASCII range: >> Uppercase and lowercase English letters (a–z, A–Z) (ASCII: 65-90, 97-122) >> Digits 0 to 9 (ASCII: 48-57) >> Characters !#$%&'*+-/=?^_`{|}~ (ASCII: 33, 35-39, 42, 43, 45, 47, 61, 63, >> 94-96, 123-126) >> Character . (dot, period, full stop) (ASCII: 46) provided that it is not >> the first or last character, and provided also that it does not appear two >> or more times consecutively (e.g. john.....@example.com is not allowed.). >> Special characters are allowed with restrictions. They are: >> Space and "(),:;<>@[\] (ASCII: 32, 34, 40, 41, 44, 58, 59, 60, 62, 64, >> 91-93) >> The restrictions for special characters are that they must only be used >> when contained between quotation marks, and that 3 of them (The space, >> backslash \ and quotation mark " (ASCII: 32, 92, 34)) must also be preceded >> by a backslash \ (e.g. "\ \\\""). >> Comments are allowed with parentheses, e.g. "john.smith(comment)@ >> example.com", "john(comment).sm...@example.com", and "joh(comment) >> n.sm...@example.com" are all equivalent to "john.sm...@example.com" >> International characters above U+007F are permitted by RFC 6531, though >> mail systems may restrict which characters to use when assigning local >> parts. >> >> Norman Franke >> Answering Service for Directors, Inc. >> www.myasd.com >> >> >> >> On May 18, 2012, at 10:40 AM, Ray Nicholus wrote: >> >>> Examples of currently allowed (and invalid) addresses: >>> >>> accent char - ép...@example.com >>> '+' in domain - test@foo+example.com >>> '/' in domain - test@example/com >>> wrapped in single quotes - 'f...@example.com' >>> wrapped in double quotes - "f...@example.com" >>> >>> Is there currently a case in JIRA to address this? >> >>
