CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 23:44:52 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=.pC48fQRLJPCfU.dc3g85Wa5GeMlHyy0L11BL3dXDXk-1760139892-1.0.1.1-YKPwEdFYFBZ0OsHm7qQShgjKjBet2fNbKUArfqJa9qhod0jCSNWeHGeOzhp2BXMgQ490VrNhIVaGJ2aBEQKQXf9QOakZY3ogqc6a5EzWvVY; path=/; expires=Sat, 11-Oct-25 00:14:52 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c9fcf228e3c181-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2442 » RFC Editor
Search RFCs
RFC 2442
The Batch SMTP Media Type, November 1998
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2442
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2442
Abstract
This document defines a MIME content type suitable for tunneling an ESMTP transaction through any MIME-capable transport. This memo provides information for the Internet community
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us