<?xml version='1.0'?>

<reference anchor='RFC2369'>

<front>
<title abbrev='URLs as Meta-Syntax'>The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields</title>
<author initials='G.' surname='Neufeld' fullname='Grant Neufeld'>
<organization>Calgary, Alberta</organization>
<address>
<email>grant@acm.org</email>
<uri>http://www.nisto.com/</uri></address></author>
<author initials='J.D.' surname='Baer' fullname='Joshua D. Baer'>
<organization>Box 273</organization>
<address>
<postal>
<street>4902 Forbes Avenue</street>
<street>Pittsburgh</street>
<street>PA 15213-3799</street>
<country>USA</country></postal>
<email>josh@skyweyr.com</email></address></author>
<date month='July' year='1998' />
<area>Applications</area>
<keyword>mail</keyword>
<keyword>uniform resource locator</keyword>
<keyword>URL</keyword>
<abstract>
<t>
   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 ) 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.
</t>
<t>
   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.
</t>
<t>
   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.
</t>
<t>
   The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,
   &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;,  &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this
   document are to be interpreted as described in RFC 2119.
</t></abstract></front>

<seriesInfo name='RFC' value='2369' />
<format type='HTML' octets='45836' target='http://xml.resource.org/public/rfc/html/rfc2369.html' />
<format type='XML' octets='31893' target='http://xml.resource.org/public/rfc/xml/rfc2369.xml' />
</reference>
