David Lee wrote:
If, conversely, it is not in breach, then SA has a problem: it shouldn't
be marking it "INVALID_DATE". Incidentally, it is this aspect (rather
than any other) of the date that is triggering this SA rule, isn't it?
I guess we could fix it by renaming the rule "STUPIDLY_FORMATTED_DATE".
Anyone writing their own mail application, such as this mobile
providers, should really stick to formatting as seen in well established
MTAs.
This seems to me to be a clear breach of RFC2822. Mmail's defence is that
section 4.3 ends:
> Other multi-character (usually between 3 and 5) alphabetic time zones
> have been used in Internet messages. Any such time zone whose
> meaning is not known SHOULD be considered equivalent to "-0000"
> unless there is out-of-band information confirming their meaning.
and that the "usually 3 or 5 alphabetic" could (they argue) include the
17-character "GMT Standard Time".
"usually 3 or 5 alphabetic" refers to the reality that there have been,
and still are, both 3 and 5 character timezone codes in use.
Besides it has really been Coordinated Universal Time (UTC) since
January 1, 1972. I doubt that their clock set to GMT is really
purposely off by up to 0.9 seconds to the rest of us. :)
Daryl
