IETF Logo Mail Archive

Re: [apps-discuss] Comments on Malformed Message BCP draft

Jaap Akkerhuis <jaap@NLnetLabs.nl> Sat, 16 April 2011 08:39 UTC

Return-Path: <jaap@bartok.nlnetlabs.nl>
X-Original-To: apps-discuss@ietfc.amsl.com
Delivered-To: apps-discuss@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 5F5FBE06AB for <apps-discuss@ietfc.amsl.com>; Sat, 16 Apr 2011 01:39:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SRKW9+M6fYYm for <apps-discuss@ietfc.amsl.com>; Sat, 16 Apr 2011 01:39:19 -0700 (PDT)
Received: from bartok.nlnetlabs.nl (bartok.nlnetlabs.nl [IPv6:2001:7b8:206:1:216:76ff:feb8:3c02]) by ietfc.amsl.com (Postfix) with ESMTP id B7026E0675 for <apps-discuss@ietf.org>; Sat, 16 Apr 2011 01:39:19 -0700 (PDT)
Received: from bartok.nlnetlabs.nl (localhost [127.0.0.1]) by bartok.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p3G8dD5X087566; Sat, 16 Apr 2011 10:39:13 +0200 (CEST) (envelope-from jaap@bartok.nlnetlabs.nl)
Message-Id: <201104160839.p3G8dD5X087566@bartok.nlnetlabs.nl>
To: Nathaniel Borenstein <nsb@guppylake.com>
In-reply-to: <62554BEB-8154-48D7-BEAF-40217AEEDB61@guppylake.com>
References: <F5833273385BB34F99288B3648C4F06F1343319E22@EXCH-C2.corp.cloudmark.com> <CEDB17EC-80CE-49B5-91C1-FBCB0449BBA5@network-heretics.com> <62554BEB-8154-48D7-BEAF-40217AEEDB61@guppylake.com>
Comments: In-reply-to Nathaniel Borenstein <nsb@guppylake.com> message dated "Sat, 16 Apr 2011 09:27:35 +0100."
Date: Sat, 16 Apr 2011 10:39:13 +0200
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (bartok.nlnetlabs.nl [127.0.0.1]); Sat, 16 Apr 2011 10:39:14 +0200 (CEST)
Cc: ietf-822@imc.org, Keith Moore <moore@network-heretics.com>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] Comments on Malformed Message BCP draft
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Apr 2011 08:39:20 -0000

    And the senders of misformatted messages might eventually fix
    their code, if only to shut up the annoying warning messages.

And the easiest way to do that is declare these as spam, so nothing will
be fixed in the end.

	jaap

v2.23.0 | Report a Bug | By Email