On 9 Jun 1997, Jason L Tibbitts III wrote:
> BR> Jason, I'm wondering -- how is virtual majordomo going to work in 2.0?
>
> Well, that's just it, I don't use virtual stuff so I'm shooting for the
> "ideal implementation" as I see it. That means that virtual servers under
> Majordomo work like virtual web servers and virtual FTP servers: each
> virtual server is a completely disconnected set of functionality. When you
> send a lists request to majordomo@a.com, you get a.com's lists and not
> b.org's lists even if they're both running on the same server. But this
> probably requires MTA support. I don't know if sendmail can do that kind
> of thing; perhaps it can. Someone once told me that Exim's aliases file
> can do this:
>
> majordomo@a.com: /path/to/majordomo -d a.com
> majordomo@b.org: /path/to/majordomo -d b.org
>
> which really is the ideal way to support this.
The newer Sendmail's support this. I'm using an older version, so I use
procmail to filter mail to do this.
Where is the definition for each domain sitting in majordomo's eyes? You
shouldn't hard-code the directory structure. That was one of the problems
with earlier 1.9x and we overcame that in 1.94 and did away with all that.
And yes, this is the *ideal* way of doing it. :)
> BR> Also, please please please make sure than when you're coding things
> BR> that require config files, that the config file is not set to any one
> BR> directory (like where the software is) and that it's location is
> BR> configurable.
>
> Each "domain" (virtual server, whatever) has a completely separate set of
> config files, and a completely separate set of lists. The directory
> structure looks like this:
Wait, you'll allow each domain to exist in whatever directory structure we
want, no? Let's say I want a.com is exist in /majordomo/a.com and b.org to
exist in /usr/local/majordomo/b.org
If we're working off an httpd virtual server implementation as an example,
this is part of it. In my mind, this is an *essential* feature.
-------------------------------------------------------------------------
| Brock Rozen | brozen@webdreams.com | http://www.webdreams.com/~brozen |
-------------------------------------------------------------------------
Follow-Ups:
References:
|
|
