--
Hi. I'm still trying to get over to 1.94.1 (just in time to re-upgrade to
1.94.2!), and I can't figure out why this is happening:
>>>
MAJORDOMO WARNING (mj_resend)!!
resend: $admin_headers not defined in
/majordomo/majordomo-1.94.1/majordomo.cf !!
Majordomo will only catch "subscribe" and "unsubscribe" in
the subject field...
<<<<
Yet when I do this:
$ grep admin_headers /majordomo/majordomo-1.94.1/majordomo.cf
I get:
$admin_headers = <<'END';
In fact, here's what I have in majordomo.cf:
# Administrative checks. These used to be buried in the resend code
#
$admin_headers = <<'END';
/^subject:\s*subscribe\b/i
/^subject:\s*unsubscribe\b/i
/^subject:\s*uns\w*b/i
/^subject:\s*.*un-sub/i
/^subject:\s*help\b/i
/^subject:\s.*\bchange\b.*\baddress\b/i
/^subject:\s*request\b(.*\b)?addition\b/i
END
I looked through the resend code, and I would think that if it couldn't read
majordomo.cf, it would complain here:
if (! -r $cf) {
die("$cf not readable; stopped");
}
So the 'require "$cf";' on the next line should work, no? And if MD can
require majordomo.cf, it should get $admin_headers! I don't get any hints
that MD can't find majordomo.cf: wrapper config-test works just fine,
majordomo.cf is world-readable, etc. I only get complaints about
$admin_headers and $admin_body from resend when sending a message to my test
list, presumably from this section:
if (! defined($admin_headers)) {
&bitch("resend: \$admin_headers not defined in $cf !!\n" .
"Majordomo will only catch \"subscribe\" and \"unsubscribe\" in\n" .
"the subject field...\n");
I'm running PERL 5.003 here (with EMBED, whatever that means.) and
everything else seems to work -- the message does get delivered to the list.
Thanks,
Bonnie Scott
Prodigy Services Corp.
|
|