Nick Jennings <[EMAIL PROTECTED]> wrote on Wed, 12 Jan 2000:
> Argh! I despise procmail, yes its powerfull, and can do alot, but
> it's severly anoying.
...
> yes procmail is powerfull, but its far too much of a
> hassle for just setting up a simple filter,
You could try maildrop instead, then. You might like that better than
procmail (or maybe not).
In any case I don't see what's so complex about essentially having the
following:
.forward:
|/usr/bin/procmail
.procmail:
### Mutt users list
:0
* ^Sender.*owner-mutt-users@mutt\.org
mutt-users-mail
Two files, and not very long or complex ones at that. The setup using
maildrop would be approximately the same I believe, if not even simpler.
> I think it _IS_ a mail clients job to do filtering,
> after all, it checks the /var/spool/mail/<username> for new mail and drops
> in in your inbox, if it drops it in the inbox, why not instead drop it in
> some other box and let you know?
A MUA reads mail folders (some of which might incoming mail folders, or
mail spool files). It doesn't transfer or move mail non-interactively,
it does so only under the user's direction. Or no?
Regardless, Mutt tries to follow the principle "use the right tool for
each job", instead of trying to cram every feature into itself, which
leads into large monolithic applications that are slow and bug-infested.
For incoming email filtering, the right way to do this is at the mail
delivery time with specilised mail filter applications, not when the
MUA starts.
Mikko
--
// Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/
// The Corrs list maintainer // net.freak // DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
I'm a shareware signature! Send $2 if you use me, $10 for a manual.
