Re: Gnus5, procmail, and reading mail lists.

[Sudish Joseph <joseph@cis.ohio-state.edu>]

Joe Hildebrand writes:
>> "Steven" == Steven L Baur <steve@miranova.com> writes:
Steven> I just reread the thread, and saw again the comments about a
Steven> procmail NOV hack, which I assume add-active-nov is referring
Steven> to.
> Yes, it was a hack.  No, even I don't use it anymore.  The only place
> it was probably documented was on my web server.

I think it can also be accessed off Lars' page somewhere, too.

> If anyone is still using add-active-nov, could you please contact me?
> I'm interested in getting everyone cut over to the Gnus way.

This seems too strong to me.  Sure, supporting completely safe
external mail delivery from within ding is extremely hard to do.  But
"completely safe" here relates to getting things to work correctly if
you're delivering directly to groups that you might do a "B m" or 
"B c" into.  If you're willing to forgo that luxury, it's possible to
achieve safe external delivery.

I switched over to using .spool files 2-3 weeks back, primarily to see
if startup split time wouldn't be a significant factor.  I now find it
a pain to have to wait through all the "splitting" messages before I
can read mail.  YMMV, of course.

As for biffing externally delivered mail, I have a Tk-from-Perl5
script that will biff such messages properly.  (It's modeled on
XMultibiff and offers seperate header and message previews.)

I've been thinking about this stuff and discussed some approaches with
Lars (unsuccessfully :<).  I think I'll post a complete list of
pros/cons/methods on this topic separately.

-Sudish