On Fri, Jan 05, 2001 at 05:22:40PM -0600, Michael Orion Jackson wrote:
| I don't know about procmail
If Maildir format is what mh uses, then procmail can do it no problem
and always could. Just save your article to `directory/.' It's in
the procmailrc man page, search for `mh'
[ Ahh, I see I should have read this before suggesting procmail in my
earlier reply to a later thread ... ]
| but if you dig perl, the perl module
| and general way-better-than-procmail replacement Mail::Audit.pm handles
That's a matter of opinion, and I see that the Mail::Audit author
believes in it very strongly.
I can't argue with the statement `it has a tortuous and complicated
recipe format' ... but procmail has a lot going for it ...
1) it can do just about anything needed (as Mail::Audit probably can
too.)
2) it's light weight (loading up perl and then compiling a module and
your script, then handling the email is likely to use multiple
megabytes of memory and a cpu second or two.) It's not a big deal for
one or two emails, but when you get a flood of emails, it makes a big
difference. Especially on a slow box like piglet with lots of people
who may be doing exactly the same thing.
It's even lighter weight when procmail is being used as the local
mailer (which it often is, because it's very good at it.)
3) it's very simple and robust. There's only one executable,
very little to go wrong. On a machine like piglet, it's unlikely that
the admins will muck with procmail much, and if they *do* update it,
it'll probably work just like it did before.
With Mail::Audit, all they have to do is upgrade perl on you or
reinstall it, and suddenly *all* your mail is bouncing.
Also, one typo in your mail processing script, and all your mail
starts bouncing (because the perl script won't compile.) With procmail,
a typo in your ~/.procmailrc file might break that one rule, but
procmail will not start bouncing your mails unless everything else
goes wrong first.
| Maildir in addition to the more "normal" mailbox formats. I'm using it
| (Mail::Audit) right now with great success (~5 busy mailing lists, spam
| filters, etc).
Only 5? My .procmailrc has 169 rules handling at least 30 mailing
lists, many of which are very busy (siglinux isn't very busy. :)
It also has a scoring mechanism that assigns scores to emails based on
certain phrases and keywords that they contain, and if the score gets
too high, it gets saved away as probable spam.
Don't get me wrong -- I'm a perl bigot. But I'm just as big a
procmail bigot :)
--
Doug McLaren, [EMAIL PROTECTED]
That weasel stole my bee!
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
