RE: Can someone test AOL's mx servers for me...
Please. Please. Everyone. Thank you. But you can all go home now! I think I've received about 50 messages now about the RFC compliant '<>' usage and have got the message. So now I know ... it's right up there with not using CNAMEs for MX records ... they use to work once upon a time in a more forgiving internet (whenever that was) or at least a less RFC compliant internet. But I can take a hint (all 50!). And I have since figured out what the flippin' other problem with the mail was. Thank you all. Karyn -----Original Message----- From: Mark Brown To: Karyn Ulriksen Sent: 8/11/00 3:47 AM Subject: Re: Can someone test AOL's mx servers for me... On Thu, Aug 10, 2000 at 06:04:56PM -0700, Karyn Ulriksen wrote:
I'm seeing some wierd errors when emailing AOL. The response for the "MAIL FROM: user@domain.com" is a '501 syntax error'.
Is that exactly what you are typing? In that case AOL is being perfectly reasonable - the correct syntax is "FROM:<user@domain.com>" (without quotes) and similarly for RCPT TO. The <> are mandatory. -- Mark Brown mailto:broonie@tardis.ed.ac.uk (Trying to avoid grumpiness) http://www.tardis.ed.ac.uk/~broonie/ EUFS http://www.eusa.ed.ac.uk/societies/filmsoc/
On Fri, Aug 11, 2000 at 04:04:26AM -0700, Karyn Ulriksen wrote:
Please. Please. Everyone. Thank you. But you can all go home now! I think I've received about 50 messages now about the RFC compliant '<>' usage and have got the message. So now I know ... it's right up there with not using CNAMEs for MX records ... they use to work once upon a time in a more forgiving internet (whenever that was) or at least a less RFC compliant internet. But I can take a hint (all 50!).
Although those people are correct that RFC821 specifies that you should be sending angle brackets, they are conveniently forgetting the author's own rule of implementing protocols, from RFC791: "In general, an implementation must be conservative in its sending behavior, and liberal in its receiving behavior. That is, it must be careful to send well-formed datagrams, but must accept any datagram that it can interpret (e.g., not object to technical errors where the meaning is still clear)." Note the "must". So, they may be correct in telling you that you're not RFC821 compliant, but they are not RFC791 compliant for rejecting it. I will not buy any objection that "FROM: joe@foo.bar" is unclear but "FROM: <joe@foo.bar>" isn't. Or, in summary: You're being sloppy, but they're being assholes.
participants (2)
-
Karyn Ulriksen
-
Shawn McMahon