FYI 35, RFC 2635 on DON'T SPEW
RFC Editor <rfc-ed@ISI.EDU> Thu, 01 July 1999 23:51 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25557; Thu, 1 Jul 1999 19:51:28 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA03969 for ietf-123-outbound.10@ietf.org; Thu, 1 Jul 1999 19:45:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA03947 for <all-ietf@loki.ietf.org>; Thu, 1 Jul 1999 19:41:49 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25086 for <all-ietf@ietf.org>; Thu, 1 Jul 1999 19:37:42 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id QAA27538; Thu, 1 Jul 1999 16:37:43 -0700 (PDT)
Message-Id: <199907012337.QAA27538@boreas.isi.edu>
To: IETF-Announce:;
Subject: FYI 35, RFC 2635 on DON'T SPEW
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 01 Jul 1999 16:37:43 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. FYI 35: RFC 2635: Title: DON'T SPEW A Set of Guidelines for Mass Unsolicited Mailings and Postings (spam*) Author(s): S. Hambridge, A. Lunde Status: Informational Date: June 1999 Mailbox: sallyh@ludwig.sc.intel.com, Albert-Lunde@nwu.edu Pages: 18 Characters: 44669 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-run-spew-08.txt URL: ftp://ftp.isi.edu/in-notes/rfc2635.txt This document explains why mass unsolicited electronic mail messages are harmful in the Internetworking community. It gives a set of guidelines for dealing with unsolicited mail for users, for system administrators, news administrators, and mailing list managers. It also makes suggestions Internet Service Providers might follow. This document is a product of the Responsible Use of the Network Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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.
- FYI 35, RFC 2635 on DON'T SPEW RFC Editor