Re: What I've been wondering about the DMARC problem

Sabahattin Gucukoglu <listsebby@me.com> Wed, 16 April 2014 06:58 UTC

Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A94371A006B for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 23:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_DBL_REDIR=0.001] 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 Lu11xtuRJ3jx for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 23:58:56 -0700 (PDT)
Received: from st11p02mm-asmtp001.mac.com (st11p02mm-asmtpout001.mac.com [17.172.220.236]) by ietfa.amsl.com (Postfix) with ESMTP id 581B61A0064 for <ietf@ietf.org>; Tue, 15 Apr 2014 23:58:55 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from [192.168.1.6] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by st11p02mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N4400JPE3DXCL60@st11p02mm-asmtp001.mac.com> for ietf@ietf.org; Wed, 16 Apr 2014 06:58:47 +0000 (GMT)
Subject: Re: What I've been wondering about the DMARC problem
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <534D98CC.9080400@gmail.com>
Date: Wed, 16 Apr 2014 07:58:44 +0100
Content-transfer-encoding: quoted-printable
Message-id: <2478F2D1-2E08-45D7-86A2-36443959E272@me.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-MANTSH: 1TEIXWV4bG1oaGkdHB0lGUkdDRl5PWBoaGxEKTEMXGx0EGx0YBBIZBBsdEBseGh8 aEQpYTRdLEQptfhcaEQpMWRcbGhsbEQpZSRcRClleF2hjeREKQ04XSxsYGmJCH2lpHx9JGXhzB xltGhwfEkYZEQpYXBcZBBoEHQdNSx0SSEkcTAUbHQQbHRgEEhkEGx0QGx4aHxsRCl5ZF2FNEh1 pEQpMRhdia2sRCkNaFxgbGQQbGBkEGxMYBBkaEQpEWBcZEQpESRcYEQpCRRdmUH1dH21kGgVIY xEKQk4XbHBgeUAdYlJpGmIRCkJMF2dJH215aRh+ckJNEQpCbBdlaGUYbU0cGENGThEKQkAXZxx nXkJkY1Ibc2QRCnBoF2EacnpnbnJaTlpSEQpwaBdteGhLTH5TR194BREKcGgXZUtQa2BmeEdJX U4RCnBoF24SQWhvfVMTbnltEQpwaBdpfWEBHxJncgUdchEKcH8XelNve2JleFNpfmIRCnBfF2Q fY1hMf21CG10eEQpwbBdrZk5rQWVfZlNnAREKcEwXZxpTbEBrQG0fQ1oR
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96, 1.0.14, 0.0.0000 definitions=2014-04-15_04:2014-04-15, 2014-04-15, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404160063
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OoIJk9OPnJeK4Lz0I7KBkxtFg60
Cc: dcrocker@bbiw.net, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 06:58:59 -0000

On 15 Apr 2014, at 21:38, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> The mailman fix is worse than the disease. I think the .INVALID fix is
> much better, because Reply-all will still work.

Reply-all should still work with the Mailman fix; reply-to contains member (or member and list, for the reply-to-list case) and To/CC are included by MUA as usual.  It's "Reply" that's broken, and in the reply-to-list case: if the sender's address is discarded then the recipient can't use it, and if it's included then the sender has to manually manipulate the recipients in the composer window just to reply to the sender only after hitting Reply.

I really have little issue with the Mailman fix as it currently stands.  It's borked, but it works.  My lists are mostly of the chatty reply-to-list variety anyway.  The display name isn't touched; lots of users won't even notice …

Apparently Mailman 3 will do this properly, implementing support for DMARC by rejection and not tampering. http://j.mp/1m6N5Jt
Perhaps someone should point them to this discussion, or advise on the rewrite-to-invalid hack (which BTW has shortcomings of its own, especially for users of touchscreen devices …).

Cheers,
Sabahattin