Re: [gnu.emacs.gnus] Setting up an nndir version of a mailing list or newsgroup?

[Jason L Tibbitts III <tibbs@hpc.uh.edu>]

>>>>> "JD" == Joev Dubach <dubach1@husc.harvard.edu> writes:

JD> Um, I mean, from an administrative standpoint: how do I shove the
JD> mailing list into that /that/directory/where/it/wants/to/reside/?  With
JD> the .overview being set up properly?  On a reasonably continuous
JD> schedule?

Well, I'm the one that keeps ding-list and ding-list-recent.  Everything is
done with Procmail and and old hack that was used before (ding) could
handle Procmail spools.  Use this at your own risk, and don't use it on
modifiable groups, where Gnus will ever delete anything or touch the
.overview file.

Here is the Procmail rule for ding-list and ding-list-recent:

UMASK=022

:0
*^TOding@ifi.uio.no
{
        :0 c
        ding-list/. ding-list-recent/.

        :0 hw :ding.lock
        | ( /home/tibbs/bin/add-active-nov $LASTFOLDER; \
            /usr/local/bin/tail -500 ding-list/.overview > ding-list-recent/.overview ; \
            rm -f blurgh `ls -1t ding-list-recent/* | sed -e 1,500d` )
}


Here's add-active-nov:

#!/usr/local/bin/perl

($dir=$ARGV[0]) =~ s#/[0-9]+$##;
($num=$ARGV[0]) =~ s#.*/([0-9]+)$#$1#;
($group=$dir)   =~ s#/#\.#g;

$lines      = 0;
$chars      = (stat($ARGV[0]))[7];
$references = "";

open (HEADERS, "formail -c -a Subject: -X subject: -a From: -X from: -a Date: -X date: -a Message-ID: -X message-id: -X in-reply-to: -X references: -X lines: -X content-length: < $ARGV[0] |") || "Could not open formail";
while(<HEADERS>)
{
  chop;
  if (s/^from:[ \t]*//i) {
      $from = $_;
    }
  elsif (s/^subject:[ \t]*//i) {
    $subject = $_;
  }
  elsif (s/^date:[ \t]*//i) {
    $date = $_;
  }
  elsif (s/^message-id:[ \t]*//i) {
    $id = $_;
  }
  elsif (s/^references:[ \t]*//i) {
    s/.*\t([^\t]+)/\1/;
    $references = $_;
  }
  elsif (s/^in-reply-to:[ \t]*//i) {
    s/.*\t([^\t]+)/\1/;
    if (   $references eq "" && $_ =~ /(<[^>]+>)/) {
      $references = $1;
    }
  }
  elsif (s/^lines:[ \t]*//i) {
    $lines = $_;
  }
  elsif (s/^content-length:[ \t]*//i) {
    $chars = $_;
  }
  else {
    die "Unknown field: $_";
  }
}

close (HEADERS);

if (-f "$dir/.overview") {
  $nov = "$dir/.overview";
} elsif (-f "$dir/.nov") {
  $nov = "$dir/.nov";
} else {
  $nov = "$dir/.overview";
}

system("lockfile -! $nov.lock") || die "Could not get lock";

open (NOV, ">>$nov") || die "Could not open $nov";
printf NOV ("$num\t$subject\t$from\t$date\t$id\t$references\t$chars\t$lines\t\n");
close (NOV);

system("rm -f $nov.lock");

$act = "$ENV{'HOME'}/Mail/active";
$actold = $act . ".old";

system("lockfile -! $act.lock") || die "Could not get lock";

rename($act,$actold) || die "rename $act $!";

open(ACTIVE, "$actold") || die "Could not open $actold";
open(NEW_ACTIVE, ">$act") || die "Could not open $act";

while (<ACTIVE>) {
  s/^$group [0-9]+/$group $num/;
  print NEW_ACTIVE;
}

close ACTIVE;
close NEW_ACTIVE;
system("rm -f $act.lock");


JD> I'd think people would have a bunch of scripts for this, seeing as
JD> there are actual mailing lists (ding-list, ding-list-recent at least)
JD> that get filtered into nndir-friendly directories.

Well, not a bunch, but the above gross hacks have fed over 11000 articles
into those two groups with zero barfs so far.  I just noticed that it will
miss BCCd articles, but a match on envelope sender should fix that.

 - J<