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: Kmail: Gmail (less secure apps) advice for GNU emacs developers.
Date: Thu, 13 Aug 2020 08:57:38 +0200	[thread overview]
Message-ID: <87tux71199.fsf@mat.ucm.es> (raw)
In-Reply-To: jwvwo25t42s.fsf-monnier+emacs@gnu.org

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

>>> "SM" == Stefan Monnier <monnier@iro.umontreal.ca> writes:

   >> > FWIW, this has been discussed at my workplace as well, tho luckily it
   >> > hasn't happened (yet?).  At that time, I had considered what I'd do, and
   >> > I concluded that I'd most likely setup a forwarding on my (gmail) work
   >> > email and buy a more respectable email service like `posteo.de`.
   >> 
   >> Oh no, I might try out dovecot, but even if it works, it will occupy
   >> a huge amount of my disk.

   > Not sure what you're saying, but I'm only suggesting to use some other
   > provider instead of Google.  No need to install&manage anything
   > like dovecot.

The problem with another provider is:

    1. My Gmail account actually occupies some 22 GB, I presume to have
       that amount of space in any other provider will need some
       payment. While I might consider this for my private account, I
       don't feel like I should pay for my work account.

    2. The other provider must allow me to send email using the from of
       my work address, as google does.

    3. That is why I thought to stay with gmail but to go back to use
       dovecot (if their figured out how to connect to an gmail, with
       the new identification process). I did this in the past and the
       downside of this approach is that I will end up with an
       additional 22GB on my laptop and more in the future.

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

  reply	other threads:[~2020-08-13  6:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87o8njdlvs.fsf@mat.ucm.es>
     [not found] ` <1897936.H7q943mS67@merkaba>
     [not found]   ` <5532801.MhkbZ0Pkbq@twilight>
2020-08-10 16:20     ` Kmail: Gmail (less secure apps) advice for GNU emacs developers Uwe Brauer
2020-08-10 16:46       ` Allan Sandfeld Jensen
2020-08-10 22:37       ` Stefan Monnier
2020-08-11 18:15         ` Uwe Brauer
2020-08-11 18:53           ` Stefan Monnier
2020-08-13  6:57             ` Uwe Brauer [this message]
2020-08-13  8:13               ` Robert Pluim
     [not found]     ` <21978174.sr7ieKrsik@beastie.bionicmutton.org>
2020-08-13  8:49       ` Uwe Brauer
2020-08-14  2:55         ` Richard Stallman
2020-08-14  4:25           ` 황병희
2020-08-14 10:16           ` Lars Ingebrigtsen
2020-08-15  4:40             ` Richard Stallman
2020-08-15  9:14               ` Martin Steigerwald
2020-08-15  9:20                 ` Martin Steigerwald

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