Gnus development mailing list
 help / color / mirror / Atom feed
From: Joe Hildebrand <hildjj@fuentez.com>
Cc: hildjj@fuentez.com
Subject: Re: Gnus5, procmail, and reading mail lists.
Date: 17 Nov 1995 14:40:41 -0700	[thread overview]
Message-ID: <yyapweqdina.fsf@arls2006.fuentez.com> (raw)
In-Reply-To: tibbs@sina.hpc.uh.edu's message of Fri, 17 Nov 1995 15:18:43 -0600

> "Jason" == Jason L Tibbitts <tibbs@sina.hpc.uh.edu> writes:


   Jason> As you see, I really need Procmail to keep the recent list,
   Jason> and I need the .overview file to be up to date while I'm
   Jason> splitting.  Of course, if anyone has any better ways of
   Jason> doing this, I'm all ears.  I know this works without
   Jason> problems.

   Joe> I'm interested in getting everyone cut over to the Gnus way.

I guess I'm worried that people are going to lose mail, and blame me,
since my name is on the script.  Even though it's not my fault Gnus
can't do locking :)

   Jason> I wonder if I can keep doing the archives my while doing
   Jason> everything else the proper way without any conflicts.

No problem.  Keep your archive delivery script.  Add one more branch
at the top of the {} block:


:0: ding.lock
*^TOding@ifi.uio.no
{
      :0c:
      ding.spool

      # turn add-active-nov on, from here to the end of this block.
      # since the block starts a sub-shell, this shouldn't propagate
      # out of the block.
      TRAP=add-active-nov

      ...
}

Remove the TRAP from the beginning of your .procmailrc, 
then see <URL:http://www.fuentez.com/public-info/ding/> for
instructions on how to set up ding to slurp your .spool files.

-- 
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


  reply	other threads:[~1995-11-17 21:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-11-14  1:43 Steven L. Baur
1995-11-14 13:04 ` Per Abrahamsen
1995-11-15  2:42   ` Steven L. Baur
1995-11-14 16:27 ` Joe Hildebrand
1995-11-14 17:22   ` Scott Blachowicz
1995-11-14 21:35     ` Joe Hildebrand
1995-11-15  6:58     ` Sudish Joseph
1995-11-15 18:46       ` Scott Blachowicz
1995-11-15  4:37   ` Sudish Joseph
1995-11-15 14:32     ` Per Abrahamsen
1995-11-15 15:50       ` Kai Grossjohann
1995-11-15 16:13         ` Per Abrahamsen
1995-11-15 17:50         ` Steven L. Baur
1995-11-17 21:18   ` Jason L Tibbitts III
1995-11-17 21:40     ` Joe Hildebrand [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-11-14  1:55 Steven L. Baur
1995-11-13 22:21 Steven L. Baur
1995-11-13 20:33 Steven L. Baur
1995-11-13 22:43 ` Joe Hildebrand
1995-11-14 19:52   ` Edward J. Sabol
1995-11-13 17:48 Mark Borges
1995-11-13 20:16 ` Joe Hildebrand
1995-11-14  0:24   ` Mark Borges
1995-11-15  6:19 ` Mark Borges
1995-11-15  8:17   ` Steven L. Baur

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=yyapweqdina.fsf@arls2006.fuentez.com \
    --to=hildjj@fuentez.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).