At 15:03 16-08-2011, Keith Moore wrote:
sorry, I misunderstood what was being suggested. if the server gets
DATA followed by a message (or a message fragment) followed by
CRLF.CRLF, it should accept the message (or fragment) and deliver it.
no matter what else follows, or doesn't follow, during the same SMTP
Yes. The SMTP server mentioned that it is accepting the message (up to
the end-of-data terminator. Rejecting the message is not an option once
the message has been accepted.
Hence the dilemma. It wasn't an valid RFC5322 message and the issue
is exasperated when it was DKIM signed and now recorded as a failure.
Never mind the fact QUIT (or a new transaction command) is an SMTP
requirement before the transaction is considered complete for
delivery. Its in the specs, but really, how much liberalism in
failure to comply to standards do we continue to tolerant?
If you want to change this, change the spec. I find it surreal that
people can have such a deep seeded passion for argument and fighting
for establishing standards and ideas to the point of delays in WG,
IETF, IESG reviews, etc, yet there this odd prevailing mindset among
the same people for tolerating failure. Honestly, whats the point in
throwing the RFC2919 book at people of its ok not follow any of this
and all these design implementation pressures to get things right is
all for nothing?
Crazy man. :)