From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.devel Subject: Re: Making GNUS continue to work with Gmail Date: Wed, 12 Aug 2020 10:13:54 -0700 Message-ID: <87sgcru6r1.fsf@ericabrahamsen.net> References: <87v9ienz6c.fsf@gnus.org> <878sf9c69y.fsf@gnus.org> <871rkw62t3.fsf@gnus.org> <87bljki71n.fsf@mat.ucm.es> <87364wxlec.fsf@gnus.org> <87imdsgmlw.fsf@mat.ucm.es> <871rkfhkhc.fsf@mat.ucm.es> <875z9p5hnc.fsf@mat.ucm.es> <87ft8shzjt.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18785"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org, Eric S Fraga To: Arthur Miller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 12 19:16:12 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k5uMF-0004nc-TW for ged-emacs-devel@m.gmane-mx.org; Wed, 12 Aug 2020 19:16:11 +0200 Original-Received: from localhost ([::1]:41394 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k5uME-0002Lc-W1 for ged-emacs-devel@m.gmane-mx.org; Wed, 12 Aug 2020 13:16:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54742) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k5uKD-0000Bz-FF for emacs-devel@gnu.org; Wed, 12 Aug 2020 13:14:05 -0400 Original-Received: from ericabrahamsen.net ([52.70.2.18]:55460 helo=mail.ericabrahamsen.net) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k5uKB-0000KN-Ho for emacs-devel@gnu.org; Wed, 12 Aug 2020 13:14:05 -0400 Original-Received: from localhost (c-73-254-86-141.hsd1.wa.comcast.net [73.254.86.141]) (Authenticated sender: eric@ericabrahamsen.net) by mail.ericabrahamsen.net (Postfix) with ESMTPSA id 31352FA1FD; Wed, 12 Aug 2020 17:13:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericabrahamsen.net; s=mail; t=1597252436; bh=G5wibeHy0loc+cqxy6yQIMRs0tv5obCozb/Fm2xkyE4=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=XRKvkCAuAPlh7dSXCL7OF9XRkODR9TM4oD7Ns8aHPtjR81/EUWJ+nJehvURejbRfV BfXV5JOtyvHKI7K83qjH42qdLjgQ5vzRN3xcTPALBk2oIODPx4JsPkPBVFhLTyJdjn Uaq6SA/TbHJBHLd5f5PuCtONixBQEH5NPbR05HXw= In-Reply-To: (Arthur Miller's message of "Wed, 12 Aug 2020 14:40:08 +0200") Received-SPF: pass client-ip=52.70.2.18; envelope-from=eric@ericabrahamsen.net; helo=mail.ericabrahamsen.net X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/12 13:13:57 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:253704 Archived-At: Arthur Miller writes: > Eric S Fraga writes: > >> On Tuesday, 11 Aug 2020 at 18:11, Robert Pluim wrote: >>> I=CA=BCm starting to agree with Stefan here: maybe it=CA=BCs time to st= art using >>> a different email provider. > >> The long term solution is your own domain etc. > Domain itself is maybe not enought, you probably think of running own > mailserver/website etc? For Gmail users, one potential "intermediate step" could look like: - Get your own domain - Start a Google Apps account as part of your google account, using your new custom domain. - Use this new domain as a new Gmail account - Start the long process of "external migration": getting people to stop using your @gmail.com account, and start using your @custom.me account. Set up automatic forwarding from gmail to custom, etc. - Set up a local sync of your @custom.me mail - When you're ready, switch your @custom.me MX records to your new mail provider, and sync mail up to it. This way you can take as long as you like to do the social work of migrating to a new email address. Another bonus is that, since Google once saw @custom.me as a gmail-backed address, it will have whitelisted it for deliverability. My understanding is that that whitelist doesn't go away after you switch your MX records, solving (one part of) your potential deliverability problem. I have no insight into how Google works, this is just what I've heard. I did this with two different email addresses (luckily I never used @gmail.com, they were custom from the start) and I have had nearly no gmail-related deliverability problems since switching to self-hosting my email. YMMV, in a big way. Eric