BestPrac.Org

Stop Spam : Best Practice in Email
Spam Prevention and Eradication


Principles of Best Practice -
Email Server Software Developers:

Summary

Email servers usually occur at least twice between the sender and the intended recipient of emails - including spam emails. This creates at least two opportunities for spam to be stopped dead in its tracks, and save bandwidth resources and costs in the process.

Firstly, the email server accessed by the sender should capable of recognising OUTGOING spam, and stop it at source. Outbound filters and rate limiters are an important, though currently under-utilised part of that process.

Secondly, the email server from which an end-user receives his/her email should also be fully featured, to filter out spam and other security risks before they reach the recipient.

Ref # Principle or Proposed Principle
ESS001  Email Server Software should seek to maximise the information contained within email headers, by ensuring that all header information received is forwarded (unless antispam or other security filters return or destroy the email), and by adding all possible additional information into the headers. No header information should ever be "stripped".
ESS002  Email Server Software Developers should build in every conceivable option for maximum versatility, in the most user-friendly manner possible, for the postmaster to be able to configure filters and response options for both incoming and outgoing emails, including allowing third-party anti spam and other security solutions to be implemented.
ESS003  Email Server Software Developers should build into their product readily configurable 'rate limiters', flexible enough to ensure that ISPs, Hosting Services and other users can configure different rate limits for different clients.
ESS004 
ESS005 
ESS006 
ESS007 
ESS008 
ESS009 
ESS010 
ESS011 
ESS012