From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: Membership disabled due to excessive bounces Date: Sun, 11 Nov 2018 17:51:15 -0500 Message-ID: <87tvknxm69.fsf@netris.org> References: <8736s7nao4.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44922) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gLyah-0003KJ-3y for guix-devel@gnu.org; Sun, 11 Nov 2018 17:52:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gLyab-0004Cg-Oe for guix-devel@gnu.org; Sun, 11 Nov 2018 17:52:26 -0500 Received: from world.peace.net ([64.112.178.59]:47556) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gLyaa-00046g-Ru for guix-devel@gnu.org; Sun, 11 Nov 2018 17:52:21 -0500 In-Reply-To: <8736s7nao4.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Sun, 11 Nov 2018 11:58:03 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Pierre Neidhardt Cc: guix-devel Pierre Neidhardt writes: > Today is the second time I receive a membership deletion email from the > mailing list (first one was on the 31st of October). > > It starts with: > >> Your membership in the mailing list Guix-devel has been disabled due >> to excessive bounces The last bounce received from you was dated >> 11-Nov-2018. You will not get any more messages from this list until >> you re-enable your membership. You will receive 3 more reminders like >> this before your membership in the list is deleted. > > I've re-enabled my membership both times. > > My email is hosted by https://gandi.net (I use their email hosting > service). I send emails with Emacs' mu4e if that matters. > > Does anyone know why this happens? I've never had this issue before > with any other mailing list (most of them also hosted by Mailman). It's happening because there's a Guix developer, who will remain unnamed, who has configured a very strict DMARC policy for their email domain, and the GNU infrastructure is not currently able to cope well with this. There are at least two unresolved issues: (1) When Guix developers push commits to our git repository, Savannah sends a notification email on their behalf, with the developer's email address in the "From:" header. (2) GNU Mailman apparently breaks the DKIM signatures on replies in some cases, due to its processing of the mail and its modification of certain mail headers. In both cases, the end result is that messages sent on this developer's behalf by Savannah or GNU Mailman are rejected by email providers that honor this developer's strict DMARC policy. Solutions exist for both of these problems. The latest version of GNU Mailman apparently avoids breaking DKIM signatures, and the git notification commit could be changed to use a different email address in the "From:" header. However, it will take some time for the GNU sysadmins to upgrade Mailman. In the meantime, unless the Guix developer will agree to change their DMARC policy (which they seem very reluctant to do), I'm sorry to report that we will have to live with this issue for a while longer. Mark