I packaged Mailman (2.x) for Yunohost, if someone wants to test and give me feedbacks you are very much welcome. Note that the state is clearly in progress, as so far I tested it only a virtual machine by simulating MX record. It seems to be working, but I haven’t tested it in a prod environment.
Disclaimer - I am not a mail expert, and especially not a postfix expert. Feel free to review what I’ve done and propose a cleaner configuration if you know what you’re doing .
Mailman is a free software for managing electronic mail discussion and e-newsletter lists. Mailman propose a web interface where admins can create, configure and moderate lists, and users can register to lists and check archives (example).
What the package does
It installs mailman and configure nginx and postfix. After the installation, you should be able to access the web interface through http://yourDomain.tld/mailman/ (or the path you chose during install). Mailman lists are created with the format listname@lists.yourDomain.tld (you can also change the lists prefix during install).
NB : You will need to configure a DNS (MX?) record for lists.yourDomain.tld
Thanks @CaptainSqrt2 for this package: installing was really easy!
I faced the first problem after having created the first mailing-list: all went good, I received an email which confirms the setting of this list. But the adress it gave brings me back to the YunoHost (SSO) portal…
I didn’t make the DNS configuration, because the url is “http://mydomain.tld/cgi-bin/mailman/admin/list-name” (and so not in a list.mydomain.tld sub-domain.
Have someone a clue about what I should check or try?
Bonjour,
Merci beaucoup @CaptainSqrt2 pour avoir packagé Mailman!
Toute l’installation s’est bien passée, mais l’adresse qui m’est donnée par le courriel de confirmation reçu suite à la création de la première ML m’indique une adresse qui me ramène sur le portail Yunohost (donc non identifiée par YunoHost).
Je n’ai pas fait la config DNS pour le sous-domaine list.mondomaine.tld parce que l’url donnée par Mailman n’avait pas l’air de la nécessiter. (Et donc je n’ai pas bien pris vraiment de temps pour le faire… ).
Quelqu’un.e aurait-ille des pistes pour mon problème?
I’m not sure to understand exactly what the problem is though . The URL for the admin interface should be something like : http://YOURDOMAIN.TLD/mailman/admin/LISTNAME. It is expected that it redirects to the SSO : you should be at least login as some user to attempt to access the admin interface (then it asks the list admin password anyway).
If you want the lists to work, your should create the DNS MX entry for lists.yourdomain.tld (or whatever suffix you chose), otherwise people won’t be able to send mails to the lists (or at least my understanding is that it shouldn’t work )
sorry to bother, but I broke my installation of Mailman and I’m not able to install it again. Well, in fact, I never was able to install it.
After several minutes, I still don’t have the prompt. So I have some questions :
Is the “user admin” a user of YunoHost ?
Is the “Mailman administration password” a new password ?
Is it possible to have no prefix for the lists.
How can I fix this ?
unfortunately the package have not been maintained for quite some time (maybe a year ?), and it was kind of quick and dirty… Hopefully a package for Sympa (a more modern mailing list manager)
To answers the specific questions :
The user admin is in the LDAP database. It’s not really a user like the “john doe” or whatever you manage with “yunohost user”, it’s a special user.
The mailman administration password is a new password, yes
From my understanding of mailman and postfix, it’s easier to have no prefix for the lists. Though theorically you should be able to have no prefix, but I’m not sure how to do it exactly. The app assume there’s a prefix.
Uh sorry, I realize you were talking about the mailman admin, not the Yunohost admin.
From what I recall, the mailman admin (which should be a regular YunoHost user) is the user who will have access to mailman web administration pages (e.g. to create new lists and so on). He will still need the administration password though. This user should be created / exist before installing mailman.
Sympa is not packaged for now. There are some discussions about it but it won’t be before a few monthes .
So, if I use a YunoHost user as Mailman admin, installation never finishes.
I need to install a list server. I would prefer to install a packaged one. Is it better to help debugging Mailman package ? Or to see what is needed to install Sympa ? I need a listserver on my Yunohost instance for the end of february.
Let know what you think is better. I won’t have time to make a test environnement, but I can share my steps to install Sympa.
Personally I have experience with Mailman, so I can help you debugging. On the other hand, having someone look into installing Sympa would be a good start to package it. But I have no experience about it.
Do you have some logs to investigate what fails in Mailman install ?
I’m sorry but I had no time to go further this days.
I would like to had pointers to the install script to see where it hangs, more precisely. Is it possible to use the “yunohost app install” command with a local copy of the repository ?
Yes, you can git clone the repo and install from local files. If you really want to investigate and run the install multiple time, you might want to use ynh-dev to have a virtual machine with which you can have snapshots.
But according to your last message maybe you’re okay with it now
Posting to lists is now working but configurations in postfix and mailman where missing. I’ll give some details later.
I still have a problem. Access to mailing lists archives is missing. Adding this in mailman conf for nginx does not solve the problem.
location /pipermail {
alias /var/lib/mailman/archives/public;
autoindex on;
}
When I use the mailing list archive link, I’m back to the main Yunohost page.
You can also manually edit the app settings in /etc/yunohost/apps/mailman (the unprotected_regex) and regen the ssowat conf with yunohost app ssowatconf if you want to avoid the full reinstallation.
I had a look at those regex rules, but the app is not public. Only YunoHost users should access Mailman and its archives. So a second path should be added to settings.yml. I can’t find how to do that.
If I modify ssowat.conf.json, pipermail access could be broken with other installations or upgrades I suppose.
No need anymore for a special prefix like lists.thedomain.tld (though you can still create a special domain lists.yourdomain.tld manually in YunoHost and install the app for this domain)
No more dirty hack of postfix conf, now uses a proper hook during postfix’s conf regen
Je viens juste de tester l’installation, l’inscription et désinscription à une liste publique, et procédé à la désinstallation.
Contexte : YunoHost 2.7.* installé sur base Debian 8 Jessie à jour sur un VPS avec redirection vers mon_serveur.tld par IP et non DNS.
Installation : pas de problème.
le DNS n’est pas bien configuré, il est impossible d’utiliser la fonction de confirmation d’inscription ou de désinscription par réponse au mail. Cependant le lien figurant dans le corps du message fonctionne pour ces deux opérations.
Désinstallation : pas de problème.
EDIT : Il faudrait voir comment franciser ces messages Peut-être puis-je aider ?
I just tested the installation, subscription and unsubscription to a public list, and proceeded to uninstall.
Context: YunoHost 2.7. * Installed on Debian 8 Jessie updated on a VPS redirection to my_server.tld via IP not by DNS.
Installation: no problem.
If the DNS is not configured correctly, you can not use the un/subscription confirmation function by replying to the mail. However, the link in the body of the message works for both of these operations.
Uninstall: no problem.
EDIT: You should see how to Frenchify these messages May i could try to help ?
.
. The URL for the admin interface should be something like : 
)
