BCP 30, RFC 2505 on Anti-Spam Recommendations

RFC Editor <rfc-ed@ISI.EDU> Tue, 09 February 1999 22:15 UTC

Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id RAA00102 for ietf-123-outbound.10@ietf.org; Tue, 9 Feb 1999 17:15:01 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA00074 for <all-ietf@ietf.org>; Tue, 9 Feb 1999 17:12:49 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id OAA00684; Tue, 9 Feb 1999 14:12:49 -0800 (PST)
Message-Id: <199902092212.OAA00684@boreas.isi.edu>
To: IETF-Announce:;
Subject: BCP 30, RFC 2505 on Anti-Spam Recommendations
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 09 Feb 1999 14:12:49 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        BCP 30:
	RFC 2505: 

        Title:	    Anti-Spam Recommendations for SMTP MTAs
	Author(s):  G. Lindberg
	Status:     Best Current Practice
	Date:       February 1999
        Mailbox:    lindberg@cdg.chalmers.se
	Pages:      24
        Characters: 53597
        Updates/Obsoletes/See Also: None  
        I-D Tag:    draft-lindberg-anti-spam-mta-08.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2505.txt


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.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc2505.txt"><ftp://ftp.isi.edu/in-notes/rfc2505.txt>