AW: AW: [Mailman-Users] Unable to get Mailman up and running withqmail/vpopmail

[DIGITAL FOR YOU - Alexander Schwethelm]

Thanks for your very detailed mail.  It made everything very clear.  Mailman
is still not running, but I have some more details:

I did a "su mailman" and ran check_perms and indeed I do get an error
message.  I ran check_perms -f before as root, reporting "no problems".

	kundenserver:/var/mailman # ./bin/check_perms
	No problems found
	kundenserver:/var/mailman # su mailman
	mailman at kundenserver:~> ./bin/check_perms
	Traceback (most recent call last):
	  File "./bin/check_perms", line 364, in ?
	    checkarchivedbs()
	  File "./bin/check_perms", line 226, in checkarchivedbs
	    for dir in os.listdir(mm_cfg.PRIVATE_ARCHIVE_FILE_DIR):
	OSError: [Errno 13] Permission denied:
'/var/mailman/archives/private'
	mailman at kundenserver:~>

I created a -qmail-default in /var/mailman with the following content
"|/var/qmail/bin/preline /usr/bin/python /var/mailman/qmail-to-mailman.py".
Mails sent to the list stay in the qmail queue forever, so this doesn't work
for some reason.  In the "qmail-to-mailman.py" I added at the top of the
file the two configuration variables:

	MailmanHome = "/var/mailman"; 
	MailmanOwner = "postmaster at hockey.wthc.net";

I also did the following:

	Next, look for the line that looks like local =
re.sub("^mailman-","",local). Change it to read: "local =
re.sub("^hockey.wthc.net-","",local)"

While playing around I added -qmail-herren ("herren" is the name of my list)
with the following content: ""|/var/mailman/mail/mailman post herren", but
no success either.  I'll provide you with the exact procedure I followed in
order to install mailman now.  The only difference is that I did a "chown -R
mailman ." in "/var/mailman" while playing around, besides that this is 1:1
what I have.

Best regards, Alex

PS:  Below you'll see my installation process.  My domain is called
hockey.wthc.net, the list I am plaing around with "herren".  The mails
staying in the queue have "mailman-herren at hockey.wthc.net" as the recipient
when sending mails to "herren at hockey.wthc.net".

	useradd -d /var/mailman mailman
	groupadd mailman
	mkdir /var/mailman
	chgrp mailman /var/mailman
	chmod a+rx,g+ws /var/mailman

	cd /usr/local/src/mailman
	tar zxvpf mailman-2.1.5.tgz
	cd mailman-2.1.5

	./configure --prefix=/var/mailman \
	            --with-mail-gid=mailman \
	            --with-cgi-gid=nobody \
	            --with-cgi-ext=.cgi \
	            --with-python=/usr/bin/python

	make install
	cd /var/mailman 
	./bin/check_perms
	./bin/check_perms -f
	./bin/check_perms

	Edit /var/mailman/Mailman/mm_cfg.py. Add the following lines to the
end of the file:
	DEFAULT_EMAIL_HOST = 'hockey.wthc.net'
	DEFAULT_URL_HOST = 'hockey.wthc.net'
	add_virtualhost('hockey.wthc.net', 'hockey.wthc.net')
	ALLOW_SITE_ADMIN_COOKIES = 1

	Set a password for list creation:
	cd /var/mailman
	./bin/mmsitepass

	From the Mailman source directory, copy the qmail-to-mailman.py
script into the mailman directory:
	cp /usr/local/src/mailman/mailman-2.1.5/contrib/qmail-to-mailman.py
/var/mailman
	chown mailman.mailman /var/mailman/qmail-to-mailman.py
	chmod a+rx /var/mailman/qmail-to-mailman.py

	Edit qmail-to-mailman.py. At the top of the file, edit the two
configuration variables:
	MailmanHome = "/var/mailman"; 
	MailmanOwner = "postmaster at hockey.wthc.net";

	Next, look for the line that looks like local =
re.sub("^mailman-","",local). Change it to read: 
	local = re.sub("^hockey.wthc.net-","",local)

	cd /var/mailman
	./bin/newlist mailman
	./bin/config_list -i data/sitelist.cfg mailman
	/var/mailman/bin/mailmanctl start

	Put in links so that the daemons will be started when the system is
booted up:
	cp /var/mailman/scripts/mailman /etc/init.d/mailman
	ln -sf /etc/init.d/mailman /etc/init.d/rc3.d/S97mailman
	ln -sf /etc/init.d/mailman /etc/init.d/rc2.d/K97mailman

	And lastly, set up cron jobs for Mailman maintenance: 
	crontab /var/mailman/cron/crontab.in -u mailman

	Qmail Configuration
	cd /var/mailman
	touch .qmail-default

	Add to .qmail-default:
	|/var/qmail/bin/preline /usr/bin/python
/var/mailman/qmail-to-mailman.py


	I've added hockey.wthc.net:mailman to
/var/qmail/control/virtualdomains

	After all this I restarted qmail and qrunner...



-----Ursprüngliche Nachricht-----
Von: Tierra [mailto:etierra at gmail.com]
Gesendet: Mittwoch, 24. November 2004 02:03
An: DIGITAL FOR YOU - Alexander Schwethelm
Cc: Mark Sapiro; mailman-users at python.org
Betreff: Re: AW: [Mailman-Users] Unable to get Mailman up and running
withqmail/vpopmail


On Wed, 24 Nov 2004 01:38:07 +0100, DIGITAL FOR YOU - Alexander Schwethelm
<info at digital4u.de> wrote:
> 1. I re-configured mailman with "--with-mail-gid=vchkpw".  Here I am
> not sure what would be correct and how this influences the
> installation/system. So what should I use there mailman or vchkpw???

Your actually going to want "--with-mail-gid=mailman" with your setup. None
of the mailman stuff goes through vpopmail. You don't even need to setup a
domain with vadddomain, so you'll probably want to vdeldomain. When you put
"list.mydomain.tld:mailman" in virtualdomains file in qmail, your telling
qmail to send all mail that goes to that domain to the local user "mailman",
unlike your other vpopmail domains which should look like
"virtual.com:virtual.com" - meaning send to vpopmail to handle. So vpopmail
has nothing to do with mailman/qmail. So the reason your going to want to
configure with the mailman gid is so mailman has access to the mail being
delivered to the mailman user instead of if you were handling lists on
virtual domains setup in vpopmail (which is a pain with qmail), where you
would need to configure with vpopmail actually, not vchkpwd (I think
anyway). This is the reason setting up with lists.mydomain.tld instead of
just mydomain.tld is so much easier.

> 2. I know created a "/home/vpopmail/domains/mailman" for my .qmail
> files. Before I either created
> /home/vpopmail/domains/mylist.domain.tld or droped a .qmail file
> directly into /var/mailman.  What is correct here?

Again, get rid of all entries of lists.mydomain.tld in vpopmail, you won't
need them. You will need the .qmail-default file in the mailman user's home
directory (which like I mentioned before might be elsewhere from
/home/mailman).

> 3. Putting "|/usr/bin/python /var/mailman/qmail-to-mailman.py" in
> either ".qmail-default" or ".qmail-mylist" doesn't work.  What works
> is putting "|/var/mailman/mail/mailman post mylist" into
> .qmail-mylist, but it would be impossible to add for each list all
> those aliases.  What am I doing wrong? Is there maybe something wrong
> with my "qmail-to-mailman.py"-file?

There's two ways to doing this. The first is using the script provided
inline with the README.QMAIL file to generate those .qmail-mylist-* files,
and doing that for EVERY list. The second, is creating a .qmail-default file
that has runs the qmail-to-mailman.py script which parses everything and
sends it where it needs to go. It also handles any new lists you create as
well. That's the reason it's the highly suggested route.

It sounds like you either have the wrong path to the qmail-to-mailman
script, or the permissions are messed up (check my first note). Another
thing you need to check is "su mailman" and run bin/check_perms script to
make sure mailman has all the access it needs.

> 4. Also, but not as important, I am already wondering why there is
> always a text file attached to each message  (something like
> ATT00111.txt). This file contains the listname, lists email address
> and the web link.  Why is that?

Umm, other people know more about that than I do on the list, I'll let
someone else answer that.

Bryan Petty

P.S. Can you use the "Reply-To-All" feature of your mail client so
everything stays in the same thread?