ESMTP and LMTP Transmission Types Registration
draft-newman-esmtpsa-01

[Ballot discuss]
The Last Call says:

  Implementation Report can be accessed at
  http://www.ietf.org/iesg/implementation.html

  Yet, the Secretariat was not asked to post the Implementation Report
  until the Last Call was finished.  I think we need to rereun the Last
  Call with the information available to the community.

[Note]: 'This document has no shepherd. Please see the email message I''ve sent to IESG for additional information (and a pointer to implementation report).' added by Alexey Melnikov

[Note]: 'This document has no shepherd.<br><br>Please see the email message I''ve sent to IESG for additional information (and a pointer to implementation report).' added by Alexey Melnikov

This list is not complete.

The following software generates WITH parameters specified in RFC 3848:

1) Postfix MTA since 2007-07-20 (ESMTP*)
2) Exim, since version 4.42 (ESTMP*)
3) Cyrus IMAP (LMTP*)
4) Sun Java System Messaging Server 7 Update 3 (all)
5) Isode M-Switch (ESTMP*) and Isode M-Box (LMTP)

The following software parses/interprets WITH parameters specified in RFC 3848:

1) SpamAssassin since 3.0.3 (detects message submission hops)
2) Msglint <http://tools.ietf.org/tools/msglint/> (verifies values)
3) Various Sieve (RFC 5228) scripts that can check Received headers

[Ballot comment]
I'd say that these acronyms need to be expanded


Title: ESMTP and LMTP Transmission Types Registration


Abstract

  This registers seven new mail transmission types (ESMTPA, ESMTPS,
  ESMTPSA, LMTP, LMTPA, LMTPS, LMTPSA) for use in the "with" clause of
  a Received header in an Internet message.

[Ballot comment]
It might be wise to add to the security considerations some note to the effect that this information is not trustable, and SHOULD NOT be used for mail filtering or relaying decisions except in very controlled environments.