Re: [perpass] Fwd: here's my message to perpass from yesterday, see any problems with it?

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 16 December 2013 15:53 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9619F1AE357 for <perpass@ietfa.amsl.com>; Mon, 16 Dec 2013 07:53:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level:
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wj3e99_a2X0I for <perpass@ietfa.amsl.com>; Mon, 16 Dec 2013 07:53:35 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id CD3C21AE34D for <perpass@ietf.org>; Mon, 16 Dec 2013 07:53:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E2C55BE6E for <perpass@ietf.org>; Mon, 16 Dec 2013 15:53:33 +0000 (GMT)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LXaVP8gow6rt for <perpass@ietf.org>; Mon, 16 Dec 2013 15:53:33 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C5EC0BE63 for <perpass@ietf.org>; Mon, 16 Dec 2013 15:53:33 +0000 (GMT)
Message-ID: <52AF21FD.8060305@cs.tcd.ie>
Date: Mon, 16 Dec 2013 15:53:33 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: perpass <perpass@ietf.org>
References: <52AA44A4.9060608@bbn.com> <D6019517-65AA-4695-B81D-CA5AB600AAF3@ieca.com> <52AF0BD8.2060503@cs.tcd.ie>
In-Reply-To: <52AF0BD8.2060503@cs.tcd.ie>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [perpass] Fwd: here's my message to perpass from yesterday, see any problems with it?
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Dec 2013 15:53:36 -0000

On 12/16/2013 02:19 PM, Stephen Farrell wrote:
> Ta. That did make it to the ietf list over the weekend
> and I replied, but whatever's gumming up the system
> for Steve also hit my reply;-)
> 
> The IETF list is the right place for the discussion
> though rather than this list I think so if folks can
> wait a while until we unstick whatever's gummed up
> that'd be good. I'll send mail when I think that's
> done. (I figure there's some spam filter somewhere
> that's messing up or something, based on the ticket
> I saw generated.)

The explanation arrived. My response to Steve's mail
contained the string "route" at the end of a sentence,
so then a full stop "." and was followed by a sentence
that started with "In" but with no spaces between those.
That was interpreted as a URI for somewhere naughty
enough to apparently get the message a spam score
sufficiently high that the message is just dropped.

I just fixed that in my response and my mail is on
the IETF discuss list [1] so follow up there if
commenting further please.

If you're also replying to Steve, [2] or to my
reply, please watch out for rewrapping the text if
you don't see your mail hit the list.

What a world;-)

S.

[1] http://www.ietf.org/mail-archive/web/ietf/current/msg84998.html
[2] http://www.ietf.org/mail-archive/web/ietf/current/msg84975.html