From: Harry Putnam <reader@newsguy.com>
Subject: Re: Splitting and procmail
Date: Sun, 08 Sep 2002 17:31:26 -0700 [thread overview]
Message-ID: <m3fzwkgg0x.fsf@newsguy.com> (raw)
In-Reply-To: <87r8g43b21.fsf@dishevelled.net> (Mark Triggs's message of "Sun, 08 Sep 2002 22:44:54 +1000")
Mark Triggs <mst@dishevelled.net> writes:
>> So, my question is now: Mail splitting cannot be used togeather with
>> procmail, right?
No wrong, using them together can give twice the power and agility.
Here is how I do it. I never knew about the variable Reiner
mentioned `nnmail-resplit-incoming' not sure what it does. But we've
always been able to replit a group with `B r'.
I have procmailrc setup so that a final catchall group is listed
after all spam (or other) rules. That way all spam etc is sorted,
then anything left is dumped into a file I call prinb.in
(preinbox.in)
At the end of procmailrc:
:0
prinb.in
Everything that wasn't spam or something else I sort with procmail,
is now in ~/spool/prinb.in
Now when I press `g' in gnus, it slurps prinb.in into nnml:prinb
I scan that group by eye, inside gnus, see if I want to take any
actions right then, if not press `M-P a (select all) B r
(respool). and the group nnml:prinb is split according to my nnmail-split
setup. (I actually have a keyboard macro set to run the above
commands with a keycombo C-x C-z).
I find that I recognize most stuff that needs attention on the first
visual scan, after splitting, anything I missed will be sent to the
appropriate group where I will notice the new message count.
But my mail only amounts to some 150 to 200 per day incoming.
No tricky stuff on mail-sources, just the normal type setup one uses
with procmail:
(setq mail-sources
'((directory :path "/home/reader/spool/" :suffix ".in")))
So to summarize: What you want to do can all be done by setting a
catchall at the end of procmailrc, sort it after gnus slurps it with
nnmail-split rules.
next prev parent reply other threads:[~2002-09-09 0:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-08 8:40 Jonas Steverud
2002-09-08 12:33 ` Reiner Steib
2002-09-09 0:14 ` Harry Putnam
2002-09-09 9:30 ` Kai Großjohann
2002-09-09 12:39 ` Reiner Steib
2002-09-09 13:06 ` Kai Großjohann
2002-09-09 13:54 ` Reiner Steib
2002-09-09 14:09 ` Kai Großjohann
2002-09-09 16:39 ` Harry Putnam
2002-09-08 12:44 ` Mark Triggs
2002-09-08 14:31 ` Jonas Steverud
2002-09-09 0:31 ` Harry Putnam [this message]
2002-09-09 4:32 ` Mark Triggs
2002-09-09 3:40 ` Scott A Crosby
2002-09-09 9:32 ` Kai Großjohann
2002-09-10 11:25 ` Jonas Steverud
2002-09-11 13:29 ` Jonas Steverud
2002-09-13 17:51 ` Jonas Steverud
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=m3fzwkgg0x.fsf@newsguy.com \
--to=reader@newsguy.com \
/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 NNTP newsgroup(s).