RFC 3249: Implementers Guide for Facsimile Using Internet Mail
In plain English — editorial summary, not part of the RFC
This document is intended for the implementers of software that use email to send to facsimiles using RFC 2305 and 2532. This is an informational document and its guidelines do not supersede the referenced documents. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3249
- Published
- September 2002
- Authors
- V. Cancio; M. Moldovan; H. Tamura; D. Wing
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 2007
- RFC 5598Internet Mail ArchitectureCurrent
July 2009
- RFC 3886An Extensible Message Format for Message Tracking ResponsesCurrent
September 2004
- RFC 2530Indicating Supported Media Features Using Extensions to DSN and MDNCurrent
March 1999
- RFC 5322Internet Message FormatUpdated
October 2008
- RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated
August 2009
- RFC 9007Handling Message Disposition Notification with the JSON Meta Application Protocol (JMAP)Current
March 2021
- RFC 3250Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type RegistrationObsoleted
September 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?