Re: [Tools-discuss] SPF rejection of mail to chairs

Robert Sparks <rjsparks@nostrum.com> Thu, 27 February 2020 19:44 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5BBE3A0A4F for <tools-discuss@ietfa.amsl.com>; Thu, 27 Feb 2020 11:44:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level:
X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 IByOA6Ig8fQr for <tools-discuss@ietfa.amsl.com>; Thu, 27 Feb 2020 11:44:41 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 021183A0A4E for <tools-discuss@ietf.org>; Thu, 27 Feb 2020 11:44:40 -0800 (PST)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01RJiccp085393 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 27 Feb 2020 13:44:40 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1582832680; bh=z0l4VIHfQ3nkuq6MUp4DhfFjNH3q1R9BMcurfMt6io0=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=e2BH5fcj4b9J/wYOxfaO+fsWS1TY7b8Pns+GmZy5Od6W3aQGksKCqK+k7GGw9Dqtp FLI2F7K9UB0Lwoah889QamrQDy1i05IfqPRkWh3Zy5V6pYEicFSGvgR9sPAu0v2s/z x9SLkm0NoR530xMwbZXCuRfKGBjvj/ZKO3PUiWwk=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: Carsten Bormann <cabo@tzi.org>, tools-discuss@ietf.org
Cc: Michael Richardson <mcr+ietf@sandelman.ca>
References: <RT-Ticket-282330@www.ietf.org/rt> <20191121040335.A47AD120944@ietfa.amsl.com> <253406B7-7911-4971-9ED5-D836606D3B6A@tzi.org> <rt-4.4.2-17081-1574310971-201.282330-4-0@www.ietf.org/rt> <CABL0ig51Bfs5w94vnZnTBQaQ+mC5+Vjett61Cs1d0sc_DpFsXA@mail.gmail.com> <9898.1574329972@dooku.sandelman.ca> <A7C5D382-FDE4-4EB7-9463-FB2E0884920C@tzi.org> <96dbab15-2b11-4114-8ad0-690047430d68@nostrum.com> <DB2BE9AA-1018-44B0-B926-AF27427B4577@tzi.org> <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <7f34680e-4fe8-cf17-a0e9-d3696d509a6f@nostrum.com>
Date: Thu, 27 Feb 2020 13:44:38 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <0C8935E8-7693-4FAE-85DF-33408D297F15@tzi.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/eVzx2YVlVrwS2cI3WlVWa-YBGTE>
Subject: Re: [Tools-discuss] SPF rejection of mail to chairs
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2020 19:44:45 -0000

Hi Carsten -

The situation hasn't changed so far. Our efforts the last few weeks have 
been focused on the server replacement and finalizing the python2/3 
transitions. I expect we will get to spend some time talking about 
changing the behavior of the draft and chair aliases while we're in 
Vancouver.

I understand your point about not having a place to go to follow the 
status things like this, and am looking for ways to better provide that.

RjS

On 2/26/20 11:18 AM, Carsten Bormann wrote:
> Generic, undirected PING…
>
> Grüße, Carsten
>
>
>> On 2019-12-20, at 18:33, Carsten Bormann <cabo@tzi.org> wrote:
>>
>> Hi Robert,
>>
>>> On Dec 20, 2019, at 17:16, Robert Sparks <rjsparks@nostrum.com> wrote:
>>>
>>> Hi Carsten -
>>>
>>> We're aware of this problem. Unfortunately there is not any quick fix for it.
>>>
>>> The path through the mail processing chain for the aliases is very different than the path for the mailing lists, and the way we are applying the current workaround isn't applicable there.
>> I suspected so.
>>
>> A lot of our processes are set up to make use of the aliases, so in the end this creates  (hidden-terminal like) problems for these as well.
>>
>> I’m not sure the majority of mail servers are set up to report SPF failures as delivery status, so I’m not even sure I know the extent of this problem.  (So far, I have often resorted to the explanation that some people are too lazy to read my mail, but maybe SPF vs. forwarding is the real problem.)
>>
>>> We are discussing what we can do instead.
>> I wonder if there is a way to stay informed about the progress of issues like this (that are not naturally rooted in the issue tracker of some piece of software).  I mostly brought this up again on the list because I have no visibility.
>>
>> (I also need a better workaround.  I wonder if I need to move to sending IETF mail from a mail account with a ~all SPF setting, like it’s 2014 again…  Maybe I can just manually set my From address to cabo=40tzi.org@dmarc.ietf.org?)
>>
>> Grüße, Carsten
>>
>> [1]: https://en.wikipedia.org/wiki/Hidden_node_problem
>>
>>> RjS
>>>
>>> On 12/20/19 1:14 AM, Carsten Bormann wrote:
>>>> On Nov 21, 2019, at 10:52, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
>>>>>> Is there a need for the DMARC hack for the chair aliases, too?
>>>>> Oh crap, yes we do.
>>>>> and on all of the Internet-draft author lists.
>>>> Just fell into the trap again (on a draft…@ietf.org alias).
>>>>
>>>> Where do I need to report this bug to so it gets addressed?
>>>>
>>>> Grüße, Carsten
>>>>
>>>> ___________________________________________________________
>>>> Tools-discuss mailing list
>>>> Tools-discuss@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/tools-discuss
>>>>
>>>> Please report datatracker.ietf.org and mailarchive.ietf.org
>>>> bugs at http://tools.ietf.org/tools/ietfdb
>>>> or send email to datatracker-project@ietf.org
>>>>
>>>> Please report tools.ietf.org bugs at
>>>> http://tools.ietf.org/tools/issues
>>>> or send email to webmaster@tools.ietf.org
>>> ___________________________________________________________
>>> Tools-discuss mailing list
>>> Tools-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tools-discuss
>>>
>>> Please report datatracker.ietf.org and mailarchive.ietf.org
>>> bugs at http://tools.ietf.org/tools/ietfdb
>>> or send email to datatracker-project@ietf.org
>>>
>>> Please report tools.ietf.org bugs at
>>> http://tools.ietf.org/tools/issues
>>> or send email to webmaster@tools.ietf.org
>> ___________________________________________________________
>> Tools-discuss mailing list
>> Tools-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-discuss
>>
>> Please report datatracker.ietf.org and mailarchive.ietf.org
>> bugs at http://tools.ietf.org/tools/ietfdb
>> or send email to datatracker-project@ietf.org
>>
>> Please report tools.ietf.org bugs at
>> http://tools.ietf.org/tools/issues
>> or send email to webmaster@tools.ietf.org