Re: Gnus5, procmail, and reading mail lists.

[Joe Hildebrand <hildjj@fuentez.com>]

> "Steven" == Steven L Baur <steve@miranova.com> writes:

   Steven> LOCKEXT=+

   Steven> I thought movemail *did* use .lock for an extension.  At
   Steven> least that's what the XEmacs sources seem to imply.

I got that from somewhere.... anyone want to 'fess up?  I haven't lost
any mail (that I know of :) using either that or the default.  Maybe
I'll go have a look at the 19.29 movemail source.

   Steven> If you are going to use Gnus expiration, it is important to
   Steven> also set: (setq nnmail-keep-last-article t)

I thought this was only if procmail was delivering directly to the
nnm[lh] directory.

   Steven> If you are going to generate NOV databases out of procmail,
   Steven> you will have to deal with the same locking issues you face
   Steven> with the spool files, with the added nicety that while the
   Steven> NOV database is being updated Gnus must be locked out too.
   Steven> I don't think anybody is doing it this way.

Anymore.  Some people may still be using add-active-nov.

   mb> Finally, should I restrict myself to the Gnus5 expiry process,
   mb> or can I just run a simple cron job each weekend to remove old
   mb> mail? (I suspect that might confuse Gnus5 after a while,
   mb> though.)

   Steven> I had previously been using the pattern: ^TOding(-request)?
   Steven> This doesn't work 100% mainly due to messages being Cc:'ed
   Steven> to you and the mailing list.

procmailrc(5) says:
     If the regular expression contains `^TO' it will be  substi-
     tuted by `(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope
     |Apparently(-Resent)?)-To):(.*[^a-zA-Z])?)', which should
     catch all destination specifications.

which should catch CCs.

-- 
Joe Hildebrand                  Fuentez Systems Concepts
hildjj@fuentez.com              11781 Lee-Jackson Hwy, Suite 700
Lead Software Engineer          Fairfax, VA 22033
	"Breakfast recapitulates phylogeny" - Spider Robinson