From: Colin Baxter <m43cap@yandex.com>
To: Ben Hancock <ben@benghancock.com>
Cc: Fernando de Morais <fernandodemorais.jf@gmail.com>,
help-gnu-emacs@gnu.org
Subject: Re: Rmail tips
Date: Fri, 09 Feb 2024 19:22:15 +0000 [thread overview]
Message-ID: <87cyt5h28o.fsf@yandex.com> (raw)
In-Reply-To: <87le7t68k5.fsf@benghancock.com> (Ben Hancock's message of "Fri, 09 Feb 2024 06:01:14 -0800")
>>>>> Ben Hancock <ben@benghancock.com> writes:
> Fernando de Morais <fernandodemorais.jf@gmail.com> writes:
>> I believe this answer is long overdue and now, after a few months
>> of use, you should have already configured RMAIL to suit your
>> needs.
>>
>> However, here are some recommendations for things that were
>> helpful to me when using RMAIL:
> Thanks for your kind reply and these helpful snippets, Fernando. I
> just recently started using Mairix, which has been great.
> The one thing I still haven't found the optimal approach for in
> RMAIL is filtering mails into dedicated mailboxes -- for example,
> for high-volume mailing lists, that I may want to keep out of my
> regular RMAIL inbox.
> I've tried using the rmail-automatic-folder-directives variable to
> handle this, but it has the downside that mails are marked as seen
> when they are filed away; they also still land in the main RMAIL
> file first.
> My MTA (maildrop) of course can put incoming mails into specific
> files based on conditions. But if I just visit those files with
> RMAIL, i.e. by using the 'i' command, there is also no distinction
> between what is old and what is unseen. It seems that I would have
> to configure those files as separate _inboxes_, and fetch mail
> from them into another RMAIL file.
> That's doable, but I'm wondering if there's another way ... or if
> I should abandon filtering altogether and just search?
I filter incoming mail by means of procmail and then read the mailboxes
using "rmail-input". This might be too simple for what you want, of
course.
Best wishes,
Colin Baxter.
next prev parent reply other threads:[~2024-02-09 19:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 13:58 Rmail tips Ben Hancock
2024-02-07 0:36 ` Fernando de Morais
2024-02-07 11:23 ` Dr Rainer Woitok
2024-02-07 11:50 ` Fernando de Morais
2024-02-07 11:52 ` Stephen Berman
2024-02-09 14:01 ` Ben Hancock
2024-02-09 19:22 ` Colin Baxter [this message]
2024-02-10 7:05 ` Ben Hancock
2024-02-10 8:29 ` Colin Baxter
2024-02-12 13:53 ` Ben Hancock
2024-02-12 14:34 ` Colin Baxter
2024-02-15 16:08 ` Ben Hancock
2024-02-21 6:00 ` Colin Baxter
2024-02-15 13:21 ` Fernando de Morais
2024-02-15 13:23 ` Fernando de Morais
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=87cyt5h28o.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=ben@benghancock.com \
--cc=fernandodemorais.jf@gmail.com \
--cc=help-gnu-emacs@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.
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).