Mailman

[timryberg]

A while ago Chris W and I had a discussion on the Sago forums about the possibility of running the Mailman mailing list server on an Interworx box. He indicated that he thought it would probably work. It doesn't.

I requested that Sago do this for me (installing from source because the RPM wants Postfix MTA and the newest version isn't of Mailman isn't available for RH9 in RPM format.

I would just like to let you know that this apparently does not work. One of their Senior Linux admin's has been working on it when he has time off and on for close to a month. He belives that the problem is with that vPOPMail and Mailman daemon are not communicating properly.

I just thought that I'd let you know (no, I'm not mad; just a little disapointed).

I am reiterating my previous request that future versions of Interworx support alternate MTA's -- specifically Postfix.

Thanks for reading

Tim

[IWorx-Paul]

Hi Tim,

I disagree that it isn't possible. That's not to say it isn't tricky though.
I have successfully installed mailman on a server running Qmail + Vpopmail, as InterWorx-CP does. That's NOT to say that I have installed mailman on an InterWorx-CP server. I haven't tried yet.

I can tell you, when I was successful, I did it using this recipe:
http://nav.bandersnatch.org/clues/qmail-vpopmail-mailman.html

You may be correct, perhaps all hope is lost. But I'm not convinced, at least not yet. I'm going to fiddle around with it and see if I can come up with an InterWorx-CP specific recipe to get this working.

Stay tuned...

Paul

[timryberg]

Thank you for your prompt and timely response to this. I will share this with Chris M at Sago and see if it helps him (most of it appears to be above my head).

I will let you know if it does.

Tim

[IWorx-Paul]

I've written a bash script that will successfully get mailman installed on an InterWorx server.

DISCLAIMER: This is ONE way to do it. There may be other, better ways. This in no way implies that we provide support for mailman. There isn't even a guarantee that it will work if you use this script. You only get the "it worked for me" guarnatee. There is no offical support for this script. It is very possible that InterWorx-CP will offically support mailman in the future. There is no guarantee that it will be done the same way as it is done in this script.

This script assumes several things.
* You are comfortable running scripts in a linux environment

* You know how to edit and save text files in a linux environment

* You have root access to your server

* Using this script, you'll end up with a mailman installation available at http://lists.domain.com/mailman/admin

* The lists.domain.com name points to the same IP address as the parent "domain.com"

* It assumes there is a SiteWorx account created on the server that you want this mailman setup to be associated with.

* It assumes that the subdomain "lists.domain.com" is DNS'd and already working, where domain.com is actually the main SiteWorx account domain. The script won't complete unless it can resolve lists.domain.com

For example, if the main domain on your SiteWorx account was "yourdomain.com", the first step is to get lists.yourdomain.com DNS'd and resolving. You could add this as a subdomain in SiteWorx, or add a CNAME record under DNS Management in NodeWorx. Then you must wait until the name lists.yourdomain.com is resolving to the IP address.

Then, log into your server as root, and

1) Get the script:
wget http://updates.interworx.info/scripts/mailman.sh
2) Run the script:
sh mailman.sh yourdomain.com

The script will complain if it can't resolve lists.domain.com, and quit. Otherwise it will occasionally print out notices and ask you to enter things like password settings, etc.

Follow all instructions the script gives you, and you should be able to create mailman lists for the domain "lists.yourdomain.com".

Paul

[timryberg]

Thanks Paul, I will pass this on to Chris M.

[timryberg]

I've used this script to install mailman on the domain transwarplists.net

When I visit http://www.transwarplists.net

I get the standard Apache server root page (not the SiteWorx start page, even though I hace verified that I hacve index.html 1.gif 2.gif. 3.gif in their usueal places.

When I load lists.transwarplists.net I get the following:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>403 Forbidden</title>
</head><body>
<h1>Forbidden</h1>
<p>You don't have permission to access /
on this server.</p>
<p>Additionally, a 404 Not Found
error was encountered while trying to use an ErrorDocument to handle the request.</p>
<hr />
<address>Apache/2.0.40 Server at lists.transwarplists.net Port 80</address>
</body></html>

When I load lists.transwarplists.net/mailman I get

Access forbidden!

You don't have permission to access the requested directory. There is either no index document or the directory is read-protected.

If you think this is a server error, please contact the webmaster

Error 403

www.transwarplists.net
Thu 17 Jun 2004 11:00:34 PM EDT
Apache/2.0.40 (Red Hat Linux)


When I load lists.transwarplists.net/mailman/admin I get:

Server error!

The server encountered an internal error and was unable to complete your request.

Error message:
Premature end of script headers: admin

If you think this is a server error, please contact the webmaster

Error 500

www.transwarplists.net
Thu 17 Jun 2004 11:01:56 PM EDT
Apache/2.0.40 (Red Hat Linux)

Any idea what I've done wrong?

Here is my transwarplists.net.conf file

<VirtualHost 65.110.52.171:80>

SuexecUserGroup transwa2 transwa2

DocumentRoot /home/transwa2/transwarplists.net/html
ServerName lists.transwarplists.net

ServerAlias ftp.transwarplists.net lists.transwarplists.net www.transwarplists.net
ServerAdmin webmaster@transwarplists.net
DocumentRoot /home/mailman/transwarplists.net
Alias /pipermail/ /home/mailman/transwarplists.net/archives/public/
ScriptAlias /mailman/ /home/mailman/transwarplists.net/cgi-bin/
ErrorLog /home/mailman/transwarplists.net/logs/error_log

# subdomain logic
RewriteEngine On
RewriteOptions inherit
RewriteCond %{HTTP_HOST} !^www\.transwarplists\.net [NC]
RewriteCond %{HTTP_HOST} !^transwarplists\.net [NC]
RewriteCond %{HTTP_HOST} ^([A-Z0-9a-z-]+)\.transwarplists\.net [NC]
RewriteCond %{DOCUMENT_ROOT}/%1 -d
RewriteRule ^(.+) %{HTTP_HOST}/$1 [C]
RewriteRule ^([0-9A-Za-z-]+)\.transwarplists\.net/?(.*)$ %{DOCUMENT_ROOT}/$1/$2 [L]
# end subdomain logic

ErrorLog /home/transwa2/var/transwarplists.net/logs/error.log
CustomLog /home/transwa2/var/transwarplists.net/logs/transfer.log combined

php_admin_flag engine On

# cgi: 1
<Directory /home/transwa2/transwarplists.net/html>
AllowOverride AuthConfig FileInfo Options Limit Indexes
</Directory>

ScriptAlias /cgi-bin/ /home/transwa2/transwarplists.net/html/cgi-bin/

</VirtualHost>


YES, I restarted httpd

Tim

[IWorx-Paul]

It looks to me like there was some confusion with the very last step.


<VirtualHost 65.110.52.171:80>
ServerName lists.transwarplists.net

ServerAdmin postmaster
DocumentRoot /home/mailman/transwarplists.net
Alias /pipermail/ /home/mailman/transwarplists.net/archives/public/
ScriptAlias /mailman/ /home/mailman/transwarplists.net/cgi-bin/
ErrorLog /home/mailman/transwarplists.net/logs/error_log
</VirtualHost>

This whole block needs to be on it's own ABOVE the large virtualhost block, and not munged together into the one big vhost, like it is in your example.

So the file should look something like:

<VirtualHost 65.110.52.171:80>

ServerName lists.transwarplists.net

ServerAdmin postmaster
DocumentRoot /home/mailman/transwarplists.net
Alias /pipermail/ /home/mailman/transwarplists.net/archives/public/
ScriptAlias /mailman/ /home/mailman/transwarplists.net/cgi-bin/
ErrorLog /home/mailman/transwarplists.net/logs/error_log

</VirtualHost>

<VirtualHost 65.110.52.171:80>

SuexecUserGroup transwa2 transwa2

DocumentRoot /home/transwa2/transwarplists.net/html
ServerName transwarplists.net

ServerAlias ftp.transwarplists.net transwarplists.net www.transwarplists.net
ServerAdmin webmaster@transwarplists.net

# subdomain logic
RewriteEngine On
RewriteOptions inherit
RewriteCond %{HTTP_HOST} !^www\.transwarplists\.net [NC]
RewriteCond %{HTTP_HOST} !^transwarplists\.net [NC]
RewriteCond %{HTTP_HOST} ^([A-Z0-9a-z-]+)\.transwarplists\.net [NC]
RewriteCond %{DOCUMENT_ROOT}/%1 -d
RewriteRule ^(.+) %{HTTP_HOST}/$1 [C]
RewriteRule ^([0-9A-Za-z-]+)\.transwarplists\.net/?(.*)$ %{DOCUMENT_ROOT}/$1/$2 [L]
# end subdomain logic

ErrorLog /home/transwa2/var/transwarplists.net/logs/error.log
CustomLog /home/transwa2/var/transwarplists.net/logs/transfer.log combined

php_admin_flag engine On

# cgi: 1
<Directory /home/transwa2/transwarplists.net/html>
AllowOverride AuthConfig FileInfo Options Limit Indexes
</Directory>

ScriptAlias /cgi-bin/ /home/transwa2/transwarplists.net/html/cgi-bin/

</VirtualHost>

[timryberg]

Thanks, Paul.

I replaced my existing file witht he one you pasted above and things seemed to be working until I tried to fill out the form at:

http://lists.transwarplists.net/mailman/create

and got the error message:

Error: Unknown virtual host: lists.transwarplists.net

My thought is that it may be a propogation issue but I wonder why that would be since lists.transwarplists.net clearly exists.

Any ideas?

Tim

[timryberg]

When I began looking around at my server settings I discovered dns records for an ns3.transwarplists.net a name server that I never registered (I did ns1 and ns2 back in late January). I'm not sure if I put it in there by mistake or if a well meaning Sago staffer did when they had access to my system (it was probably me, though).

I removed that record from the Nodeworx settings screen and from the individual domain transwarplists.net in case that is the problem.

In the meantime I've registered the server ns3.transwarphosting.net since I am too lazy to remove it from the 20+ domains on my server.

Do you think this may have had something to do with the problem above?

[IWorx-Paul]

I don't think DNS has anything to do with it Tim.

Take a look in your /home/mailman/transwarplists.com/Mailman/mm_cfg.py

Near the bottom, see what it says for the add_virtualhost line.

Without poking with the install I'm not sure where else to check off hand.

Paul

[timryberg]

Paul,

You're a GENIUS! You hit the nail right on the head.

All the refferences to the virtual domain in the file said lists.transwarplists.net.com

There must have been a glitch in the installer.

Thanks for all of your help. I've successfully created several lists so far and things seem to be running smoothly.

Whatever they're paying you it isn't enough!

Tim

[timryberg]

I forgot to tell you, the version I installed was the newer one than the one you did when you did the script. I just edited the version number in the script in about 5 places it was listed and it worked like a charm.

[IWorx-Paul]

Great, glad it's working for you now Tim. I've updated the mailman.sh script to use the latest mailman version (2.1.5) and I fixed the ".com" problem that was the source of your "virtualhost doesn't exist" problem as well.

Paul

[oaf357]

This looks like exactly what I need but I have an issue:

[root@server1 root]# host lists.braidsbybreslin.com
lists.braidsbybreslin.com is an alias for braidsbybreslin.com.
braidsbybreslin.com has address 65.110.59.27
[root@server1 root]# sh mailman.sh braidsbybreslin.com
This script will install mailman for one domain. It will install it on lists.braidsbybreslin.com.
Mailman will be downloaded, configured, compiled, and installed.
If this sounds ok, hit <enter>. Otherwise, <ctrl-c>.



Please wait...
mailman.sh: line 21: service: command not found
You can not continue until lists.braidsbybreslin.com resolves to valid IP address on this server.

[IWorx-Paul]

This script needs to be run as root - can you confirm whether you're already running it as root or not?

Thanks,
Paul

[oaf357]

I was running it as root.

I don't think service is anywhere in my path. How do I add /sbin/ to my path?

Also, other than the subdomain do I need to create anything else?

[IWorx-Paul]

export PATH=$PATH:/sbin

This will put /sbin in your path. Do that, then try running the mailman script again.

Paul

[timryberg]

Paul,

I know that when you use qmail for mailman you have to create the listname alisas by hand (says so in the documentation, and creating the lists did not create the aliases automatically). My question is, where should the alisa lead?

mailman@lists.transwarplists.net or transwarplists.net (mailboxes that do not exist according to SiteWorx)

Or, since Mailman is a system user:

mailman@rhl.transwarphosting.net (my machine's name) or mailman@65.110.52.170 (the prime IP of the mahcine) or 171 (the IP address the domain is on).

Thanks

[IWorx-Paul]

Actually for a particular list, you should just be able to send mail to

<listname>@lists.transwarplists.net

That that should be it.

If you're talking about an alias such that <listname>@transwarplists.net (without the lists. in the domain), it should point to <listname>@lists.transwarplists.net.

Paul

[oaf357]

Okay. On an RH9 box running InterWorx what is the equivalent to /etc/aliases?

[oaf357]

Okay. Everything seems to be working except that the list address itself fails miserably.

braids@lists.braidsbybreslin.com is a lost cause at the moment.

[IWorx-Paul]

Did you do something regarding your "/etc/aliases" question? That might explain the problem.

[IWorx-Paul]

Did you try to vaddaliasdomain lists.braidsbybreslin.com to braidsbybreslin.com? Or some other method of combining these domains in terms of mail? That seems to be the cause of the troubles right now, since when I send mail to that e-mail address you listed, it bouces back as if I had sent it to the @braidsbybreslin.com instead of the @lists.braidsbybreslin.com. For this set up, they must be different.

Paul

[oaf357]

[root@server1 bin]# ./vaddaliasdomain braidsbybreslin.com lists.braidsbybreslin.com
Error: Both domains already exist, unable to create alias.

And no I didn't find the alternative to /etc/aliases.

[IWorx-Paul]

Well, I haven't been able to figure out yet why it tries to deliver @lists.braidsbybreslin.com to @braidsbybreslin.com, but I found a work around for you. In the ~vpopmail/domains/braidsbybreslin.com/.qmail-default file, I put:
| /home/vpopmail/bin/vdelivermail '' $EXT@lists.braidsbybreslin.com

This won't affect existing mail @braidsbybreslin.com so don't worry about that.

Mailing lists created at lists.braidsbybreslin.com should work now, test it out.

Paul

[timryberg]

Actually for a particular list, you should just be able to send mail to

<listname>@lists.transwarplists.net

That that should be it.

If you're talking about an alias such that <listname>@transwarplists.net (without the lists. in the domain), it should point to <listname>@lists.transwarplists.net.

Paul

Got the following:

Hi. This is the qmail-send program at rhl.transwarphosting.net.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<dchs1994@transwarplists.net>:
Sorry, no mailbox here by that name. vpopmail (#5.1.1)

<info-staff@transwarplists.net>:
Sorry, no mailbox here by that name. vpopmail (#5.1.1)

<allstartrek@transwarplists.net>:
Sorry, no mailbox here by that name. vpopmail (#5.1.1)

--- Below this line is a copy of the message.

Return-Path: <tryberg@softhome.net>
Received: (qmail 22380 invoked by uid 108); 25 Jun 2004 03:00:16 -0000
Received: from mail.cpinternet.com (209.240.224.4)
by apa.liat.liat.jian.co.uk with SMTP; 25 Jun 2004 03:00:16 -0000
X-Node: 2
Received: from softhome.net (modem0121-cp-tnt-d2.cpinternet.com [64.61.224.121])
by mail.cpinternet.com (8.12.10/8.12.10) with ESMTP id i5P32YYb015715;
Thu, 24 Jun 2004 22:02:37 -0500 (CDT)
Message-ID: <40DB95C7.4000805@softhome.net>
Date: Thu, 24 Jun 2004 22:02:31 -0500
From: Tim <tryberg@softhome.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: allstartrek@transwarplists.net, dchs1994@transwarplists.net,
info-staff@transwarplists.net
Subject: Test
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

This is a test message to these lists


This message was sent from the email address that is the administrator of the list. rhl.transwarphosting.net is the "name" of my machine. While it shows the addresses as listname@transwarplists.net I sent them to listname@lists.transwarplists.net

Any thoughts? Do I have to start the mailman deamon? The site is up and allowing me to create/edit new lists so I assumed it was running.

[IWorx-Paul]

This looks like the same problem oaf was having. I'm not sure why I didn't run into this issue actually. Here's a work around for you to try Tim:

as root:
echo "| /home/vpopmail/bin/vdelivermail '' \$EXT@lists.transwarplists.net" > ~vpopmail/domains/transwarplists.net/.qmail-default

[timryberg]

Hi Paul,

I DID have to start the mailman runner, but that didn't help. I then executed the command you gave (as root) and it has done nothing. No response usually means it did what you told it to, but I am still getting that same error.

Also, I thought that it may be a problem with the email at that domain but it isn't my listmaster at transwarplists.net works fine.

[IWorx-Paul]

It did change the bounce message, but now it seems like the mail isn't making it into mailman's system. What's the contents of the /home/vpopmail/domains/lists.transwarplists.net/.qmail-default file?

If you'd like me to help debug on the server you can e-mail the login info to support@interworx.info.

Paul

[timryberg]

Paul,

The file in question contains the following:

| /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox

That is all.

There is another file sinply titled .qmail containing the following

|/var/qmail/bin/preline /usr/bin/python /home/mailman/transwarplists.net/qmail-to-mailman.py

I have emailed you the server login info and would appreciate anything you can do. Thanks again in advance.

[timryberg]

Paul,

I don't know what you did (but would appreciate your telling me so I can learn something from it) but I just got a TON of mail messages from mailman. All if my list created mails and other administrative things apparently since I installed the thing and tried some tests that never worked.

Things seem to be working correctly now and all I can do is say THANK YOU! You are an asset to your company and whatever they are paying you it isn't enough.

Sincerely,

Tim Ryberg
Happy Sago/Interworx customer

[oaf357]

So now that I've gotten Mailman all hooked up my client has decided to go another way and I want to uninstall Mailman.

What's the fastest, cleanest method to uninstall it?

[timryberg]

So now that I've gotten Mailman all hooked up my client has decided to go another way and I want to uninstall Mailman.

What's the fastest, cleanest method to uninstall it?

LOL doesn't that beat all!?

Anyway, I have no idea how to uninstall something installed from source (short of just deleting the files, but somehow I expect you want to remove all traces). I'm sure it's nore complicated than uninstalling an RPM.

Better let Paul answer that one.

[timryberg]

Paul,

will this script work on CentOS? I would assume so since it's from source but figured I should ask first.

Thanks,

Tim

[Aschweti]

Hi there,

I am having a real bad time getting mailman up and running. Following this post (I know it's a little older), I feel that I am exactly where "timryberg" had been, just before Paul solved it for him.

So, if Paul or Tim are still around they might be able to give a hint and end my odyssee :confused:

OK, mailman seems to run fine. I can create lists and sign up for them. My problem seems to be with aliases and I absolutely don't understand why a .qmail-default pointing to qmail-to-mailman.py doesn' work.

Before creating aliases and just using a .qmail-default/.qmail "alias" I didn' get any error messages, but all mails stayed in the qmail queue. So mails to the list never made it to mailman.

Then I used the following script to create aliases and from there on I received "Sorry, no mailbox here by that name" error messages.


#!/bin/sh
if [ $# = 1 ]; then
i=$1
echo Making links to $i in the current directory...
echo "|preline /var/mailman/wthc.net/mail/mailman post $i" > .qmail-$i
echo "|preline /var/mailman/wthc.net/mail/mailman admin $i" > .qmail-$i-admin
echo "|preline /var/mailman/wthc.net/mail/mailman bounces $i" > .qmail-$i-bounces
echo "|preline /var/mailman/wthc.net/mail/mailman confirm $i" > .qmail-$i-confirm
echo "|preline /var/mailman/wthc.net/mail/mailman join $i" > .qmail-$i-join
echo "|preline /var/mailman/wthc.net/mail/mailman leave $i" > .qmail-$i-leave
echo "|preline /var/mailman/wthc.net/mail/mailman owner $i" > .qmail-$i-owner
echo "|preline /var/mailman/wthc.net/mail/mailman request $i" > .qmail-$i-request
echo "|preline /var/mailman/wthc.net/mail/mailman subscribe $i" > .qmail-$i-subscribe
echo "|preline /var/mailman/wthc.net/mail/mailman unsubscribe $i" > .qmail-$i-unsubscribe
fi


Thanks in advance for any help ;)

Best regards,

Alex

[timryberg]

I had a similar issue and all I know is Paul fixed it. You should not have to created aiases by hand at all. They system makes them for you.

[Aschweti]

Hi Tim,

good to see, that you are still around ;)

That's what I understood reading the post. Paul fixed it somehow. Didn't you have a look at your system after he fixed it? As far a I understand you provided him with your login?

Well, maybe he will reply too?

Regarding you answer. That's what I thought too and in the beginning I did not create any aliases, but then all mails to whatever@lists.mydomain.tld ended up in the qmail queue.

I am working on this for the past 3 days, so believe I tried everything I could think of without any success. What makes it even worth, I am quite positive that I am just missing something little... But I don't know what :(

Thanks for replying. Take care,

Alex


PS: Couldn't you check what Paul did?

[IWorx-Paul]

Hi Alex,

To be honest I don't recall exactly what I did to make it work on Tim's server - I'm sure it would come back to me though if I started looking at the problem again. If you could foward one of the bounces messages to support@interworx.info, and provide your server's login info at http://interworx.info/rootdrop I'll take a look.

[Aschweti]

Hi Paul,

thanks for your reply. Sorry, that I didn't respond earlier, but for some reason I didn't get a message, that a new message has been posted and I was so busy today that I didn't have a look anyway.

I start to realise, that interworx is a provider and I have to admit that I am not an Interworx client. I was not aware of that as I Googled directly to the forum. Now I am not sure, if you are even willing to give support.

In case you do: great! If you don't or can't I absolutely understand.

Of course I could forward a bounce message, but unfortunately I am not allowed to send you our server's login. Whatsoever I could describe very detailed what I have currently on the machine.

By now I am very sure, that all this is an alias problem. I've added lists.mydomain.tld:mailman to "virtualdomains" and lists.mydomain.tld to rcpthosts. Of course I restarted qmail. As far as I understand qmail should now send mails to whatever@lists.mydomain.tld to the user "mailman". This users home directory is "/var/mailman", where my mailman installation resides. There I have a .qmail-default file with "|/usr/bin/python /var/mailman/qmail-to-mailman.py" in it. It seems mails never make it to "qmail-to-mailman.py"?!

However you decide, thanks very much and best regards from Germany,

Alex

PS: With the described szenario I get a "Sorry, no mailbox here by that name. (#5.1.1)"-message, when I create the domain "lists.mydomain.tld" with the tool vqadmin, having an actual folder /home/vpopmail/domain/lists.mydomain.tld and creating the .qmail-default file there all mails stay in the qmail queue, but no error messages anymore.

[timryberg]

Hi Tim,

good to see, that you are still around ;)



Yep I am. I haund these forums because I get to harass the InterWorx developers ;-)

Actually that's only part of it. I find I get more intelligent technical responses from people on this forum (InterWorx staff AND users) than my data center. Also I am talkint to people who are all using more or less the same environment than I am (Linux of some RedHat variety).



That's what I understood reading the post. Paul fixed it somehow. Didn't you have a look at your system after he fixed it? As far a I understand you provided him with your login?

Well, maybe he will reply too?

Regarding you answer. That's what I thought too and in the beginning I did not create any aliases, but then all mails to whatever@lists.mydomain.tld ended up in the qmail queue.

I am working on this for the past 3 days, so believe I tried everything I could think of without any success. What makes it even worth, I am quite positive that I am just missing something little... But I don't know what :(

Thanks for replying. Take care,

Alex


PS: Couldn't you check what Paul did?

Paul has already responded. IIRC now that I think about I think he fixed cron or something like that.

You should not have to edit ANY config files at all, the mailman installer is supposed to do that for you. This is actually the first of two times I've had problems. The second time was a prob;em with vPopmail not being confugured quite right by Sago when they installed InterWorx (it was one of the first times they'd done it on CentOs and they installed it AFTER the OS had been installed). I'm sure Paul will figure it out.

[pascal]

Hello :)

Looking for a mail list manager I thought use :
- mailman
or
- sympa

....

What do you thing about mailman ?
What is the solution for your last pbm ?

I found this tuto about qmail and mailman http://adminblogs.com/steve/articles/326.aspx

For you, should it works on a centos / interworx-cp box ?

finaly, Paul, the link you gave http://nav.bandersnatch.org/clues/qmail-vpopmail-mailman.html is down :\

Thanks for your help and any advises
ps : in fact I thought install sympa (and wwsympa) but if there is knowledge here about mailman it should be better to install it.

Pascal

[timryberg]

Hello :)

Looking for a mail list manager I thought use :
- mailman
or
- sympa



If I had my chouce I'd use sympa hands down but it's too complex for me to install at my current technical level (and a lot of the docimentation is in french or scattered english).

Check out http://lists.squidge.org/wws for a sympa mailing list server example.


....
What do you thing about mailman ?
What is the solution for your last pbm ?



Mailman is okay if you only have one or two lists but if you ruin many lists and each list has users on many lists there is no "MY Mailman" section on the site and each list has it's own password. (of course there is one master mailman password.

[/quote]

I found this tuto about qmail and mailman http://adminblogs.com/steve/articles/326.aspx

For you, should it works on a centos / interworx-cp box ?
[/QUOTE]

yes I have it installed on CentOS/InterWorx and it works just fine.

Tim

[pascal]

Thanks tim

lol, I prefer SYMPA because it is French. It is not because I am chauvinistic but contrary to you because documentation is in French :)

but you right it seems to be very complex to install and more to install with QMAIL.

I'll do some tests on a test box.

I will shout for help if I have some pbms with mailman :)

Tim, do you remember the last solution Paul did on your box to have mailman working ?

Thanks for your help

[pascal]

Hi Alex,

To be honest I don't recall exactly what I did to make it work on Tim's server - I'm sure it would come back to me though if I started looking at the problem again. If you could foward one of the bounces messages to support@interworx.info, and provide your server's login info at http://interworx.info/rootdrop I'll take a look.

Hello Paul and tim

Is the pbm oaf, tim and others had was something like this :


add this
|/var/qmail/bin/preline /usr/local/bin/python /home/mailman/foo/qmail-to-mailman.py

in
~vpopmail/domains/lists.xxxx.com/.qmail-default and not in .qmail ?

Thanks

[pascal]

I'v ran the paul's script it juts work fine :)

The only change I've made is in ~vpopmail/domains/lists.xxxx.com/.qmail-default , I added |/var/qmail/bin/preline /usr/bin/python /home/mailman/foo/qmail-to-mailman.py

Well everything is working fine but I can't figure out how to deny the ability to users to create a new list ?

In fact I'd like that only admin was able to create new list from the web interface.

???

Thanks
Pascal

[IWorx-Paul]

Hi Pascal,

~vpopmail/domains/lists.xxxx.com/.qmail-default and not in .qmail ?
That sounds familiar Pascal, that was probably the problem.

In fact I'd like that only admin was able to create new list from the web interface.
If I recall correctly, the you can't create a new list unless you know the admin password. Is that not correct?

Paul

[pascal]

Paul,

May I send my mailman website adress by mail. Then could you please try to create a list ?

In fact I'd prefer a tool to generate mails for news / announcements : it why I'll try to use mailman or ezmlm (see my other post about ezmlm and siteworx api to add automaticly the email of a new siteworx account to a list of annoucement/news)

Thanks

[timryberg]

If I recall correctly, the you can't create a new list unless you know the admin password. Is that not correct?

That is corect, the server has a master admin password and anybody who knows it can create a list. If you don't want others to be able to create a list edit the html pages to remove the link to the create list page and then don't share the admin password.

Tim

[timryberg]

Hi Pascal,
That sounds familiar Pascal, that was probably the problem.

It also looks faniliar to me (though I have no idea what it means; the first time I read it I though it was a permissions problem but the group names do not start with a period).

To answer Pascal's question the only thing I know is that the first time he fixed it (RedHat9) it was apparently an issue with cron. The second time (CentOS) was a problem withhow qmail was instlled/configured. Not sure more than that.

[pascal]

Hello thanks and soory as I forgot to update this thread to tell that everything is working fine :)

Now I'm trying to figure out how add a new email to a list automaticly from a script

I also try to setup a list to use it as an annoucement list, but it should be ok as I found a post about this in the mailman faq

Thanks
Pascal

[pascal]

And also have to say that the Paul installation script work just fine.

Everything was ok the first time

I only change the script to add lines in .qmail-default rather than .qmail
As it is written in the Paul's web link he gave

So thanks Paul :)

Pascal

[houndbee]

I just installed Mailman using this script. I guess I need to add the following aliases, but I don't know how. Help appeciated

## mailman mailing list
mailman: "|/home/mailman/kaustubh.org/mail/mailman post mailman"
mailman-admin: "|/home/mailman/kaustubh.org/mail/mailman admin mailman"
mailman-bounces: "|/home/mailman/kaustubh.org/mail/mailman bounces mailman"
mailman-confirm: "|/home/mailman/kaustubh.org/mail/mailman confirm mailman"
mailman-join: "|/home/mailman/kaustubh.org/mail/mailman join mailman"
mailman-leave: "|/home/mailman/kaustubh.org/mail/mailman leave mailman"
mailman-owner: "|/home/mailman/kaustubh.org/mail/mailman owner mailman"
mailman-request: "|/home/mailman/kaustubh.org/mail/mailman request mailman"
mailman-subscribe: "|/home/mailman/kaustubh.org/mail/mailman subscribe mailman"
mailman-unsubscribe: "|/home/mailman/kaustubh.org/mail/mailman unsubscribe mailman"

[IWorx-Tim]

Please log into your server and navigate to /chroot/home/<uniquename>/var/<domain_name>/mail

Open the file .qmail-default (it will already exist) and REPLACE it's current contents with the text you have above.

Please understand that this will disable all InterWorx aliases on that domain . If you need other aliases on that domain then put the text above in the file BEFORE the current text and they should work.

[marco114]

Sorry to open an old thread. My customer has multiple domains they want mailman lists on. Is this script safe to run to have more domains with mailman?

Thanks
Marc