Gnus development mailing list
 help / color / mirror / Atom feed
From: Steve Evans <stevee@gorbag.com>
Subject: Re: [POLL]: Procmail or native gnus splitting ?
Date: Mon, 14 Jul 2003 07:34:55 +0100	[thread overview]
Message-ID: <m3brvxobu8.fsf@kosh.local> (raw)
In-Reply-To: <plop87el0xsh4q.fsf@gnu-rox.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11 Jul 2003, zedek@gnu-rox.org wrote:

> Hello,
>
> I am just submitting a poll on every Gnus board I can to ask people
> what do they use to classify theirs mails.
>
> It is a consequence of the redaction of an article on 'how to get
> IMAP and Gnus play fairly together' on the Gnus French site [1].
> There, I've been told not to talk about nnimap splitting feature
> because numerous people used to use procmail base filter to split
> their incoming mails.
>

I use both procmail and Gnus splitting. Procmail is used to separate
stuff from mailing lists and spam into their own spool files. Gnus
splitting is then used to refine the remainder.

I do it like this so that I can use a biff type program, in my case
kbiff, which only looks at the default spool file. That way it tells
me when I have important mail that I should probably look at now, but
not have it get swamped by stuff that can wait. I use the same setup
at work, where it is particularly useful.

Steve
- -- 
____________________________________________________________________
Steve Evans            E-mail: mailto:stevee@gorbag.com
                       WEB:    http://www.gorbag.com
Registered Linux user #217906: http://counter.li.org
Public Encyption Key:          http://www.gorbag.com/public-key.html
____________________________________________________________________
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE/Ek8Pe55D0k1e/z4RAlsgAJ92SWz7zJGwtvibBWP9WE22FFaLHgCfZph8
69r7/DUFO9N/c+xXSC5Oy9M=
=NlKM
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2003-07-14  6:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11  6:37 Xavier Maillard
2003-07-13 10:56 ` Malcolm Purvis
2003-07-13 12:03 ` Matthias Andree
2003-07-13 17:57 ` Jochen Küpper
2003-07-18 23:37   ` Kirk Strauser
2003-07-13 20:41 ` Karl Pflästerer
2003-07-13 21:37 ` Chris Halverson
2003-07-14  6:34 ` Steve Evans [this message]
2003-07-14 22:08   ` Johan Bockgård
2003-07-14  7:20 ` Kai Großjohann
2003-07-14  8:04 ` Nicolas Kowalski
2003-07-14 18:23 ` Mikael Cardell
2003-07-14 21:20 ` Danny Siu
2003-07-14 22:21 ` Henrik Enberg
2003-07-15 22:32   ` Scott Kullberg
2003-07-14 23:17 ` Jesper Harder
2003-07-14 22:51   ` Xavier Maillard
2003-07-15  7:42     ` Jochen Küpper
2003-07-15  8:02     ` Kai Großjohann
2003-07-16  9:09       ` Jochen Küpper
2003-07-15 12:08 ` Wes Hardaker
2003-07-19  0:10 ` Mats Lidell

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=m3brvxobu8.fsf@kosh.local \
    --to=stevee@gorbag.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).