I use a combination of sendmail's virtualusers table and alias file.
The virtualusers table makes list-request@domain.com map to list-request,
so you end up with local aliases. The alias file allows you to execute
programs.
Here's an example:
The virtualusers file:
owner-test@virt.domain.com jdoe@wherever.com
test-owner@virt.domain.com owner-test@virt.domain.com
test@virt.domain.com test
test-approval@virt.domain.com jdoe@wherever.com
test-outgoing@virt.domain.com test-outgoing
test-request@virt.domain.com test-request
The alias file:
test: "|/usr/local/server/majordomo/wrapper resend -l test -h virt.domain.com -C /usr/local/etc/majordomo/majordomo-virt.domain.com.cf test-outgoing,devnull"
test-outgoing: :include:/home/majordom/lists/test, "|/usr/local/server/majordomo/wrapper archive -a -m -f /home/majordom/archives/test/test"
test-request: "|/usr/local/server/majordomo/wrapper majordomo -l test -C /usr/local/etc/majordomo/majordomo-virt.domain.com.cf"
This presupposes that all listnames will be unique. Also not that we create
a separate majordomo.cf file for each virtual domain.
--
Omar
On Wed, Oct 27, 1999 at 12:55:04AM +1000, John Robens wrote:
> My problem is that I am trying to use procmail to parse the headers to
> work out what messages should be passed to the outgoing user.
>
> I can map the majordomo users using the virtualusers table in sendmail,
> but can it run the commands required to put a full majordomo configuration
> in there? Since it is a fixed dbm format I thought not to risk it. I
> wanted the mailing lists (there are lots) separated (secondary
> requirement) from the sendmail, as I am in the process of migrating them
> between hosts.
Follow-Ups:
References:
|
|
