Summary: the member tools domain mail forwarding form blocks emails with plus signs, cites obsolete RFC 822
The domain email forwarding form on sonic.net incorrectly blocks emails with plus signs (eg email@example.com) in the "points-to" field and pops up an error citing the obsolete RFC 822.
Depending on how you look at this, it's a bug report - don't implement an obsolete RFC and throw an error citing it - or a feature request - please update the logic in https://members.sonic.net/email/domalias/index.php to comply with RFC 2822 which supersedes 822 and allows plus signs (nb: sonic's mail server already supports plus signs, this is an issue with the form logic in https://members.sonic.net/email/domalias/index.php)
To reproduce this bug:
Go to the member tools domain alias section:
Select a domain you own that is hosted at sonic.net.
Get redirected to
Add New Domain Email Alias with a left hand value of * (asterisk, a catch-all redirect) and a right hand email address with a valid sonic mailbox plus a plus sign and text (eg firstname.lastname@example.org)
Result: a popup error warning: "the rule violates RFC 822"
Expected outcome: forwarding mail to a plus sign address per RFC 2822, which supersedes 822.
RFC 822 does not allow plus signs in emails, however RFC 2822 explicitly makes 822 obsolete and does allow plus signs.
See RFC 2822 Sec 3.4 which defines "address" and refers to 3.2.4 for the valid characters (atoms).
The spec for 3.2.4 allows plus signs as valid characters.