Tom Limoncelli wrote:
> Well, I've added "sendme" capability to my majordomo. Basically, you
Ah! I was just about to do this! Thanks for saving me the effort!
> As I'm posting this, I just realized that this could become a
> generalized archiving system with some additional support. When
> an archive grows to a certain size or age, the file could be moved
> into this directory as "archive.$listname.$date" and a description
> could be appended to the "index" file. Well, it's just a thought.
> (I guess .private lists would need some kind of security mechanism)
I've done just this. I have a program called mlarchive. It manages
archives in a directory specified by $arcdir in majordomo.cf. For each
list there are three files: listname, which contains the current archive
issue, listname.issue, which specifies the issue number currently being
archived (defaults to 1 if missing, and will be created automaticly as 2
when the issue closes), and listname.ctl, which looks like:
$arcsize = 524288; # issue size (a minimum, not a maximum)
$arcowner = "tsarna"; # who to notify when issues close
$arcdest = "/home/ftp/pub/archive"; # where to put closed issues
$arcext = ".lha"; # compressor extension
$arccmd = "/usr/local/bin/lha a %A %F >/dev/null"; # compressor command
For more common usage, the latter two could be:
$arcext = ".Z";
$arccmd = "compress %F >/dev/null";
$arcext = ".gz";
$arccmd = "gzip %F >/dev/null";
Here's how I use mlarchive in my aliases file:
"|/home/listserv/majordomo/wrapper mlarchive test"
I could easily clean up the code and whip up a distribution if folks are
interested. This along with Tom's sendme would be a great addition to
Majordomo, especially for people managing lists where many subscribers
don't have access to FTP.
I'd like to add one more .ctl option, a command to be run when an issue
closes. This would provide the neccesary hook for updating the index
> [sendme code deleted]
Hmmm, it just sends it as straight text, doesn't it? I'd like to be able
to send binary files, with uuencoding & splitting (or even better,
optionally send it as MIME).
Ty Sarna "Sure I'm shallow and you're deep, but aren't
firstname.lastname@example.org those just different ends of the same pool?"