From: John Blinka <john.blinka@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Computer system email no not working since gmail change.
Date: Fri, 27 Sep 2024 12:49:16 -0400 [thread overview]
Message-ID: <CAC_tCmo07ozp18bMrHM0neM785JfNsiaDNENQmURF2YHukdGPw@mail.gmail.com> (raw)
In-Reply-To: <ZvVk1xCnjTlINamE@schatulle>
[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]
On Thu, Sep 26, 2024 at 9:43 AM Frank Steinmetzger <Warp_7@gmx.de> wrote:
> Am Thu, Sep 26, 2024 at 05:44:08AM -0500 schrieb Dale:
>
> > > That said, if you're interested in limiting opportunistic snooping,
> something
> > > like this may help:
> > >
> > > https://proton.me/mail
> >
> >
> > I'll have to check into that more. I'm not sure I could send my system
> > emails through that tho. It sounds like it requires encryption end to
> > end. I think.
> >
> > Dale
>
> I would actually try and set up local mail delivery straight to /var/spool
> without the detour over a network. We’ve had this topic already, methinks.
> You can then add the folder to Thunderbird/Seamonkey, since spool usually
> is
> mbox format, which is also the default in TB.
>
> --
> Grüße | Greetings | Salut | Qapla’
> Please do not share anything from, with or about me on any social network.
>
> If a snowball is a ball of snow – what, then, is a football?
>
Exactly. I used to send system email out through gmail, but after periodic
breakages in that route due to Google security changes, I realized keeping
these emails within my local network was a more reliable, lower hassle
alternative for me: postfix/dovecot/mutt. I just use it for system mails,
so config was straightforward. No more gmail config hassles, no more Google
reading my emails. The one time I’ve been hacked was through gmail, so I’ve
also eliminated a security risk.
Not the answer to the question asked, so possibly not a useful one, but
maybe food for thought.
John Blinka
[-- Attachment #2: Type: text/html, Size: 2191 bytes --]
next prev parent reply other threads:[~2024-09-27 16:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 2:44 [gentoo-user] Computer system email no not working since gmail change Dale
2024-09-25 20:43 ` Dale
2024-09-26 7:13 ` covici
2024-09-26 7:28 ` Dale
2024-09-26 8:56 ` Michael
2024-09-26 10:44 ` Dale
2024-09-26 11:16 ` Michael
2024-09-26 15:42 ` Dale
2024-09-26 17:54 ` [gentoo-user] " Grant Edwards
2024-09-26 17:58 ` Grant Edwards
2024-09-26 20:20 ` Dale
2024-09-26 20:42 ` Grant Edwards
2024-09-26 21:03 ` Grant Edwards
2024-09-27 0:19 ` Dale
2024-09-26 21:11 ` Dale
2024-09-26 21:22 ` Grant Edwards
2024-09-27 0:08 ` Dale
2024-09-27 2:40 ` Grant Edwards
2024-09-27 4:47 ` Dale
2024-09-27 13:47 ` Grant Edwards
2024-09-27 14:11 ` Dale
2024-09-27 14:48 ` Grant Edwards
2024-09-27 15:33 ` Dale
2024-09-27 16:00 ` Grant Edwards
2024-09-27 16:28 ` Dale
2024-09-27 16:53 ` Michael
2024-09-27 10:31 ` Michael
2024-09-27 12:11 ` Dale
2024-09-27 13:06 ` Michael
2024-09-27 14:13 ` Dale
2024-09-26 12:47 ` Grant Edwards
2024-09-26 15:18 ` Dale
2024-09-26 13:42 ` [gentoo-user] " Frank Steinmetzger
2024-09-27 15:51 ` Dale
2024-09-27 16:49 ` John Blinka [this message]
2024-09-26 11:49 ` covici
2024-09-26 12:49 ` [gentoo-user] " Grant Edwards
2024-09-26 16:09 ` [gentoo-user] " Matt Connell
2024-09-27 15:58 ` Dale
2024-09-26 9:03 ` Wolfgang Müller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAC_tCmo07ozp18bMrHM0neM785JfNsiaDNENQmURF2YHukdGPw@mail.gmail.com \
--to=john.blinka@gmail.com \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox