unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: Richard Stallman <rms@gnu.org>
Cc: Bob Rogers <rogers-emacs@rgrjr.homedns.org>,
	oub@mat.ucm.es, emacs-devel@gnu.org
Subject: Re: gmail+SMTP(only) (oauth2)
Date: Thu, 19 May 2022 14:57:09 +0200	[thread overview]
Message-ID: <87v8u1znmi.fsf@mat.ucm.es> (raw)
In-Reply-To: E1nrS1C-0006oa-RF@fencepost.gnu.org

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

>>> "RS" == Richard Stallman <rms@gnu.org> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]

> It looks like we are making progress on the case of using gmail only
> to receive incoming mail (by forwarding it).  Assuming you can get an email
> account in a place with better policies than Google's.

To be completely clear here. 

    1. That information was a bit unofficial.

    2. Most likely the legal department would warn the user, that in the
       case of missing/disappearing messages it is entirely the user's
       fault, since he/she forwarded the messages. That enough will
       scare most of the users.

> Do schools and employers ever require that you _send_ them mail
> from the Google account you're ordered to use?

I can only speak for my university and the answer is «Yes» it does do,
and that is the core of the problem.

I thought I could modify my «From field» and use either some external SMTP
servers or a SMTP server ones installed on my own machine), however
messages by users more knowledgeable than me convinced me that such
messages will be either blocked or marked as SPAM.

So for the moment I only see two alternatives.

    1. Use google app-password (for this approach one can still use gnus
       (and I presume rmail, vm, etc) vanilla).

    2. Switch to oauth2 (with all the hassle involved).


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

  reply	other threads:[~2022-05-19 12:57 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 [this message]
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

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=87v8u1znmi.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=rogers-emacs@rgrjr.homedns.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).