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

Philip Homburg <pch-ietf-6@u-1.phicoh.com> Wed, 15 March 2017 11:00 UTC

Return-Path: <pch-bF054DD66@u-1.phicoh.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 DB8DE129B55 for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 04:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=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 LeydrvLSkumm for <ietf@ietfa.amsl.com>; Wed, 15 Mar 2017 04:00:25 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9C9B1129B4B for <ietf@ietf.org>; Wed, 15 Mar 2017 04:00:24 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #127) id m1co6fG-0000FQC; Wed, 15 Mar 2017 12:00:22 +0100
Message-Id: <m1co6fG-0000FQC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Subject: Re: Do you really not care whether people accept your mail?
From: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
References: <alpine.OSX.2.20.1703132331590.54839@ary.local> <m1cnjqr-0000GkC@stereo.hq.phicoh.net> <CABa8R6v+ymVRef5_7vCso2xDNAy2XtsAtRP78dbVFcaprFG3iw@mail.gmail.com>
In-reply-to: Your message of "Tue, 14 Mar 2017 16:54:33 -0700 ." <CABa8R6v+ymVRef5_7vCso2xDNAy2XtsAtRP78dbVFcaprFG3iw@mail.gmail.com>
Date: Wed, 15 Mar 2017 12:00:20 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Vq63ovitGfPlX2f3yKrY34bAAzc>
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: Wed, 15 Mar 2017 11:00:27 -0000

>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.

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.

In any case, that's my experience.

In some sense it is amazing how reliable e-mail is. E-mail seems to be
reliable enough that gmail rejecting the occasional e-mail immediately
makes it the most unreliable e-mail provider (for my e-mail). 
That's also an amazing success story.

>> In the context of IPv6 we now have an additional problem. Sites that have
>> filters that are more strict for IPv6 than for IPv4. The obvious very
>> quick workaround for many mail admins is to avoid delivering mail over
>> IPv6.
>> Of course, that just increases the SPAM/HAM ratio, justifying more
>> draconian
>> measures. Which in the end will just kill IPv6 as a transport for e-mail.
>
>Do you imagine that you may be making different choices than others?

Imagine that some will be making different chocies than me, yes.

>There are plenty of senders, in fact the vast majority by volume, who are
>perfectly fine with authenticating their mail.  And many of them send over
>IPv6.  This may be a speed bump, but it is not the death of IPv6 for email
>transport.

It is likely that a few big providers together will make up the vast majority
of e-mail volume.

However, gmail (or in fact any I send mail to) has not made SPF, etc.
mandatory. So if gmail would make DMARC mandatory for IPv4, that would
signal something.

Maybe gmail can publish some graphs, contrasting the percentage of 
mail that arrives over IPv6 to IPv6 adoption for other google services?