SMTP Service Extension for Checkpoint/Restart

Metadata

Publisher: IETF
Doc Type: Experimental
Pages: 7
Abstract: This memo defines an extension to the SMTP service whereby an interrupted SMTP transaction can be restarted at a later time without having to repeat all of the commands and message content sent prior to the interruption.
Publication Date: 1995-09-01
Status Note: Experimental
DOI: 10.17487/RFC1845
Link: https://doi.org/10.17487/RFC1845
Author(s): Dave Crocker
Ned Freed
A. Cargille
Keyword(s): SMTP, Transaction

Latest version of IETF RFC 1845

Document Versions — IETF RFC 1845

▶ IETF RFC 1845 (1995-09-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

IETF RFC 821 [Superseded*]
IETF RFC 822 [Superseded*]
IETF RFC 974 [Superseded*]
IETF RFC 1123 [Active*]
IETF RFC 1521 [Superseded*]
IETF RFC 1651 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC1845.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 1845, SMTP Service Extension for Checkpoint/Restart. Available at https://doi.org/10.17487/RFC1845

Snippet:

IETF RFC 1845, SMTP Service Extension for Checkpoint/Restart. Available at https://doi.org/10.17487/RFC1845

HTML (ISO 690 compliant)

Preview:

IETF RFC 1845, SMTP Service Extension for Checkpoint/Restart. Available at https://doi.org/10.17487/RFC1845

Snippet:

<span class="citation"><cite>IETF RFC 1845</cite>, SMTP Service Extension for Checkpoint/Restart. Available at <a href="https://doi.org/10.17487/RFC1845" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1845</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 1845, SMTP Service Extension for Checkpoint/Restart
doi: 10.17487/RFC1845
url: https://doi.org/10.17487/RFC1845

Snippet:

<li>
<cite id="bib-rfc1845">IETF RFC 1845</cite>, SMTP Service Extension for Checkpoint/Restart
<span class="doi">10.17487/RFC1845</span>
</li>

Referenced By

IETF RFC 2476 [Superseded*]
IETF RFC 4409 [Superseded*]
IETF RFC 6409 [Active*]