RFC 2442 (rfc2442) - Page 1 of 9
The Batch SMTP Media Type
Alternative Format: Original Text Document
Network Working Group N. Freed
Request for Comments: 2442 D. Newman
Category: Informational Innosoft
J. Belissent
Sun Microsystems
M. Hoy
Mainbrace
November 1998
The
Batch SMTP
Media Type
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved.
Abstract
This document defines a MIME content type suitable for tunneling an
ESMTP [RFC-821, RFC-1869] transaction through any MIME-capable
transport. This type can be used for a variety of purposes,
including: Extending end-to-end MIME-based security services (e.g.,
[RFC-1847]) to cover message envelope information as well as message
content. Making it possible to use specific SMTP extensions such as
NOTARY [RFC-1891] over unextended SMTP transport infrastructure.
Enabling the transfer of multiple separate messages in a single
transactional unit.
Requirements Notation
This document occasionally uses terms that appear in capital letters.
When the terms "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY"
appear capitalized, they are being used to indicate particular
requirements of this specification. A discussion of the meanings of
the terms "MUST", "SHOULD", and "MAY" appears in [RFC-1123]; the
terms "MUST NOT" and "SHOULD NOT" are logical extensions of this
usage.
Freed, et. al. Informational