Since a failed mailman 3 installation (impossible to reinstall and no support or developpment), I can't backup mailman anymore
https://paste.yunohost.org/raw/gafaxasego

After initial install, mailman won't work and show this error page

Yunohost version : 4.3.3

The incoming mails aren't fed through rspamd, making it impossible to auto-discard spam messages.
It would be helpful if they were and there was a header field that i could match in mailman to filter messages.

Bonjour,
Depuis quelques temps, j’ai le message suivant quand j’essaie d’envoyer un message sur une liste mailman :
Une erreur est survenue lors de l’envoi du courrier. Le serveur de courrier a répondu : 5.1.1 <[email protected]>: Recipient address rejected: User unknown in virtual mailbox table. Veuillez vérifier l’adresse du destinataire [email protected] et essayer à nouveau.
L'interface admin marche très bien, donc je ne vois pas d'où peut venir le problème ?

Like discussed in this post : https://forum.yunohost.org/t/access-mailman-list-administration-interface-without-yunohost-account/8872
I have exactly the same usercase as chateau. Would be nice if it could be included in the package !

Hi,
I use mailman v2 from yunohost without major problem.
Users can subscribe without being a yunohost server know user. This is the public side !
As soon as a user wants to authenticate in order to manage its subscription, he needs to provide a yunohost user/password information.

How can I fix that and give users the right to manage their subscription ?

Thanks
D.

I am not able to send email to the list after installing the app.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<[email protected]>: host spool.mail.gandi.net[217.70.178.1] said: 554 5.7.1
    <[email protected]>: Relay access denied (in reply to RCPT TO command)

any suggestion ?

Hello, as it's not possible to install 2 times mailman instances on a yunohost server (I have a few domain on my server), how can I have different mailing list with different domain name ?
It's important for me to separate those domains event for the mail adress.
Sincerely
Yvan

http://docs.mailman3.org/

Great new upgrade. Relies on #7.

bonjour,

I've installed mailman, it looks cool, however I was confused because when I create a new list in a specific language (French), all the subscription templates are in English, which is not suitable for our French users.

I was beginning to translate the first sample, when I thought it might already translated. I've found them in /usr/share/doc/mailman/examples/fr/ and in /usr/share/mailman/fr/ (they look the same).

So to get everything translated in my list, I've done this from the command line:

sudo cp /usr/share/doc/mailman/examples/fr/* /var/lib/mailman/lists/ma_liste/fr/

is it a known limitation of mailman?

Like discussed in this post : https://forum.yunohost.org/t/access-mailman-list-administration-interface-without-yunohost-account/8872
I have exactly the same usercase as chateau. Would be nice if it could be included in the package !

Hi,
When I send mail to mailman, I see in mail.log the following error 550 5.1.1 [email protected]: Recipient address rejected: User unknown in virtual mailbox table

/var/lib/mailman/data/virtual-mailman know this address, but /etc/postfix/main.cf dosen't contain any reference to virtual-mailman. I don't know if it's expected ?

mailman 2.1
yunohost 2.7.9 over debian jessie in LXC

thanks for help

Hello,

I have an issue with mailman,
I can't create a new mailing list,
I have this issue "Erreur: Vous n'êtes pas autorisé à créer de nouvelles listes".
I don't know what is the , I used root@mydomaine for the creator .

How to do that to create a newmailingliste

As I wrote in the forum to the question:

Messages from Mailman lists should be monthly archived, but Mailman says that there is no archive since hundred posted messages for 6 months.

and

I had the same issue with mailman and I solved it by changing the owner of some archives directory (as far as I can remember) to allow mailman to write in.
I’m sorry, I dit that a few months ago, I don’t remember the details

What I found out:

The permissions that seem to be wrong is that folders for archives (in /var/lib/mailman/archives/) are owned by www-data:www-data. Well at least some of them. When making a new list, the system created archive folders owned by www-data:www-data and then when mailman receives a first message that's supposed to be archived and wants to save it to that folder it cannot (there's no error), unless it is owned by list:www-data (user list and group www-data)

So there are two solutions:

• you change the owner of the folder (for example /var/lib/mailman/archives/your-new-list) to list (but not the group, group should stay www-data):

    $ sudo su
    # cd /var/lib/mailman/archives/private/
    # chown list:www-data your-new-list*

• you add user list to group www-data. after that even if the folder is owned by www-data, user list can write to it.

    $ sudo su
    # adduser list www-data
    # service mailman restart
    (maybe it also needs a reboot)

this seems pretty hacky, and should be solved in some other way, I think. i have no idea what security consequences this has.

maybe there's also a setting somewhere with what permissions are those archive folders created.

Something must be fixed in the installation so that archives work after it without those hacks.

hello,
with edithtml I can modify html files. But for text files, the text (in French) is displayed in iso-8859 instead of utf-8. Even if I switch encoding to display it correctly, I get this error:

Bug in Mailman version 2.1.23

We're sorry, we hit a bug!

Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.

Here are more details:
https://forum.yunohost.org/t/yunohost-update-to-3-7-1-1-fail-due-to-mailman/11141/2

Spotted during test on the bullseye CI

Dunno what to do about this ... I guess we could still hack something by manually porting the .deb to bullseye or something, but is that the right thing to do ...

Hi,
I just tried to create a new list, and got this error page :

Bug in Mailman version 2.1.29

We're sorry, we hit a bug!

Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs or the web server logs.

The if I try again to create the same list, I get

Error: List already exists: plaftest

The list has been created, but doesn't work. If I send a mail to it, I get a "Delivery Status Notification (Failure) : 550 5.1.1 [email protected]: Recipient address rejected: User unknown in virtual mailbox table".

I can give some more logs if necessary and if you tell me how.

Please, having a 'real' upgrade script would be great to upgrade our own half-broken mailman instance :)

Bonjour,
J'ai eu une erreur en essayant de mettre à jour mailman aujourd'hui, voici le log : https://paste.yunohost.org/raw/asitiyuqoj
Maintenant si je veux retenter la mise à jour, j'ai le message d'erreur suivant :

Vous ne pouvez pas faire ça maintenant car dpkg/apt (le gestionnaire de paquets du système) semble avoir laissé des choses non configurées. Vous pouvez essayer de résoudre ce problème en vous connectant via SSH et en exécutant sudo apt install --fix-broken et/ou `sudo dpkg --configure -a'.

Mais les 2 commandes proposées ne donnent aucun résultat (rien à modifier).

Hi,

I use to access my mailman admin page using a link of the following form: https://mydomain/mailman/admindb/admins
Since I updated mailman to v2.1.29 I get redirected to the Yunohost user page (the page with the colored tiles) everytime I try to access the mailman admin.

I can however still access the list configurations, such as https://mydomain/mailman/listinfo/admins

Let me know if I can collect more information for you !

Cheers

Sur un serveur à jour :

args:
app: mailman
args: domain=xxxxxx.ovh&path=%2Fmailman&admin_password=XXXXXXXXXX language=fr&is_public=1
force: false
label: Mailman
no_remove_on_failure: false
ended_at: 2019-09-23 12:58:22.147896
env:
YNH_APP_ARG_ADMIN_PASSWORD: '**********'
YNH_APP_ARG_DOMAIN: xxxxx.ovh
YNH_APP_ARG_IS_PUBLIC: 1
YNH_APP_ARG_LANGUAGE: fr
YNH_APP_ARG_PATH: /mailman
YNH_APP_ID: mailman
YNH_APP_INSTANCE_NAME: mailman
YNH_APP_INSTANCE_NUMBER: '1'
YNH_CWD: /var/cache/yunohost/from_file/mailman_ynh-1240761bf871657f82851bb5ef2da4d1a508d28a/scripts
YNH_INTERFACE: api
YNH_STDINFO: /tmp/tmprgf8RZ/stdinfo
YNH_STDRETURN: /tmp/tmp5q6vdy/stdreturn
error: 'Une erreur inattendue est survenue : shell command return code: 1'
operation: app_install
related_to:

• • app
  • mailman
    started_at: 2019-09-23 12:58:00.220380
    success: false