[174363] in North American Network Operators' Group
Re: no more "Send through Gmail" option
daemon@ATHENA.MIT.EDU (Hugo Slabbert)
Fri Sep 5 19:02:07 2014
X-Original-To: nanog@nanog.org
Date: Fri, 5 Sep 2014 16:01:53 -0700
From: Hugo Slabbert <hugo@slabnet.com>
To: Royce Williams <royce@techsolvency.com>
In-Reply-To: <CA+E3k91amZGcU-Yhjvt-=8DcXQDhFfrAQaCSDWEB23dS76rcEg@mail.gmail.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
--aFi3jz1oiPowsTUB
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
>If it really was more the former, there would be a "if your SPF
>records include:_spf.google.com, you can still do it" option, IMO.
Manager: So, you're saying if we just check the SPF record when they set=20
up the account, we could still let them do it.
Tech: Yes, except if they also use DKIM; then it's a no-go.
Manager: Okay, so if their SPF record includes Google's and they don't=20
have DKIM, then we'd be okay?
Tech: Yes...but if they don't have an SPF record when they set up the=20
account and then add one later, we'd still be in trouble.
Manager: ...
Tech: I guess we could do periodic checks for SPF records on their=20
domains and either disable sending or send them an alert if an SPF=20
record is created that could problems?
Manager: ...okay...and then it'd be okay?
Tech: Well, if they don't have DKIM to start and then add it, that would=20
also be a problem.
Manager: ...
Tech: ...but in addition to doing checks for new/altered SPF records, we=20
could also do checks if they add DKIM after adding the account.
Manager: ...
Tech: ...or we could just turn it off.
Manager: Works for me.
On Fri 2014-Sep-05 14:43:19 -0800, Royce Williams <royce@techsolvency.com> =
wrote:
>On Fri, Sep 5, 2014 at 2:15 PM, Eduardo A. Su=E1rez
><esuarez@fcaglp.fcaglp.unlp.edu.ar> wrote:
>>
>> Hi,
>>
>> according to this thread:
>>
>> https://productforums.google.com/forum/#!category-topic/gmail/GyeMcHv1U-=
g%5B1-25-false%5D
>>
>> Gmail isn't allowing anymore "Send through Gmail" option.
>
>Yep. Existing email-address setups are grandfathered, but no new ones
>can be added via the UI.
>
>It's probably a mix of "let's support the ecosystem by only sending
>mail from servers authorized by the domain holder" and "let's sell
>more Google for Work email hosting".
>
>If it really was more the former, there would be a "if your SPF
>records include:_spf.google.com, you can still do it" option, IMO.
>
>Royce
--=20
Hugo
--aFi3jz1oiPowsTUB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBCgAGBQJUCkDhAAoJEJqxD/2xeDE+pAsQAKy/BxEyD6UCgV3b0Qsgh9W/
/1QQ6qjQ7nEXlLX5YQDFP+JXQmJM0bXB3YflmHjkAtaL3fl7VnPnA/kImr9mBd1H
2D8jcv8Q8u/r5sTiXHsGJ3pQIkc3Htlm1EcYFDKxiL/jaG7gZ2T2MMdBSeUBnRF4
Y3lyFkvrcmwAcmjkpPtfdIsSKfFUC3VCoUw0uCgKyrLJlL28siiFikicIYkKUTLS
12e52sZFCEJgXpJeSOlgKmO3kd1Bi4q8/aaYoJtvkCdAdybUXe0bk0Iqk5L6EtjW
y9/Z5e5jqAHnBzb63iwe/Fr9gQLfCENtRzZ/XyM1QH99He2M/NooA4hdiJpAiFC9
SWsrdQi+lb93wGIgFrHVK0cGRshoy3ZptrGU30pML8aMnlQiRpDxNhIbDOX0WpXV
PPcLwLXj0MK3YUifj+8KafDlMq7JloFMjkJ4o7YQKfvrL0bx60nIQatAtFuGU6Dr
Txf+eh8P4DQuQl8mUEc76KRfI8/ZRhUfwTUNAM/vTVrRAudPyfZQp+8UZ5Ccw9+F
xhLy8BW0MacwWDXBcc4X6bExCytIoI7gJs9tuGlL3TPmqo4NejUg2mZe9PSz3X3e
S4fSA2kKgDU1kT4G/ir90t8+ZRr7rJiX+xnANVJXTnSgh+Ue7ajhlgIXmloJzwUy
A7ZLkddIckJccNrBCZVQ
=ps3s
-----END PGP SIGNATURE-----
--aFi3jz1oiPowsTUB--
