>>>>> "OX" == Oliver Xymoron <email@example.com> writes:
OX> I have many private lists I'd like to search, in addition to the public
OX> ones. Therefore, access control has to be through Majordomo.
Well, you could export the per-user passwords to your web server's access
file format and protect the pages that way.
Going through Mj2 for every access is going to be pretty slow because of
the Perl startup time.
OX> Not quite generic enough to be pluggable,
The intention wasn't really for it to be generic, only to solve the basic
needs I had. Nobody else had any ideas when I was writing it, so...
The archiving thing doesn't really have to stay where it is now, as long as
I can still extract messages by number from it I don't really care what
happens to it. There's an object interface for all of it anyway, so it
really is pluggable as long as any replacement keeps the same interface
(which currently just involves adding and retrieving by number).
OX> What I'd like is:
OX> indexmsg mbox-file byte-offset length
Let's concentrate on the data you need and not the format of the commands.
I really can't tell what this is supposed to do. I figure you're trying to
find the message number from an offset, but I don't understand the length
OX> mjshell getmessage list-name msg-number
mj_shell archive-get-immediate list message
-immediate sends things to standard out; if you leave it off the message
gets mailed to you.