Browse Prior Art Database

Message Submission (RFC2476)

IP.com Disclosure Number: IPCOM000003056D
Original Publication Date: 1998-Dec-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 12 page(s) / 28K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Gellens: AUTHOR [+2]

Abstract

SMTP was defined as a message *transfer* protocol, that is, a means to route (if needed) and deliver finished (complete) messages. Message Transfer Agents (MTAs) are not supposed to alter the message text, except to add 'Received', 'Return-Path', and other header fields as required by [SMTP-MTA].

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 10% of the total text.

Network Working Group R. Gellens

Request for Comments: 2476 QUALCOMM

Category: Standards Track J. Klensin

MCI

December 1998

Message Submission

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Table of Contents

1. Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2. Document Information . . . . . . . . . . . . . . . . . . . 3

2.1. Definitions of Terms Used in this Memo . . . . . . . . . 3

2.2. Conventions Used in this Document . . . . . . . . . . . 4

3. Message Submission . . . . . . . . . . . . . . . . . . . . . 4

3.1. Submission Identification . . . . . . . . . . . . . . . 4

3.2. Message Rejection and Bouncing . . . . . . . . . . . . . 4

3.3. Authorized Submission . . . . . . . . . . . . . . . . . 5

3.4. Enhanced Status Codes . . . . . . . . . . . . . . . . . 6

4. Mandatory Actions . . . . . . . . . . . . . . . . . . . . . 6

4.1. General Submission Rejection Code . . . . . . . . . . . 6

4.2. Ensure All Domains are Fully-Qualified . . . . . . . . 6

5. Recommended Actions . . . . . . . . . . . . . . . . . . . . 7

5.1. Enforce Address Syntax . . . . . . . . . . . . . . . . 7

5.2. Log Errors . . . . . . . . . . . . . . . . . . . . . . . 7

6. Optional Actions . . . . . . . . . . . . . . . . . . . . . 7

6.1. Enforce Submission Rights . . . . . . . . . . . . . . . 7

6.2. Require Authentication . . . . . . . . . . . . . . . . 8

6.3. Enforce Permissions . . . . . . . . . . . . . . . . . . 8

6.4. Check Message Data . . . . . . . . . . . . . . . . . . 8

7. Interaction with SMTP Extensions . . . . . . . . . . . . . . 8

8. Message Modifications . . . . . . . . . . . . . . . . . . . 9

8.1. Add 'Sender' . . . . . . . . . . . . . . . . . . . . . . 9

8.2. Add 'Date' . . . . . . . . . . . . . . . . . . . . . . 10

8.3. Add 'Message-ID' . . . . . . . . . . . . . . . . . . . . 10

8.4. Transfer Encode . . . . . ...