News for hackers. Stuff that matters.

A comment on Firefox Monitor. Parent comment

Re:Firefox Monitor by StavrosK on Wednesday June 05, 2019 @03:44PM (#20108362)
Yes, it's in the SMTP RFC.
[ Parent | on HN ]
Re:Firefox Monitor by mjlee on Wednesday June 05, 2019 @05:54PM (#20109564)
To clarify the SMTP RFC (RFC 5321) says that a valid e-mail address is defined in RFC 5322 - Internet Message Format.

RFC 5322 does say that a `+` is a valid character in the local part of an e-mail address.

The `+` character being used for address aliasing is, as far as I can tell, not mentioned in RFC 5321 or RFC 5322

[ Parent | on HN ]
Re:Firefox Monitor by jcheng on Wednesday June 05, 2019 @08:03PM (#20110299)
It's apparently a thing now:

https://tools.ietf.org/html/rfc5233

[ Parent | on HN ]
Re:Firefox Monitor by megous on Wednesday June 05, 2019 @05:26PM (#20109351)
It's not.
[ Parent | on HN ]
Re:Firefox Monitor by StavrosK on Wednesday June 05, 2019 @06:54PM (#20109934)
See the sibling comment: https://news.ycombinator.com/item?id=20109564
[ Parent | on HN ]
Re:Firefox Monitor by megous on Thursday June 06, 2019 @06:39AM (#20113202)
RFCs don't define any meaning to '+' as described in this thread, except that local part of the address should be interpreted locally (usually by MDA), and preserved unmodified during message transfer.

There's no + aliasing in the specs. There's no interpretation defined for local part of email address.

[ Parent | on HN ]
Re:Firefox Monitor by StavrosK on Thursday June 06, 2019 @06:45AM (#20113234)
Oh, yes. I meant "+" is an acceptable character to use in the local part of an email address, as per the RFC. I see now where the misunderstanding lies.
[ Parent | on HN ]