IETF Logo Mail Archive

Re: [ietf-822] WSJ/gmail/ML, was a permission to...

"John R Levine" <johnl@taugh.com> Mon, 05 May 2014 14:03 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 990BE1A035D for <ietf-822@ietfa.amsl.com>; Mon, 5 May 2014 07:03:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level:
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 cJ0TKz9uAtXv for <ietf-822@ietfa.amsl.com>; Mon, 5 May 2014 07:03:14 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB061A035A for <ietf-822@ietf.org>; Mon, 5 May 2014 07:03:13 -0700 (PDT)
Received: (qmail 33753 invoked from network); 5 May 2014 14:03:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=83d8.53679a1d.k1405; bh=xel5r2KZ9wQsCYolSonGYFcs9X9kLs4j/qHRthyi7os=; b=McjZDAaSbUhRZiG/jHs3iArkWlt8LiJpEevdNQqt0UBBdZXB9IySksJQtR8zswvhuWUCfJWxMLk4G4bVup3DjzAbErhBiYS5ZBjUieWWDvpM0+DI3OVvkUD8v169mIldARgaXetNSm4g/cQx7R9bWqPG6h4dKXhpnj3tG6NdL4qLMkVzHJPgb+CwU/b5YTME136M36f2ZEgb8+spETXfet2/bOi2OH7kF22LAqZ5wwoVyNPkPNOoCztHTi6QK1mR
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=83d8.53679a1d.k1405; bh=xel5r2KZ9wQsCYolSonGYFcs9X9kLs4j/qHRthyi7os=; b=bEwFQApRUm1Hd4ITVxZ6AfxGrbRb+I55C4M40RG/ReYugdxMm58GwF7HH/5KnLvB8abe24bSIJ9M+0Ju/QajLsQZGbS6GqbhvoOPSU3ZMqbsRV7nqs/D3YVpmy/WSFRYa+5ke6UgA8L6Pg13x+6YKpsAajTXFJGhpoepEKTOV2BWOYmD4w7Vasf12iG2QMWBGZV+x4kspOgwhia82T0b5pNrbVU3DPW8LaG8gWqlaa+L5RaWU/9CaUQuYMYB59WD
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 05 May 2014 14:03:09 -0000
Date: Mon, 05 May 2014 10:03:08 -0400
Message-ID: <alpine.BSF.2.00.1405050957230.56860@joyce.lan>
From: John R Levine <johnl@taugh.com>
To: Brandon Long <blong@google.com>
In-Reply-To: <CABa8R6tSpasb7od7ixQXLXnV0Q+3jFNPVKAw+-+Fd_7traumiQ@mail.gmail.com>
References: <20140418123721.3610.qmail@joyce.lan> <5365357D.2020101@tana.it> <CABa8R6tSpasb7od7ixQXLXnV0Q+3jFNPVKAw+-+Fd_7traumiQ@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/kKbUGuTKYwzzJ4YTu5yOO2xCDT8
Cc: ietf-822@ietf.org
Subject: Re: [ietf-822] WSJ/gmail/ML, was a permission to...
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 May 2014 14:03:15 -0000

>> Those two problems can be solved in different ways.  Gmail could use a
>> third party's submission server just like they use its pop/imap one.
>
> Gmail does allow you to use a third party submission server, and it looks
> like we may have to encourage its use even more in the future.

I'm not sure how realistic that is in practice for users who aren't 
uber-nerds.

To set up to use Yahoo's submission server from Gmail, I tried to 
configure it in the popup Gmail provided, which failed with an error 
message that told me to go log in at Yahoo.  I did, didn't help.  After 
some poking around I found a message in my Yahoo inbox that suggested I 
needed an app specific password.  (How many people will realize that Yahoo 
considers Gmail to be an app?)  It provided a link to the place in their 
credential server to create such a password, which is otherwise not easy 
to find.  So I finally found it, and made a password for Gmail, and then 
went back to Gmail, and used it, and indeed it worked.

But how many people without CS degrees are going to be able to go through 
all that?

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

v2.23.0 | Report a Bug | By Email