MAAWG Published Documents
These best practices and white papers represent the cooperative efforts of MAAWG members to provide the industry with recommendations and background information to improve messaging security and protect users. MAAWG best practices are updated as needed and new documents are added as they become available.
 |
Demystifies the messaging reputation technology now used by most large service providers to identify abusive and errant emails as junk mail
|
|
An overview of authentication technology focusing on the standardized mechanisms in general use today, Sender Policy Framework (SPF), Sender IDentification Framework (SenderID), and DomainKeys Identified Mail (DKIM)
|
|
Recommendations for both forwarders and ISPs to help distinguish legitimate consumers using a forwarding service from spammers
|
|
June 01, 2008
MAAWG Recommendation: Methods for Sharing Dynamic IP Address Space Information with Others Describes four approaches to make dynamic IP addresses more easily obtainable by mailbox providers with a discussion of the advantages and disadvantages of each
|
|
Defines how volume email senders can improve the deliverability of legitimate e-newsletters and permission-based e-marketing
|
|
A summary of the most effective abuse desk best practices from MAAWG service providers
|
|
The first best practices developed cooperatively by ISPs and email service providers outlining criteria for entering and exiting closed safe environments, recommendations for convenient end-user self-remediation, and practices to make end-user education a primary focus
|
|
Augments the best practices jointly authored by MAAWG and the OECD Business and Industry Advisory Committee (BIAC) for the OECD Anti-Spam Toolkit, Annex II
|
|
Jointly developed between the Anti-Phishing Working Group and MAAWG, this paper provides technical and business practices to help ISPs and mailbox providers thwart phishing attacks and other malevolent network abuses and also includes practices to respond constructively when these attacks occur
|
|
Recommendations include blocking unauthorized access to and from port 25, requiring authentication, and aggregating email traffic through a SMTP server that is controlled by the service provider
|
