[lug] Config help needed with mailman and qmail

[Michael Deck]

Sean, thanks. I tried that solution and it probably would have worked
but I decided to upgrade to mailman 2.1 instead -- it seems to have good
support for virtual domains. 

The thing that was hanging me up was that I was trying to have different
kinds of domains on this system, some virtual and some not. From what
I've been able to puzzle out, email to the virtual domain is handled by
a vpopmail program running as GID=vchkpw whereas email to the real
domain is handled by qmail running as GID=nofiles. AFAIK this is an
intolerable situation for mailman -- no matter how you configure it, one
of those is going to be wrong. (Correct me please if I'm wrong about
this). Anyhow, I decided I didn't need the real domain name to be real,
so I made it go virtual and moved all my lists to the virtual space.
Then I rebuilt mailman with GID-vchkpw and it has been working fine. 

I wasn't sure if the lists.cleansoft.net approach would have had the
same problem -- it seemed like it would. 

-Mike

On Mon, 2003-08-11 at 14:26, Sean Reifschneider wrote:
> On Fri, Aug 08, 2003 at 03:26:02PM -0600, Michael Deck wrote:
> >I've been running qmail and mailman happily for a while but now I'm
> >trying to add some virtual domains in addition to a "real" domain on
> 
> You probably want to set up your lists under the "lists" domain name
> ("lists.cleansoft.net") and/or forwarding the mail for the lists aliases
> to "mailman-<whatever>@<hostname-in-locals>".  That way the messages for
> the list addresses go to the mailman user.  The nice thing about the
> lists.* address is that you can just set up a virtualdomains entry that
> forwards them to the mailman user.  That way you don't have to do
> anything to set up aliases for new lists and the like.
> 
> You *HAVE* read the "README.QMAIL" file included with Mailman, right?
> The last set of patches I submitted for it I believe made it fairly
> clear how to set things up to work nicely with qmail.  If there are any
> issues there or things you don't understand about it, let me know and
> I'll see about getting the readme changed.
> 
> Sean