Mailing List Filters

Alexa Morris <amorris@amsl.com> Thu, 05 June 2008 15:03 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E40143A685B; Thu, 5 Jun 2008 08:03:18 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A6C7A3A6866; Thu, 5 Jun 2008 08:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.495
X-Spam-Level:
X-Spam-Status: No, score=-100.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMHkN4Smyg19; Thu, 5 Jun 2008 08:03:16 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:1112:1::14]) by core3.amsl.com (Postfix) with ESMTP id D1EE928C205; Thu, 5 Jun 2008 08:03:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by thunder2.amsl.com (Postfix) with ESMTP id A3B63480F2; Thu, 5 Jun 2008 08:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.amsl.com ([64.170.98.20]) by localhost (thunder2.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSl8gtZ95c3V; Thu, 5 Jun 2008 08:03:31 -0700 (PDT)
Received: from [192.168.1.102] (adsl-66-126-244-166.dsl.sntc01.pacbell.net [66.126.244.166]) by thunder2.amsl.com (Postfix) with ESMTP id 26A6B480C7; Thu, 5 Jun 2008 08:03:31 -0700 (PDT)
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 05 Jun 2008 08:03:13 -0700
Subject: Mailing List Filters
From: Alexa Morris <amorris@amsl.com>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
Message-ID: <C46D4E41.4F792%amorris@amsl.com>
Thread-Topic: Mailing List Filters
Thread-Index: AcjHHUZzhUvVyDMQEd2ZyAAUURi4Ig==
Mime-version: 1.0
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Several weeks ago, we removed some spam filtering rules from the IETF email
lists because there were concerns that, in a few very specific
circumstances, the rules were preventing legitimate mail from getting
through. Unfortunately, the removal of those spam rules has resulted in a
huge increase in spam sent to the lists, which has in turn greatly increased
the burden for all list moderators.

Because of this, we are planning to reinstitute two of those spam rules on
Monday of next week. For the vast majority of you, this will not even be
noticeable. However, if after Monday of next week you begin to experience
difficulty when you try to send mail to the IETF -- either to the
Secretariat or to a mailing list -- we have created a form that will enable
you to report your problem (the form bypasses the spam filters). Once we
know that you are experiencing difficulty, we can create an exception that
will enable you to send email again.

The form is accessible under the "IETF Secretariat" link from the home page,
at the bottom of the Secretariat contact page under "To Report Problems." A
direct link is here: http://www.ietf.org/contactform.html.

If you are curious to know what spam rules we are reinstating on Monday,
they are:

Rule A. This rule insists that, when a machine makes a HELO greeting, and
claims to be a certain machine, the name it claims exists in its appropriate
zone file, as either an "A" or an "MX" record.

Rule B. This rule does a reverse lookup on the client's IP address, and
makes sure that we can identify it as being IN-REV'ed by someone.

Please feel free to contact me if you have any questions or concerns.

Regards,
Alexa

-----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>




_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf