Re: Do you really not care whether people accept your mail?

Brandon Long <blong@google.com> Thu, 16 March 2017 00:54 UTC

Return-Path: <blong@google.com>
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 B08C112EAA1 for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 17:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 YEZVSXdmFz5s for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 17:54:05 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 0631D12EA81 for <ietf@ietf.org>; Wed, 15 Mar 2017 17:54:05 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id o4so22096129ywd.3 for <ietf@ietf.org>; Wed, 15 Mar 2017 17:54:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=nGN29pxc1COte6DWuNsdO02sRAb4uTHPrPIMQz8rKmM=; b=AwR7cven7kL80KJq5REzSo8R1pBIh0ufyY6Pqi04+zaeMNvPyeHu491w0A/I19WB/A nQOr8Bou0BJXrXDKccP5WdeLTeKRDo5U+g28sXUD98G1tTZXpE/WsB9XiNXvQBhNYEtH lb4l5TzY+SVFf4dE2EEx/DZIyVK1XfFBOxDSyW0mNpW8UgmLrWxs+aKxI9WVC5oTJfDI bek4LwQVwS6BFTZo0fsNG69cGRFilYctiy6kLoCLJAYGRcGmWULlLhtwUVhXiULz5dT4 CB3OSt1V5bz5UopBbTr6yfC0sS5spQ0bHOjG+S8DOVNK7MQkB/t7AksWdbo1is+zhHgF rpzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=nGN29pxc1COte6DWuNsdO02sRAb4uTHPrPIMQz8rKmM=; b=Y2a3rnQ42qfa4wQODUOqPMpxjNPcIjn+pmbszunM/JSEkkCruirDpJcB2GeEdBwGMz zmqN1S3SRihUp3z17Zihp7i3qhz7Ay0kd8qBukE51pxQbnEeCZWLb2MLLA3XFzQJkRC6 OGGo1/cv2XArwbeErW7eCFLXWbqGb6jhWtD75GrAmnXHQbSz7Brrr8XJ0DgdPZ4AbITn 5sOXMKUxR1L7VOLcCl1plmuaIuaghYly45FyIPvLYsgUopRyLK8n7PVZ/Jt/x3LepIs7 DrXBT28BnD/xavJzxpLLcIALhVN5ZOzPkYialyLfhXoIXTecfIpxj+uHQP0olK/nhPbF nsEA==
X-Gm-Message-State: AFeK/H2ONlZpTnbVYLnxBY02yI6aEevDhy8+wnpXMrf15gzLH2UXES/AeYoAOUpl/u644tpTPvxa2UG2uQ9MmpS5
X-Received: by 10.37.192.16 with SMTP id c16mr625030ybf.195.1489625643525; Wed, 15 Mar 2017 17:54:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.220.11 with HTTP; Wed, 15 Mar 2017 17:54:02 -0700 (PDT)
In-Reply-To: <20170315153502.GA7490@localhost>
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <m1cnjqr-0000GkC@stereo.hq.phicoh.net> <CABa8R6v+ymVRef5_7vCso2xDNAy2XtsAtRP78dbVFcaprFG3iw@mail.gmail.com> <m1co6fG-0000FQC@stereo.hq.phicoh.net> <20170315153502.GA7490@localhost>
From: Brandon Long <blong@google.com>
Date: Wed, 15 Mar 2017 17:54:02 -0700
Message-ID: <CABa8R6u_cU3wrzzcfrn-BHLxCx9EnM3R9usb73FSgTHOvcoWoA@mail.gmail.com>
Subject: Re: Do you really not care whether people accept your mail?
To: Nico Williams <nico@cryptonector.com>
Cc: Philip Homburg <pch-ietf-6@u-1.phicoh.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113a119a55215e054ace7fdf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Emikb421DneQsijdfjdudjESn_s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 16 Mar 2017 00:54:07 -0000

On Wed, Mar 15, 2017 at 8:35 AM, Nico Williams <nico@cryptonector.com>
wrote:

> On Wed, Mar 15, 2017 at 12:00:20PM +0100, Philip Homburg wrote:
> > >On Tue, Mar 14, 2017 at 3:38 AM, Philip Homburg <
> pch-ietf-6@u-1.phicoh.com>
> > >wrote:
> > >> In my experience, essentially no mail gets lost if you leave out SPF,
> DKIM,
> > >> DMARC. The only exception is gmail that occasionally rejects e-mail.
> > >
> > >"no mail gets lost" != "gmail occasionally rejects my mail"
> >
> > What I meant to write is that when I take all e-mail targets that I send
> e-mail
> > to, leaving out gmail, then sending mail without SPF, DKIM, DMARC works
> just
> > fine.
> >
> > Gmail is an exception because it seems that gmail is broken if you
> deliver
> > mail without SPF, etc. over IPv6 to gmail. That's unique to gmail.
>
> The problem is twofold: a) gmail has a huge number of mailboxes, so if
> you can't deliver to them without SPF/DKIM/DMARC, then your mail truly
> is broken, b) they could be setting the rule, so that even if you don't
> mind (a), you soon will feel the pain.
>
> > So if your outgoing mail doesn't have SPF, etc. and you do have IPv6,
> then
> > you have to think about what to do with gmail.
>
> As a user, when I send email, I don't want to think about this sort of
> thing.  An admin has to think about this sort of thing, and it's looking
> a lot like email is nowhere near the relatively easy service to run that
> it was in the 90s.
>

Do you run spam filters on your mail server today? Do you run an open relay?
Does your mail client support html email?  How about MIME?

Yes, running a mail server today is not like it was 25 years ago.


> > >Do you imagine that you may be making different choices than others?
> >
> > Imagine that some will be making different chocies than me, yes.
>
> Balkanizing email doesn't sound very good to me.


Is it balkanizing email to require five minutes to set up an SPF record?
Not setting it up is a choice to be on the outside.

Imagine if instead they were refusing to add an IPv6 address to their mail
server, so they wouldn't ever be able to send to an IPv6 only MX.  Who is
making the choice to balkanize then?

Brandon