RE: [dmarc-ietf] IETF Mailing Lists and DMARC

"Christian Huitema" <huitema@huitema.net> Sat, 05 November 2016 17:21 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56C161296C7 for <ietf@ietfa.amsl.com>; Sat, 5 Nov 2016 10:21:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 K9RVc-NhS55o for <ietf@ietfa.amsl.com>; Sat, 5 Nov 2016 10:21:26 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C4861295C8 for <ietf@ietf.org>; Sat, 5 Nov 2016 10:21:26 -0700 (PDT)
Received: from xsmtp01.mail2web.com ([168.144.250.230]) by mx43.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.86) (envelope-from <huitema@huitema.net>) id 1c34eh-000581-1z for ietf@ietf.org; Sat, 05 Nov 2016 18:21:24 +0100
Received: from [10.5.2.35] (helo=xmail10.myhosting.com) by xsmtp01.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1c34eb-0006Qf-9m for ietf@ietf.org; Sat, 05 Nov 2016 13:21:21 -0400
Received: (qmail 29503 invoked from network); 5 Nov 2016 17:21:15 -0000
Received: from unknown (HELO icebox) (Authenticated-user:_huitema@huitema.net@[172.56.39.170]) (envelope-sender <huitema@huitema.net>) by xmail10.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 5 Nov 2016 17:21:15 -0000
From: Christian Huitema <huitema@huitema.net>
To: 'Michael Richardson' <mcr+ietf@sandelman.ca>, 'IETF' <ietf@ietf.org>
References: <678C2FBA-A661-4556-A300-5C08562B5F8A@iii.ca> <29429.1478113235@obiwan.sandelman.ca> <CABa8R6vHdt75NFKW3s6xOzLcq=jmVAHDPX0tjLRdGpYSTP2cYA@mail.gmail.com> <7301.1478274182@obiwan.sandelman.ca>
In-Reply-To: <7301.1478274182@obiwan.sandelman.ca>
Date: Sat, 05 Nov 2016 10:21:13 -0700
Message-ID: <022001d23789$03154ae0$093fe0a0$@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGsYqBOEXVnO6RqnKr79Diprp8JVQHc0oqBAuJjLDMBiUaeJ6DkBmeQ
Content-Language: en-us
Subject: RE: [dmarc-ietf] IETF Mailing Lists and DMARC
X-Filter-ID: s0sct1PQhAABKnZB5plbIVbU93hg6Kq00BjAzYBqWlUcW8ntawmIBRrYFzUH2lbvx1wTMkEUUoeb KIhkyzl2dGR9IQQoYtpHB3NwY5Xj87w0HbLcIXRK+rCYHS2Pxr4sUvWQm1ERVuodk8O3ETzMDyZo 1Q5xNRLUrf3HwkCAmqEul44BSYeg2GDudv13TBandcmtTcWSOKD5RASVzg27isfnUU8Aq9Xij6e6 U5pAs/95kYwBFjHSX1ySASMY7Q8kVWau65pVsnZkx/s3iU5HXZFVgpT1b21uZVckGp0ccOY/32e+ 5fVqy4sN42wuoCbd0npwMH44Pt2njKMwCMVe5fi885J4uw2WezmviQauN2SLBDMrD7q/cJogwbqz suokuKS3SvBae3MYJkcyURBnFAZIe8Pggnek1xH/TgvWD0MaKXvNWrRcSD72jROfhu6vZJ0Q4x+0 GOxZvoENDONKwZkjGlUCvU6ZAmJB8zrNH9DxX8G2bApANEDRnSX/sJx0Uf5/xO8dap3thvg9e/eV ioOoT5f9zNwjlArtXM+EHVJ52x4j7SJ9+yFYhxTTZdKAmJdDwLTy7ggkbtiREBmTEN9TLrF9l3It GfA/WrnALV46n/TYyQX4QewGgUaWBSqGlrtXw1c9IHjJjxHw61Bw8RquN6UIEUbDp4qQeYkcvTCl J+6wa7BDiaF6UX6W4Pbk
X-Report-Abuse-To: spam@mx99.antispamcloud.com
X-Originating-IP: 168.144.250.230
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: unsure
X-SpamExperts-Outgoing-Evidence: Combined (0.16)
X-Recommended-Action: accept
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XU3yVsnRjO1hBEOCtJQsULNoqGw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 05 Nov 2016 17:21:28 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday, November 4, 2016 8:43 AM, Michael Richardson wrote:
 
> There is another option: the people who live in a p=reject policy regime
> could use a different email address for IETF participation.  It's not a
> choice I like very much though.

Been there, done that. It has quite a few nasty side effects. You easily end up also sending work related e-mail from a non-corporate account, for example when you forward an email from a WG list to a colleague at work. That's against many companies' internal policies. Thinks about consequences for example during legal actions, when the opposing party wants to discover all mail related to a particular topic. Does using a parallel server amounts to willful hiding of documents? Are you in contempt of court? Should you store your personal mail on company server so it can be searched? Bottom line, that's indeed not a choice I like much either.

- -- Christian Huitema

-----BEGIN PGP SIGNATURE-----
Comment: Using gpg4o v5.0.7.7563 - http://www.gpg4o.com/
Charset: utf-8

iQEcBAEBAgAGBQJYHhUIAAoJELba05IUOHVQSX4H/22Np5iTJdf5F9N10Y9vVBCJ
a/rqPQwK9DzvdDQRlJFA+Kn6+PRGPK4siI6Nx6eYo578t7WMJUCYFwRX0YJBRZAm
Y8kYBdO5QS/h2U0px67FEyZxask3gsoCW+gPZK1l6ER8ygcTaC3zlKxxbLgUFzXz
8tEIisUr7Xo9y497RKBVzIIpIFZ0wQtH2GipGfFU4p3LOKISnwnUugHePHU3Wt5F
0NLoUVn7c58A40o/B5k2rty2u3q+1m5JUq5iDDMwhumY/qoXvt1D6Ka6m8CkCRZA
OG+xFC62aKIv6IM4D6DlU34fEDt8sxWkGGXb5rIlemlUCItJWKLccyqyFH7wi+Q=
=H+SS
-----END PGP SIGNATURE-----