Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields (RFC2369)

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

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Neufeld: AUTHOR [+2]

Abstract

The mailing list command specification header fields are a set of structured fields to be added to email messages sent by email distribution lists. Each field typically contains a URL (usually mailto [RFC2368]) locating the relevant information or performing the command directly. The three core header fields described in this document are List-Help, List-Subscribe, and List-Unsubscribe.

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

Network Working Group G. Neufeld

Request for Comments: 2369 Nisto

Category: Standards Track J. Baer

SkyWeyr Technologies

July 1998

The Use of URLs as Meta-Syntax for Core Mail List Commands

and their Transport through Message Header Fields

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.

Abstract

The mailing list command specification header fields are a set of

structured fields to be added to email messages sent by email

distribution lists. Each field typically contains a URL (usually

mailto [RFC2368]) locating the relevant information or performing the

command directly. The three core header fields described in this

document are List-Help, List-Subscribe, and List-Unsubscribe.

There are three other header fields described here which, although

not as widely applicable, will have utility for a sufficient number

of mailing lists to justify their formalization here. These are

List-Post, List-Owner and List-Archive.

By including these header fields, list servers can make it possible

for mail clients to provide automated tools for users to perform list

functions. This could take the form of a menu item, push button, or

other user interface element. The intent is to simplify the user

experience, providing a common interface to the often cryptic and

varied mailing list manager commands.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

document are to be interpreted as described in RFC 2119.

1. Introduction

This is a proposal for additional header fields to be added to email

messages sent by email distribution lists. The content of each new

field is typically a URL - usually mailto [RFC2368] - which locates

the relevant information or performs the command directly. MTAs

generating the header fields SHOULD usually include a mailto based

command, in addition to any other protocols used, in order to support

users who do not have access to non-mail-based protocols.

...