From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Email clients
Date: Sun, 30 Jul 2023 20:02:47 +0100 [thread overview]
Message-ID: <20230730200247.27903c0b@digimed.co.uk> (raw)
In-Reply-To: <b05601a1-22f7-9564-6781-f88dda5f80d3@youngman.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
On Sat, 29 Jul 2023 12:23:47 +0100, Wols Lists wrote:
> > Hm. I already have Dovecot on my LAN server, because KMail is
> > horribly buggy with POP3, which is what my ISP offers. So fetchmail
> > -> postfix -> dovecot became necessary before I could use IMAP4 in
> > KMail.
> >
> > All incoming emails are transferred to my workstation because I like
> > to have everything in one place and one backup.
> >
> > Maybe I'll stick with KMail a bit longer...
>
> Well then, install Claws and try it - just point it at Dovecot. Okay, I
> use Thunderbird, but there's no reason I have to - I run about 4
> different instances of TB, all pointing at my Dovecot server, and all
> mail is visible on all my computers - the server/workstation, my old
> laptop, my new laptop, my wife's laptop when I borrow it, ...
Similarly, I use Claws 99% of the time, but occasionally run Thunderbird.
Neither program cares that I have also used the other to read my mail.
--
Neil Bothwick
"If Micro built cars, the worlds population would be in decline"
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-30 19:03 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 0:29 [gentoo-user] Email clients Peter Humphrey
2023-07-29 0:38 ` Jack
2023-07-29 2:37 ` Bryan Gardiner
2023-07-29 8:52 ` Wols Lists
2023-07-29 10:13 ` Arsen Arsenović
2023-07-29 11:20 ` Wols Lists
2023-07-29 13:54 ` Arsen Arsenović
2023-07-29 14:21 ` Wols Lists
2023-07-29 14:50 ` Arsen Arsenović
2023-07-29 16:27 ` Wols Lists
2023-08-02 7:16 ` [gentoo-user] " Nuno Silva
2023-07-29 5:53 ` [gentoo-user] " Philip Webb
2023-07-30 12:07 ` Frank Steinmetzger
2023-07-30 12:25 ` Peter Humphrey
2023-07-29 6:56 ` Neil Bothwick
2023-07-29 11:01 ` Peter Humphrey
2023-07-29 11:23 ` Wols Lists
2023-07-30 19:02 ` Neil Bothwick [this message]
2023-07-30 22:53 ` Peter Humphrey
2023-07-30 23:11 ` Neil Bothwick
2023-07-31 7:34 ` Wols Lists
2023-07-31 12:33 ` Peter Humphrey
2023-07-31 13:26 ` Neil Bothwick
2023-07-31 16:03 ` Peter Humphrey
2023-07-31 16:25 ` Peter Humphrey
2023-07-31 17:26 ` Peter Humphrey
2023-07-31 18:13 ` Neil Bothwick
2023-07-31 18:17 ` Michael
2023-08-01 9:53 ` Peter Humphrey
2023-08-01 10:42 ` Michael
2023-08-01 16:56 ` Peter Humphrey
2023-07-31 17:57 ` Michael
2023-08-01 9:55 ` Peter Humphrey
2023-07-31 18:14 ` Neil Bothwick
2023-07-31 14:19 ` Wols Lists
2023-07-31 15:55 ` Peter Humphrey
2023-08-01 18:51 ` Wols Lists
2023-08-01 23:39 ` Peter Humphrey
2023-07-29 9:26 ` Michael
2023-07-31 1:12 ` Matt Connell
2023-07-31 16:14 ` Peter Humphrey
2023-07-31 16:59 ` Matt Connell
2023-07-31 17:16 ` Alexe Stefan
2023-07-31 17:23 ` Matt Connell
2023-07-31 17:32 ` Kusoneko
2023-07-31 17:52 ` [gentoo-user] " Grant Edwards
2023-07-31 18:46 ` Kusoneko
2023-07-31 18:57 ` Matt Connell
2023-07-31 20:22 ` Grant Edwards
2023-07-31 20:24 ` David Rosenbaum
2023-07-31 19:27 ` [gentoo-user] " Laurence Perkins
2023-07-31 17:36 ` Jack
2023-07-31 17:43 ` [gentoo-user] " Grant Edwards
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=20230730200247.27903c0b@digimed.co.uk \
--to=neil@digimed.co.uk \
--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