public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Anyone here use Proton email service?
Date: Wed, 2 Oct 2024 23:30:58 -0500	[thread overview]
Message-ID: <17e6b499-e2e5-13f0-6d04-8651653a6596@gmail.com> (raw)
In-Reply-To: <2bb23e23-516f-4199-8a90-05676341cf52@youngman.org.uk>

Wol wrote:
> On 02/10/2024 19:47, Dale wrote:
>> Well, I'm not really wanting to do my own email server.  In a way,
>> I'd like to have it so that everything is fetched, stored on my
>> system and then I can use any email software I want, Seamonkey,
>> Thunderbird, Mutt, Kmail or whatever, without losing a single email. 
>> Thing is, even that sounds like more than I care to chew on.  If
>> someone would share configs, editing private info of course, and I
>> could just drop those in and edit with my private info, I might
>> consider it.  Thing is, I'm nervous about doing even that.  Be my
>> luck, I'd screw up something and delete every email I've ever got. 
>> :/   It would be nice tho to have a program fetch my emails and then
>> I can switch email software anytime without losing anything at all.
>
> This is my setup.
>
> I think I've talked about this before, but just emerge and set up
> dovecot.
>
> Make sure you set everything up in the local config file - look at the
> global file that comes with dovecot, and at the end you'll see a
> pointer to a non-existent local file. Set that up, and then make sure
> your email client can see it. Move a couple of emails across and make
> sure they're safe in dovecot.
>
> Then you just set up a rule on your internet provider's inbox, that
> moves emails across to dovecot, and everything is local on your
> system. Obviously, they'll stay on the internet provider's setup until
> they expire, but they're on your system, they can be backed up, and
> they'll not be on the internet to be mined or broken into or whatever
> for long.
>
> Cheers,
> Wol
>
>


I think we tried this and I couldn't get it to work and gave up on it. 
It's been a while back tho.  From my understanding, it is supposed to be
simple but simple doesn't always mean I can do it.  LOL  Email providers
always changing things doesn't help either. 

Would this also work if I moved to Proton or something similar? 

Dale

:-)  :-) 


  reply	other threads:[~2024-10-03  4:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02  4:59 [gentoo-user] Anyone here use Proton email service? Dale
2024-10-02  5:14 ` mad.scientist.at.large
2024-10-02  9:26 ` Arthur R.
2024-10-02 13:02   ` mad.scientist.at.large
2024-10-02 13:10     ` Dale
2024-10-02 14:18       ` Michael
2024-10-02 18:47         ` Dale
2024-10-02 19:10           ` Wol
2024-10-03  4:30             ` Dale [this message]
2024-10-03  8:45               ` Michael
2024-10-03  9:37                 ` Dale
2024-10-03 11:33                   ` Michael
2024-10-03 14:52                     ` Peter Humphrey
2024-10-04  6:16                     ` Wols Lists
2024-10-04  8:01                       ` Dale
2024-10-04 10:11                         ` Wols Lists
2024-10-04 13:52                         ` Michael
2024-10-03 14:44             ` Peter Humphrey
2024-10-03 15:38               ` Arve Barsnes
2024-10-07  8:15   ` gentoo-user

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=17e6b499-e2e5-13f0-6d04-8651653a6596@gmail.com \
    --to=rdalek1967@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