dear sourceforge: when you go poop, do you need a crowbar to pry your ass open?

[rone]

<dkim-milter-discuss@lists.sourceforge.net>: host mail.sourceforge.net[66.35.250.206] said:
  550-Postmaster verification failed while checking <rone@eforceglobal.com>
  550-Called:   209.177.149.166
  550-Sent:     RCPT TO:<postmaster@eforceglobal.com>
  550-Response: 550 <postmaster@eforceglobal.com>: Recipient address rejected: eforceglobal.com
  550-Several RFCs state that you are required to have a postmaster
  550-mailbox for each mail domain. This host does not accept mail
  550-from domains whose servers reject the postmaster address.
  550 Sender verify failed (in reply to RCPT TO command)

Yeah, yeah, it would be nice if eFORCE's mail server were RFC-compliant, but at the same time, i'd love to print out section 2.10 of RFC 793, roll it up, and smack SourceForge's nose with it.

Comments

[dawn-guy.livejournal.com]

I think Postel said it better (for this situation) in RFC 760 section 3.2:

The implementation of a protocol must be robust. Each implementation must expect to interoperate with others created by different individuals. While the goal of this specification is to be explicit about the protocol there is the possibility of differing interpretations. In general, an implementation should be conservative in its sending behavior, and liberal in its receiving behavior. That is, it should be careful to send well-formed datagrams, but should accept any datagram that it can interpret (e.g., not object to technical errors where the meaning is still clear).

Whether you care to point out Eric Allman's strong support of extending Postel's philosophy to mail transfer is up to you.