Re: DMARC methods in mailman --- [LEDE-DEV] DMARC related mass bounces / disabled subscriptions (fwd) Jo-Philipp Wich: [LEDE-DEV] DMARC related mass bounces / disabled subscriptions

Brian E Carpenter <> Mon, 19 December 2016 02:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2B70812945B for <>; Sun, 18 Dec 2016 18:52:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EpA7kt9Ezir4 for <>; Sun, 18 Dec 2016 18:52:39 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400e:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E3C33127071 for <>; Sun, 18 Dec 2016 18:52:39 -0800 (PST)
Received: by with SMTP id y62so3009380pgy.1 for <>; Sun, 18 Dec 2016 18:52:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=kKBqJw7LiN6M4+WOj47loGFn2B9Y8MmReDPDB8PnHdM=; b=NibSTkSD/NhdJvWFF0JcbVRwtIHNDYw3Bd3yrUQzCGLxXn5ikMRLgpQP3FXWSoTDTH EDfbz1oKBA20F0T9/O7Q9SgJG6vojBeyc2JrFZls+09wJelTz61BjPOxxncwzVuhMjhG bbmxdEFEN3wsZ+RiTQTpPRDS5lMwd6QGepCMrkqfA8QITVNNCU7gR30tqKAJ8sj6/4k9 VIATkJWzt9SFLWVx/bEhVjPoSjfej/hiOG7uc60nZuEfa3y1aqS84ol5TBWojknz+hhr KVPsqHmAJJLr2jtDV54JMoD+Ga0RDawJejyUQHdjUmzKSkZa0+LxDGZrPT9cWra3vKM5 qBRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=kKBqJw7LiN6M4+WOj47loGFn2B9Y8MmReDPDB8PnHdM=; b=gWXjLgo41czHCmT84xTj5tbIcA+Z8AclHSSjHoi7sOG8BQe2JDwJCmL1+HU2dp+2k4 nPbgwJ/p92uRV6b54cP9rqCcuDADKqnBs8qlcP6l+3zgTthuxigJzpLOoVZSgm8WuHjZ RmkSQViJDxAxn6bOXE1o80KFhifU00KjoRSdhJyO7GI75VjbU30UjjeUmKBUKoL4IUGs 8fFfVATj/73k5tBQfu/vFSR8TJ2iMDYrlsvVBrebmZjsUPye6alhJpxGBaeZB67rLiVZ d1tEFlBxpbbcNvvd877XdjIpQwM3c24jGBs4ggKgq6gOuOg8jP1XF9ncdPCsmQIRfUg5 A/WQ==
X-Gm-Message-State: AKaTC02ubEXb9JEzkp3wwv1n9MLF5mO1LCoSS9/uxULNYDRYhlWt17Ng6lZD2GqWSoAezQ==
X-Received: by with SMTP id a2mr30788260pli.106.1482115959025; Sun, 18 Dec 2016 18:52:39 -0800 (PST)
Received: from ?IPv6:2406:e007:7145:1:28cc:dc4c:9703:6781? ([2406:e007:7145:1:28cc:dc4c:9703:6781]) by with ESMTPSA id r2sm26719362pfi.67.2016. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Dec 2016 18:52:38 -0800 (PST)
Subject: Re: DMARC methods in mailman --- [LEDE-DEV] DMARC related mass bounces / disabled subscriptions (fwd) Jo-Philipp Wich: [LEDE-DEV] DMARC related mass bounces / disabled subscriptions
To: John R Levine <>
References: <20161218220828.14035.qmail@ary.lan> <> <alpine.OSX.2.11.1612182027050.19818@ary.qy>
From: Brian E Carpenter <>
Organization: University of Auckland
Message-ID: <>
Date: Mon, 19 Dec 2016 15:52:35 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.11.1612182027050.19818@ary.qy>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <>
Cc: IETF general list <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 19 Dec 2016 02:52:41 -0000

On 19/12/2016 14:29, John R Levine wrote:
>> The question was what can a mailman list admin do. I don't see another answer,
> I wrote a shim that goes between Sympa (like Mailman only French) and the 
> MTA in an afternoon that does per-user From: line rewriting.  I wrote some 
> stuff to do message wrapping in another afternoon.
> I don't think I'm a particularly brilliant programmer, and I have no doubt 
> that if the IETF found a technical approach we prefer, we could easily 
> implement it.

Yes, but *today* as an IETF list admin I don't have that choice. Objectively
I have exactly two choices: advise the user to change email provider, or rewrite
the From for every single subscriber. I'm not happy with that choice, but unless
somebody in the IETF's IT support does something, that is the choice I have.