unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: gmail+SMTP(only) (oauth2)
Date: Sat, 21 May 2022 08:43:51 +0200	[thread overview]
Message-ID: <87v8tzjsgo.fsf@mat.ucm.es> (raw)
In-Reply-To: 877d6f1wci.fsf@gmail.com

[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]

>>> "TC" == Tim Cross <theophilusx@gmail.com> writes:

> Richard Stallman <rms@gnu.org> writes:

>> 
>> That is rather unclear.  Do you mean that
>> (1) if you fail to have the right From field, your emails could
>> be blocked, or
>> (2) regardless of the From field, your emails could be blocked?

 
> Just to try and be clear for the very last time here. There is NO 100%



Thanks for this very detailed and clear explanation. Very helpful.


> If an organisation adopts Google as their email service provider, it is
> not equivalent to using gmail as your email service provider. While the
> data may use/share some of the same physical infrastructure, the
> policies and procedures, as well as the authentication and authorisation
> processes, can be significantly different.  


> Application passwords may or may not be available with organisations
> which use Google to host their email services. This will depend on the
> policies of the organisation, the level of integration and the
> authentication/authorisation approach adopted by the organisation. 

Just one last remark: according to my university, it is google itself,
who is setting up the its password authentication policy, there is no
room for negotiation. If they decide to not allow app password, there is
nothing the university can do about it. I find this strange, but that is
what I have been told.



-- 
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 --]

      reply	other threads:[~2022-05-21  6:43 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
2022-05-20 22:33 ` Richard Stallman
2022-05-21  1:09   ` Tim Cross
2022-05-21  6:43     ` Uwe Brauer [this message]

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=87v8tzjsgo.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).