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.
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).
…
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.
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.
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)
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.
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.
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.
I would prefer create every mail then go into /chroot/home/<uniquename>/var/<domain_name>/mail
and edit every mail to put each pipe.
edit
.qmail-mailman and enter |/home/mailman/kaustubh.org/mail/mailman post mailman
.qmail-mailman-admin and enter |/home/mailman/kaustubh.org/mail/mailman admin mailman
etc…
It should work too and let the .qmail-default clean, no ?
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?