Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "Björn Bidar via Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader (in English)" <>
Subject: New to GNUS troubles in figuring how to get rings rolling
Date: Tue, 25 Oct 2022 01:10:38 +0300	[thread overview]
Message-ID: <> (raw)


I have been working on having Emails working inside Emacs.
I've looked into a few solutions which seem to be the most used.
These were offline mail solutions such as mu4e, those that can fetch
mail themselves like gnus or wanderlust.

My current setup is that I have multiple clients that all connect over
I want always sync the status of a message back to imap.
My imap server is a self hosted dovecot with postfix to send messages.

I'm trying gnus right now and faced some issues that I don't know on how
to continue on.

These are mostly imap related.
1. How can I take the read status from imap into gnus and vice versa?
2. I tried to use ~nnimap-use-namespaces~ however it doesn't work.
   My mail server supports the extension however the folders aren't
   split accordingly.
3. Can I make gnus design less archiaric?
4. Can I make imap folders appear as groups by subfolder? E.g.
   if I have INBOX.Bar.Foo -> Bar will be a group.

All in all it wasn't as bad as other said around the internet however
the manual isn't as easy to digest: things are hard to find or out of
date/not relevant to modern usage, this makes the manual harder to

Have a great day,


             reply	other threads:[~2022-10-24 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 22:10 Björn Bidar via Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader (in English) [this message]
2022-11-11 20:55 ` TRS-80
2022-11-12  5:44   ` Björn Bidar

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).