From owner-freebsd-isp Mon Apr 20 17:38:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08727 for freebsd-isp-outgoing; Mon, 20 Apr 1998 17:38:47 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from stingray.ivision.co.uk (stingray.ivision.co.uk [195.50.91.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA08600 for ; Tue, 21 Apr 1998 00:38:16 GMT (envelope-from manar@ivision.co.uk) Received: from pretender.ivision.co.uk [194.112.59.168] by stingray.ivision.co.uk with smtp (Exim 1.62 #2) id 0yRR4e-0002Vj-00; Tue, 21 Apr 1998 01:38:13 +0100 Message-Id: <3.0.5.32.19980421013705.00939ad0@stingray.ivision.co.uk> X-Sender: manarpop@stingray.ivision.co.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 21 Apr 1998 01:37:05 +0100 To: freebsd-isp@FreeBSD.ORG From: Manar Hussain Subject: Re: Multi-Domain mailing list software In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:51 20/04/98 -0700, perl wrote: >Hi, I was wondering what software people use for mailing lists which exist >on a few virtual domains. Is this something majordomo can do? A little while ago I mentioned how easy and clean it is to set up virtual domains in exim. We've got an extension of this that works with a slight re-work of the dir structure for majordomo that works well for us. Basically majordomo would get installed in somewhere like /usr/majordomo/ and this and some of the sub-dirs would contain the main code files anf a config file for that install of majordomo. A further set of sub-directories contain further list related info that would be added to as majordomo is used, e.g. a lists/ dir for the list config/info/subscriber/passwd files and a archive/ dir for the list archive. (the lists/ one is the only must have one). To support multiple domains you would really want to have multiple majordomo config files - the majordomo config file to use can be specified when you call majordomo. What we've done is move the config file and the "further set of sub-directories contain further list related info" to another directory tree, adding another layer to specify the domain. E.g. the majordomo config file, lists/, archive dir etc. for the domain wibble.com would be found in: /usr/majordomo-lists/wibble.com/ There is then I believe the one and only (and small) patch to majordomo code which allows it to find the right (default_ config file and the lists files for a given domain (basically we just insert /usr/majorcomo-lists/$domain at the start of the path). That in itself may be of some interest/use - what we've also done is extend the way we do virtual domains in exim with another 10 or less lines which gets exim to look at a text file that lists all the domains that support majordomo mailing lists and for the file: /usr/majordomo-lists/wibble.com/aliases/aliases to be considered an additional aliases file for such domains. (Because it gets handled by a different delivery config area in exim you could also configure other things that make the MTA treat handling list mail differently from other mail - e.g. what user delivery is conducted as). There's not really much code change to do this - it's more an idea of how you might like to do things - but if anyone is interested I can pass on the simple details on how to set it up with exim at least. BTW - I'll probably send a copy of this to majordomo-users or majoromo-workers @greatcircle.com - probably a more appropriate forum for majordomo queries. Manar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message