IETF Logo Mail Archive

Re: gmail users read on... [bozo subtopic]

"Andrew G. Malis" <agmalis@gmail.com> Fri, 29 August 2014 21:48 UTC

Return-Path: <agmalis@gmail.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 78B611A02D7 for <ietf@ietfa.amsl.com>; Fri, 29 Aug 2014 14:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-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 fakgOwoGwcHn for <ietf@ietfa.amsl.com>; Fri, 29 Aug 2014 14:48:30 -0700 (PDT)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C64C11A01E8 for <ietf@ietf.org>; Fri, 29 Aug 2014 14:48:30 -0700 (PDT)
Received: by mail-qc0-f174.google.com with SMTP id i17so3016479qcy.5 for <ietf@ietf.org>; Fri, 29 Aug 2014 14:48:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=g7oIUKjN1ueZqFQuwsasYHiA5ZgSDUz56GkTeYNKzRY=; b=AZj6Jj0pVYxvXvgP30A1CHgUdpFqXm2/oP8m6H9URez7ti4K3aUhHcAHkrZuSgXJyp 0OzafuDVBV5NcxGcD6kOtziLFugbuWKXc5UJlC3TuCTZO9yTd4CeTAHdYDd4PmBLQoHh YmzltGNeJ2H7CMWLxGqVzmB1LEeXLEeaUzKosZLKGPDy3v1zGEO3kvJKGELMy6j7nfsI EVpDqCZtHdiSOV34qFxYQwnA+m+thVM31GlVJ5iUnNQ2erJ6gJN2N+tpCxl8yLITpAnW 4nNydVrorc1piTPitRcRw0v37sgZ7Ut0K6SCUe+qZ6yfBVXyxRAnP2nj5F4FcoWsqKfp OOOA==
X-Received: by 10.140.94.163 with SMTP id g32mr20842008qge.77.1409348910007; Fri, 29 Aug 2014 14:48:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.91.99 with HTTP; Fri, 29 Aug 2014 14:48:09 -0700 (PDT)
In-Reply-To: <5400DE33.3020401@gmail.com>
References: <54000A31.5050907@gmail.com> <20140829121101.GA16477@gsp.org> <EE9969EE-D338-4A0B-8C5B-425B638E743B@live555.com> <CABmDk8nPa3cEy_MbkTRpuP65fvQdE5PWux3Dhy5MsUS1_sZrrg@mail.gmail.com> <5400DE33.3020401@gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Fri, 29 Aug 2014 17:48:09 -0400
Message-ID: <CAA=duU2Jr5GNT47o6MAD+nh98BxR0qx1fnoCAho=+Jep2HU=9g@mail.gmail.com>
Subject: Re: gmail users read on... [bozo subtopic]
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary="001a113abd40254d770501cb9d79"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EjjZkLv6qTugrITd7Iu49DJwDp4
Cc: IETF Discussion Mailing 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: Fri, 29 Aug 2014 21:48:32 -0000

On Fri, Aug 29, 2014 at 4:10 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Exactly. Since I switched to gmail for IETF traffic, I have changed
> employers, retired, un-retired and moved countries three times, with
> a stable email environment and no need to fight any corporate or ISP
> policies. The threat of DMARC hassle is the first real problem I've had.
>

I agree with Brian here. It's great having my IETF email stay in one place
and with my choice of email clients, no matter what else is happening
elsewhere. I've also got my gmail filters well-trained. I have noticed the
occasional DMARC-generated false spam positive, but it hasn't been out of
hand (yet).

>From what I've read elsewhere, Mailman 2.1.18 mitigates the DMARC problem.
The IETF is currently using 2.1.15, so once the powers-that-be upgrade us
to 2.1.18, the problem may be solved.

Cheers,
Andy

v2.23.0 | Report a Bug | By Email