Hi,
I have some problems virtualizing Majorcool for automatic creation/deletion/
renaming of Majordomo lists.
There is, of course, no difficulty in virtualising both Majorcool and
Majordomo, but when it comes to external list creation programs to manage
entries within flat file mail aliases or ldap mail aliases, there is lack
of information about the domainname of the list under construction.
Take list_create_cmd, for example. Majorcool provides options "initial
password", "owner", "description" and parameter "list" to the external
command - where "list" is not allowed to carry a "@domain" with it.
Even with a virtualised "majorcool_<customer>.cf, there is no chance to let
list_create_cmd guess the customer domain for proper manipulation of ldap/flat
mail aliases:
<snip>--<majorcool.pl>--<snip>
if (-f "$list_create_cmd" && -x "$list_create_cmd" && open(REQ,
"$list_create_cmd -d '$desc' -o '$owner' -p '$passwd' $list 2>&1|")) {
<snip>--<majorcool.pl>--<snip>
- no way to include a "hidden" -c <my-virtualised-customer-domain>, because
"-x $list_create_cmd" will consequently fail.
My question therefore: did I miss some way to fool my list_create_cmd into
guessing the correct domain name? Or should I patch the above mentioned
part of Majorcool to be able to include a
list_create_cmd = my_list_create_cmd -c <customer domain>
within the virtualised majordomo-<customer>.cf?
Regards,
Birger
--
Birger Tödtmann. Bielefeld, Germany.
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | \dc
00 83 E2 57 EC 60 0B 1C D3 18 AE 2A 40 55 81 22
Follow-Ups:
|
|
