>>>>> "BLH" == Brian L Heess <firstname.lastname@example.org> writes:
BLH> A funny spelling error right ^^^^^^^ there. :)
No, that's new Majordomo terminology. Varlabie, yeah. NOT.
BLH> What do I point the alias for majordomo to now...I have been
BLH> experimenting and have not figured it out yet.
Oops. I had aliases in there, but took them out when I put in createlist
(which can generate aliases for the GLOBAL list, which would point to
mj_email). Here's what I use:
mj2: "|/home/tibbs/mj/2.0-snap/bin/mj_email -v1000 -d hpc.uh.edu"
You need -d to specify the domain; there is no default. -v specifies a
debug level (-d was taken, and we have to use lowercase). The output will
go to stdout if it's a terminal (so mail -v will show it to you) or to a
debug file in tempdir.
This gets you to the email interface, which works mostly like the shell
interface. It has one special feature: if you put DEBUG 1000 in the
subject, it will attach the debug information as a MIME part in the mail
that comes back to you.
Note that there isn't anything you can do from the email interface that you
can't do from the shell interface (unless you don't have configedit, in
which case you can't yet deal with multiline config options).
I have had a report that the email interface doesn't return anything but
empty messages. I know it works for me and a few other folks, so I don't
know what the problem could be. If anyone sees this, use -v and send me
the debug output.
BLH> Anyway, there is no Mj::Config man page built.
Not sure why; perhaps because I forgot the SYNOPSIS section. In any case,
you can always use pod2man or pod2text on the source file.