Skeeve,
GMX is still wrong. RFC2822 (
http://www.faqs.org/rfcs/rfc2822.html) defines an atext as:
- Code: Select all
atext = ALPHA / DIGIT / ; Any character except controls,
"!" / "#" / ; SP, and specials.
"$" / "%" / ; Used for atoms
"&" / "'" /
"*" / "+" /
"-" / "/" /
"=" / "?" /
"^" / "_" /
"`" / "{" /
"|" / "}" /
"~"
Note the presence of the + and # among the chars. So sg uses a set of atext chars (and only atext chars) in its addresses. Now, let's continue. The same RFC says:
- Code: Select all
mailbox = name-addr / addr-spec
name-addr = [display-name] angle-addr
angle-addr = [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr
addr-spec = local-part "@" domain
local-part = dot-atom / quoted-string / obs-local-part
Ah, it says the part of an address before the "@" can be a quoted string, eh? So does that mean "whatever"@spamgourmet.com should be unquoted by sg and treated the same as
whatever@spamgourmet.com?
Nope. Au contraire. Let's see part 3.4.1 of RFC2822:
An addr-spec is a specific Internet identifier that contains a
locally interpreted string followed by the at-sign character ("@",
ASCII value 64) followed by an Internet domain. The locally
interpreted string is either a quoted-string or a dot-atom. If the
string can be represented as a dot-atom (that is, it contains no
characters other than atext characters or "." surrounded by atext
characters), then the dot-atom form SHOULD be used and the
quoted-string form SHOULD NOT be used.
The last sentence is quite clear: if you don't absolutely need the quotes, you should not use them.
Since we can legally write our addresses with atext chars, we don't need the quotes, and we do not (and should not) use them. By requiring them, GMX breaks the RFC.
Please feel free to send this email to them.