OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: [Q] Making postfix work with majordomo2
From: Sudhakar Chandrasekharan (thathsnetscape.com)
Date: Thu Feb 24 2000 - 18:41:37 CST


Hi,

I am in the process of hacking the perl code in majordomo 2.0 (in alpha at
this stage) in order to make it work fully with postfix. Majordomo2, for
those who don't know, is a ground-up rewrite of majordomo (the currently
widely used majordomor 1.9X has a very restrictive license. It also has
lots of legacy code) that is distributed under an apache-like license.

The process of building and installing majordomo2 (henceforth to be
referred to as mj2) has the following steps:

1. Search for pre-installed perl modules that are needed.
2. Ask a bunch of questions about environment including whether the user
wants majorodomo to work with virtual domains.
3. Ask the user whether the alias files should be handled automatically by
mj2.
4. Compile
5. Install binaries and supporting libraries.
6. If answered 'yes' for Q4 then add entries for majordomo2 in the aliases
file(s).
7. Whenever admin creates a new list entries for it need to be added in the
aliases file(s) if 'yes' for Q4.

The mj2 code interacts with postfix configuration in 2 places. During the
install stage (running as root) entries for majordomo2domain.one.org and
majordomo2domain.two.org need to get automatically created. I am planning
to do this through virtual_maps.

And after installation when the admin wants to create a new mailing list
(running as user majordom) entries for the newly created mailing list need
to get added to the aliases file. I am still undecided whether to do this
purely through aliases or through aliases + virtual_maps.

I have a bunch of questions:

1. Can postfix handle multiple virtual_maps files and alias_database
files? I'd ideally like to keep all the virtual_maps / aliases for each
virtual domain in a seperate file.

2. I am guessing that I need to use alias_database because some of the
aliases files are going to be owner + group majordom and not root.

3. How do I handle aliases of the same name in the two domains? Just like
I'd handle the two majordomo names - through the virtual maps?

Thanks.

Thaths

-- 
    "I have two questions for you: How much? and I'll take it."  
                     -- Homer J. Simpson
Sudhakar C13n http://people.netscape.com/thaths/ Lead Indentured Slave