About  |   Legal  |   Contact  |   Resources  |   Home  |                     mainsleazespam.com

Best Practices for Bulk Email Management

Standards and Advice for Proper Implementation and Use of Email and Mass Email Lists

The Spamhaus Project     Solicited Bulk Email is an important mechanism for keeping consenting customers informed of products or service news. When Bulk Email is Solicited it is valuable to the recipient and therefore also to the sender. When it's Unsolicited it's purely Spam, an unwanted nuisance to the recipient, and, because it forces the recipient to assume the cost of receiving, storing and dealing with the unwanted advert it is also a theft of the unwilling recipient's time and resources.     The difference between senders of legitimate bulk email and spammers couldn't be clearer, the legitimate bulk email sender has verifiable permission from the recipients before sending, the spammer does not.          Mailing Lists -vs- Spam Lists          Definition of Spam

ISIPP     The Institute for Spam and Internet Public Policy is dedicated to providing analysis, information, and consulting on industry issues relating to public policies and processes regarding spam, email, and the Internet. ISIPP also organizes and sponsors industry forums such as the Email Management Roundtable, and the Email Deliverability Summit.          The Institute for Spam and Internet Public Policy ("ISIPP")          ISIPP Site Overview of Standards and Best Practices     [Ed. Note: ISIPP is headed by Anne Mitchell, Esq., President and CEO, a well known and by many anti-spammers respected lawyer familiar to and for years with a presence in the anti-spam communities online.]

MAPS. Mail Abuse Prevention System LLC.     Mailing lists have a long and venerable history on the Internet. Mailing lists are an excellent vehicle for distributing focused, targeted information to an interested, receptive audience. Consequently, mailing lists have been used successfully as a highly effective direct marketing tool. Unfortunately, mailing lists are also vulnerable to misuse through a variety of means. An all-too-common example is where an individual is forge subscribed to a high number of mailing lists and must take extraordinary measures to be removed. Also, some marketers misuse mailing lists, often through a lack of knowledge about longstanding Internet customs and rules, or because they attempt to apply direct paper mail methodology to the electronic realm.          Basic Mailing List Management Guidelines for Preventing Abuse

SpamCon Foundation.     Draft Principles.          SpamCon Foundation: To Reduce Spam (Junk Email)

Network Working Group. Request For Comments: 1855     This document provides a minimum set of guidelines for Network Etiquette (Netiquette) which organizations may take and adapt for their own use. As such, it is deliberately written in a bulleted format to make adaptation easier and to make any particular item easy (or easier) to find. It also functions as a minimum set of guidelines for individuals, both users and administrators. This memo is the product of the Responsible Use of the Network (RUN) Working Group of the IETF.          Netiquette Guidelines

Network Working Group Request for Comments: 3098      This memo offers useful suggestions for responsible advertising techniques that can be used via the internet in an environment where the advertiser, recipients, and the Internet Community can coexist in a productive and mutually respectful fashion. Some measure of clarity will also be added to the definitions, dangers, and details inherent to Internet Marketing.          How to Advertise Responsibly Using E-Mail and Newsgroups              or - how NOT to $$$$$ MAKE ENEMIES FAST! $$$$$

Network Working Group Request for Comments: 2505.     This memo gives a number of implementation recommendations for SMTP, ... MTAs (Mail Transfer Agents, e.g. sendmail...) to make them more capable of reducing the impact of spam(*).          Anti-Spam Recommendations for SMTP MTAs (rfc2505.txt)          Anti-Spam Recommendations for SMTP MTAs (bcp30.txt)

Network Working Group. Request for Comments: 2821.     This document is a self-contained specification of the basic protocol for the Internet electronic mail transport. It consolidates, updates and clarifies, but doesn't add new or change existing functionality of the following: - the original SMTP (Simple Mail Transfer Protocol) specification of RFC 821 [30], - domain name system requirements and implications for mail transport from RFC 1035 [22] and RFC 974 [27], - the clarifications and applicability statements in RFC 1123 [2], and - material drawn from the SMTP Extension mechanisms [19].          Request for Comments: 2821. Simple Mail Transfer Protocol.

Network Working Group. Request for Comments: 2822     This standard specifies a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. This standard supersedes the one specified in Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages", updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs.          Request for Comments: 2822. Internet Message Format

Network Working Group. Request for Comments: 2554     This document defines an SMTP service extension [ESMTP] whereby an SMTP client may indicate an authentication mechanism to the server, perform an authentication protocol exchange, and optionally negotiate a security layer for subsequent protocol interactions. This extension is a profile of the Simple Authentication and Security Layer [SASL]          Request for Comments: 2554. SMTP Service Extension for Authentication

Network Working Group. Request for Comments: 2487     This document describes an extension to the SMTP service that allows an SMTP server and client to use transport-layer security to provide private, authenticated communication over the Internet. This gives SMTP agents the ability to protect some or all of their communications from eavesdroppers and attackers.          Request for Comments: 2487. SMTP Service Extension for Secure SMTP over TLS

LINX Unsolicited Bulk Messaging Subcommittee     The primary audience of this document is those who operate mailing lists. It will also be of significant interest to the writers of mailing list software and to ISPs, and their abuse teams, who wish to discuss community standards with their customers. It is also intended to demonstrate to the public, to the media, to regulators and to other authorities that the industry is acting responsibly in this area.          LINX Best Current Practice Operating Mailing Lists

rhyolite.com.     Even the most curmudgeonly of anti-spammers is capable of humor. This link proves that assertion.          You Might Be An Anti-Spam Kook If...