From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: gmail+SMTP(only) (oauth2)
Date: Thu, 19 May 2022 15:01:55 +0200 [thread overview]
Message-ID: <87o7ztznek.fsf@mat.ucm.es> (raw)
In-Reply-To: 87fsl7l3c8.fsf@gmail.com
[-- Attachment #1: Type: text/plain, Size: 2189 bytes --]
> Uwe Brauer <oub@mat.ucm.es> writes:
> My recollection is that when Google originally announced the intended
> changes (back in 2017 or 2018), they indicated they would be removing
> app passwords. However, when I go through their current announcements
> and documentation on their support site, I cannot find any mention of
> removing them. Furthermore, much of their documentation appears to have
> been updated to state that app passwords are the preferred solution for
> clients who cannot do oauth2/2FA. My guess is that there was sufficient
> push-back after the original announcement that they reviewed their
> proposal and are going to leave app passwords in place for the time
> being. Even if they do decide to remove them, I would expect they will
> give a fairly lengthy notice period (It has been 4+ years since they
> flagged the removal of being able to use your normal google password).
Aha, thanks, htat is helpful, and good to know.
> I would just use app passwords and wait to see what happens. A lot can
> change in a couple of years.
Right.
> That might help if the initial sending SMTP server is on your machine
> and it is registered in the global DNS (not just an internal only DNS).
> It means your machine has a real IP address (not a non-routed address
> like 192.168.*.* or 10.*.*.* etc).
[Snip]...
> One of the reasons this is so hard to work out is because there are just
> so many different options and moving parts and the constant need to
> evolve and adapt anti-spam measures as the spammers find new loopholes
> and ways to circumvent spam prevention. I suspect it is one reason many
> organisations have decided to adopt an external service provider and
> drop in-house SMTP services.
Right, that makes sense. I am now convinced that this idea of using my
own SMTP server will fail and I will therefore give the app-password a
try.
Thanks for you detailed explanation.
Uwe
--
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military.
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-05-19 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 16:34 gmail+SMTP(only) (oauth2) Uwe Brauer
2022-05-17 22:18 ` Bob Rogers
2022-05-18 22:19 ` Richard Stallman
2022-05-19 12:57 ` Uwe Brauer
2022-05-22 22:58 ` Richard Stallman
2022-05-18 0:09 ` Tim Cross
2022-05-18 6:15 ` Uwe Brauer
2022-05-18 6:35 ` Tim Cross
2022-05-19 13:01 ` Uwe Brauer [this message]
2022-05-20 22:33 ` Richard Stallman
2022-05-21 1:09 ` Tim Cross
2022-05-21 6:43 ` Uwe Brauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7ztznek.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).