|
|
|||
|
|
||||
|
List Email Headers I send out an ezine (newsletter) called Snippets . And I manage that newsletter on my own computer using Gammadyne Mailer. Because I have substantial control over the processing of Snippets subscriptions and mailings, I wanted to understand the standards for email headers. I wanted the headers for my ezine to be correct. As I looked for standards, I not only found the standards for headers, I found other list "Best Practices" which I assembled here. But this page describes just the issues of email headers for lists. I use these list email headers for all the lists I manage using Gammadyne Mailer. To see a full set of email headers for my Snippets ezine, click here.
RFC Specified Headers Within the Internet community, Requests for Comments (RFCs) are a critical source of "standards". The RFCs are organized as a series of notes, sequentially number. They began in 1969 when the Internet was ARPANET. These notes include literally tons of information. They discuss, not only the various technical aspects of the Internet (e.g., networking protocols, procedures, programs, and concepts), but they also include meeting notes, opinion, and even humor Note that all RFCs are not Internet standards documents. RFCs can have Informational or Experimental status. Such RFCs do not represent any kind of standard. Instead, they contain information that may be useful or important to retain in this archival document series. Two examples include an RFC on the RFC history called "30 Years of RFCs" and this tribute to Jon Postel entitled "I Remember IANA". (Note that the second RFC has number 2468. This is not an accident.) Two of the RFCs, RFC 2919 and RFC 2369, directly apply to email headers for lists.
RFC 2919 RFC 2919 specifies that emails from ezines and other email lists should include the standard header field List-Id. This header field clearly identifies that the email is from a "list" and also uniquely identifies the list being used. I implement this in my email headers. To see a full set of email headers for my Snippets ezine, click here. List-ID List-ID designates a unique identifier for the mailing list. The identifier is built using the domain name, plus a string to uniquely identify that list within that domain name space. The field may also contain a plain text "name" of the list. For example, for my Snippets ezine, I use:
Here is the field from my Snippets ezine:
RFC 2369 RFC 2369 specifies that emails from ezines and other email lists should include six (6) standard header fields. These are:
I implement each of these in my email headers. To see a full set of email headers for my Snippets ezine, click here. List-Help List-Help specifies an email URL and/or web URL to obtain help for a list. It may also include "comments". The RFC notes:
Here is the field from my Snippets ezine:
List-Subscribe List-Subscribe specifies an email URL and/or web URL to directly subscribe the user (to request addition to the list). It may also include "comments". Here is the field from my Snippets ezine:
List-Unsubscribe List-Unsubscribe specifies an email URL and/or web URL to directly unsubscribe the user (to request removal from the list). It may also include "comments". Here is the field from my Snippets ezine:
List-Post List-Post specifies an email URL and/or web URL to post to the list. Frequently the "address" of the list, this could also be a moderator or a web URL for submission. It may also include "comments". The RFC notes:
Here is the field from my Snippets ezine:
List-Owner List-Owner specifies an email URL and/or web URL to contact a human administrator for the list. It may also include "comments". The RFC notes:
Here is the field from my Snippets ezine:
List-Archive List-Archive specifies an email URL and/or web URL to access archives for the list. It may also include "comments". Here is the field from my Snippets ezine:
RFC Specified Email Addresses In addition to the list headers specified by RFCs, there are standard email addresses specified by RFCs. One RFC, RFC 2142, directly applies to email addresses. The implementation of these standard email addresses is the subject of some debate because of the spam problem. However, I have implemented all of these email addresses within my system.
RFC 2142 RFC 2142 specifies a variety of standard email addresses which should be implemented. These are:
The first two of these specifically relate to ezines and lists. I have implemented all of these for my site. list-request@ RFC 2142 specifies that an address of "list-request@" should be implemented for the ezine, where "list" is the name of the ezine. For example, for Snippets, my first ezine, the address is Snippets-Request@JamesSHuggins.com. Email to this address should, at a minimum, return information on how to administer subscriptions. abuse@ RFC 2142 specifies that an address of "abuse@" should be implemented so that individuals can easily send abuse information to a domain holder. Ezine subscribers may wish to use this address to complain about spam. Additional User Defined Headers In addition to the RFC specified headers, I include a variety of "user defined" headers in my ezine list emails. RFC 822 provided for "user defined fields" in email headers. The RFC said:
Note that "X-" is a reserved string to enable people to create their own user defined fields, without worrying that these fields would conflict with any standard fields. These are sometimes called X-Headers or X-Fields. RFC 822 has been obsoleted by RFC 2822. And, unfortunately, RFC 2822 did not include the specification of X-Headers. This "flaw" in RFC 2822 has been commented on in several places on the net. Nevertheless, the use of X-Fields or X-Headers remains common and I have implemented them for my ezines. In making such implementations I have looked at other ezines to see what X-Headers they have used. I have adopted some, adapted others and invented my own. These are my current X-Fields:
To see a full set of email headers for my Snippets ezine, click here. X-Ezine-Title X-Ezine-Title specifies the name of the list. Here is the field from my Snippets ezine:
X-Ezine-Description X-Ezine-Description specifies a longer text string which provides more description of the list. Here is the field from my Snippets ezine:
X-Author X-Author specifies the formal, legal author of the ezine. Here is the field from my Snippets ezine:
X-Copyright X-Copyright specifies the copyright statement for the list. Here is the field from my Snippets ezine:
X-Mailer X-Mailer specifies the software used to email to the list. Here is the field from my Snippets ezine:
X-Recipient X-Recipient specifies the addressee of the ezine. This is important because individuals may maintain multiple addresses, including forwarding addresses. Having the addressee specified separately in an X-Field helps to ensure that subscription issues can be quickly resolved. Here is the field from my Snippets ezine:
X-Subscriber X-Subscriber is a duplicate of the X-Recipient field. I include both because my research revealed that both X-Fields were common. Here is the field from my Snippets ezine:
X-Subscribe-Email X-Subscribe-Email provides the email address to be used to subscribe to the list. This information duplicates the information contained in the standard field List-Subscribe, but isolates the email address. Here is the field from my Snippets ezine:
X-Subscribe-Web X-Subscribe-Web provides the web address to be used to subscribe to the list. This information duplicates the information contained in the standard field List-Subscribe, but isolates the web address. Here is the field from my Snippets ezine:
X-Unsubscribe-Email X-Unsubscribe-Email provides the email address to be used to unsubscribe from the list. This information duplicates the information contained in the standard field List-Unsbscribe, but isolates the email address. Here is the field from my Snippets ezine:
X-Unsubscribe-Web X-Unsubscribe-Web provides the web address to be used to unsubscribe from the list. This information duplicates the information contained in the standard field List-Unsubscribe, but isolates the web address. Here is the field from my Snippets ezine:
X-Information X-Information provides the web address for more information about the list. Here is the field from my Snippets ezine:
X-Archives X-Archives provides the web address for archived issues of the list. Here is the field from my Snippets ezine:
X-Privacy X-Privacy provides the web address for the privacy statement for the list. Here is the field from my Snippets ezine:
X-List-Best-Practices X-List-Best-Practices provides the web address for a statement of the Best Practices followed by the list. Here is the field from my Snippets ezine:
X-Licensing X-Licensing provides the web address for licensing information for list content. Here is the field from my Snippets ezine:
X-CAN-SPAM-1, X-CAN-SPAM-1, X-CAN-SPAM-2, X-CAN-SPAM-3 and X-CAN-SPAM-4 provide statements required or recommended for compliance with the US CAN-SPAM act. Here are the fields from my Snippets ezine:
List Management Information
External Sources
My Ezine/Newsletter
I Use Gammadyne Mailer I began using the Gammadyne Mailer in late 2002. It is possible to use it very simply, almost out of the box. But it also features a very complete internal programming language to let you do just about anything you want. And, it keeps all the information on my PC in an Access database, where I know the information is secure and under my control. It is screaming software. I strongly recommend Gammadyne Mailer.
Disclosure: I participate in the Gammadyne affiliate program. Click here to link without crediting my referral account. |
Best Practices of Email, Ezine and List Management
RFC 2142
|
This page created: Sun, 19.Oct.2003
Last updated: |
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|