Great Circle Associates Majordomo-Workers
(October 2000)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Some thoughts on qmail..
From: Jason L Tibbitts III <tibbs @ math . uh . edu>
Date: 22 Oct 2000 15:40:24 -0500
To: Stefan Morrell <stef @ mort . level5 . net>
Cc: majordomo-workers @ greatcircle . com, mj2-dev @ csf . colorado . edu
In-reply-to: Stefan Morrell's message of "Sun, 22 Oct 2000 18:06:10 +0100"
References: <20001022180610.H12680@mort.level5.net>
User-agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7

>>>>> "SM" == Stefan Morrell <stef@mort.level5.net> writes:

SM> The problem here is that having a .qmail-default file isn't enough.

That's odd.  The qmail support was contributed and has worked fine for
other folks for some time now.  Patches are of course welcome, but I don't
have the means to test them.

For the benefit of the folks on the mj2-dev list, where I'm CC'ing this,
I'll quote the rest of the message.

SM> In fact what is really needed is a .qmail file in ~alias for each and
SM> every address qmail creates, to pipe the mail back into mj_enqueue, as
SM> in the .qmail file created during install, or an entry in
SM> /var/qmail/users/assign (along with running qmail-newu to rebuild the
SM> cdb file and restarting the qmail queue daemons). I dunno how you might
SM> want to automate this, but it will need to likely run setuid root or
SM> possibly alias. Alternatively, the poor, long suffering sysadmin can
SM> create all the files by hand...

SM> Unless...

SM> The aforementioned sysadmin can create himself a subdomain specifically
SM> and only to handle mailing list traffic, in which case the whole thing
SM> becomes much simpler and more elegant. He simply adds MX records for
SM> the subdomain pointing at the canonical name of the qmail server and
SM> then adds a line into /var/qmail/control/virtualdomains of the form

SM> lists.mydomain.com:majordomo

SM> Which causes all email for lists.mydomain.com to be processed according
SM> to rules contained in .qmail files in majordomo's $HOME. Then he
SM> creates a .qmail-default file with the pipe to mj_enqueue so that all
SM> addresses on the lists subdomain are sent to the majordomo scripts,
SM> which then process the email as normal.

SM> My apologies if (as I suspect) I'm singing an old and weatherworn song,
SM> but the qmail documentation and configuration questions currently in
SM> the package aren't massively clear (so far at least), so I thought I'd
SM> throw my hat into the ring.

I have to say that this is the first time I've heard of problems like these
with qmail.  I do know that other qmail users have been able to use the
software without problems, so I suspect that there's something beyond my
understanding at work here.

 - J<



Follow-Ups:
Indexed By Date Previous: Re: X Loop trapping
From: David Miller <justdave@a2central.com>
Next: Re: Some thoughts on qmail..
From: John R Levine <johnl@iecc.com>
Indexed By Thread Previous: Re: Mj2: Re: X Loop trapping
From: SRE <eckert@climber.org>
Next: Re: Some thoughts on qmail..
From: John R Levine <johnl@iecc.com>

Google
 
Search Internet Search www.greatcircle.com