- Mailman-users - lists.mailman3.org

Help with fresh debian install
by Mark Dadgar Oct. 11, 2019

Oct. 11, 2019

Mailman3-Users, First-time poster, long-time Mailman user (since August of 2002!). I brought up a fresh install of Mailman3 via the current Debian package alongside my current 2.1 setup (installed and updated from source since 2002) on Ubuntu 18.04 LTS. Importing lists from 2.1 has been a real problem. I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: — mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck Traceback (most recent call last): File "/usr/bin/mailman", line 11, in <module> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main initialize(config_path) File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 189, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 152, in initialize_2 mailman.core.logging.initialize(propagate_logs) File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 157, in initialize _init_logger(propagate, sub_name, log, logger_config) File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 110, in _init_logger handler = ReopenableFileHandler(sub_name, path_abs) File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 50, in __init__ self._stream = self._open() File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 53, in _open return codecs.open(self.filename, 'a', 'utf-8') File "/usr/lib/python3.6/codecs.py", line 897, in open file = builtins.open(filename, mode, buffering) PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' Error in atexit._run_exitfuncs: Traceback (most recent call last): File "/usr/lib/python3.6/logging/__init__.py", line 1945, in shutdown h.flush() File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 56, in flush if self._stream: AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' — If I run it as root, it runs for a long time but spews a HUGE stream of these errors to /var/log/mailman3/mailman.log: — Oct 03 17:08:48 2019 (19118) Skipping and preserving unparseable message: 1570147727.3029191+80f1cc4d18f54868ad6162e8e41e52567185e983 Oct 03 17:08:49 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' Oct 03 17:08:49 2019 (19118) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' Oct 03 17:08:49 2019 (19118) Skipping and preserving unparseable message: 1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c Oct 03 17:08:50 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147729.8732843+1cd24522f62dbd73c759a0f9a749a2ed63c91668.pck' Oct 03 17:08:50 2019 (19118) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147729.8732843+1cd24522f62dbd73c759a0f9a749a2ed63c91668.pck' Oct 03 17:08:50 2019 (19118) Skipping and preserving unparseable message: 1570147729.8732843+1cd24522f62dbd73c759a0f9a749a2ed63c91668 Oct 03 17:08:51 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147731.1456919+4354e647280c69f4dbfbd5a158b682fe3ed6cbcf.pck' Oct 03 17:08:51 2019 (19118) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147731.1456919+4354e647280c69f4dbfbd5a158b682fe3ed6cbcf.pck' Oct 03 17:08:51 2019 (19118) Skipping and preserving unparseable message: 1570147731.1456919+4354e647280c69f4dbfbd5a158b682fe3ed6cbcf Oct 03 17:08:53 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147732.4526153+f423b0ba2693b41ffc3f829da2290639634c349d.pck' Oct 03 17:08:53 2019 (19118) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147732.4526153+f423b0ba2693b41ffc3f829da2290639634c349d.pck' Oct 03 17:08:53 2019 (19118) Skipping and preserving unparseable message: 1570147732.4526153+f423b0ba2693b41ffc3f829da2290639634c349d — It also dumps some mail footer templates into the template directory that are owned by root, which seems … incorrect? Any thoughts on what’s going wrong here? Many thanks in advance! Really looking forward to having modern archives! - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 9

Show diplay_name in a list
by ruben＠bkonrad.de Oct. 10, 2019

Oct. 10, 2019

Hello, I'm trying to figure out how to show the display_name of a member in postorius in Members > Subscriber. I was trying to add {{ member.diplay_name }} in the template ${postorius}/templates/postorius/lists/members.html Here an abstract of where I inserted the code: [...] {% for member in members %} <tr> {% if role == 'subscriber' %} <td> <label class="checkbox-inline"> <input type="checkbox" class="member-checkbox" name="choices" id="id_choices_{{ forloop.counter0 }}" value="{{ member.email }}" /> {{ member.display_name }} <{{ member.email }}> </label> [...] I could not figure out why it wouldn't work. I'm running mailman3 Version 3.1.1-9 on an Ubuntu 18.04. Any idea what I was missing there? Thanks in advance for any help. - Ruben

4 4

Personalization issue when no To header?
by Alan So Oct. 8, 2019

Oct. 8, 2019

We have ported a number of lists from mailman 2 to mailman 3 earlier. We cannot find any personalization setting in the mailman 3 web UI or using the mailman client. It is fine as it is not essential. However, recently we notice an issue. As the lists in the mailman 2 probably have personalization turned on, it looks like that the setting are also migrated by using "mailman import21". Recently, some users start sending mail simply with Bcc without any addresses in the To header. We notice the following error: Oct 08 11:26:03 2019 (1832) Uncaught runner exception: 'to' Oct 08 11:26:03 2019 (1832) Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver refused = agent.deliver(mlist, msg, msgdata) File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 163, in deliver callback(mlist, message_copy, msgdata_copy) File "/usr/local/lib/python3.6/site-packages/mailman/mta/personalized.py", line 58, in personalize_to msg.replace_header('To', formataddr((name, recipient))) File "/usr/lib64/python3.6/email/message.py", line 558, in replace_header raise KeyError(_name) KeyError: 'to' After tracing the source codes above, we suspect that the issue was caused by no To header due to personalization is turned on. Any quick suggestion of workarounds such as how to turn off personalization for all lists? We do not have much experiences with mailman shell. Thanks a lot.

1 0

Mailman 3 Internationalization setup
by Abhilash Raj Oct. 7, 2019

Oct. 7, 2019

Hi All, Mailman 3 is now setup for continuous internationalization. We are using Hosted Weblate[1], which is the hosted service for the Weblate project[2]. It is actually quite nice and I've been learning how to properly document a Django project from it's documentation. Which brings me to it's documentation. Weblate has great documentation for translators[2]. The UI pretty simple and should be easy to navigate around. We have setup the workflow in a way that each commit in Gitlab generates a webhook and updates Weblate. Weblate is then able to pull all the changes in real time. To pull translations back into Gitlab, I have a custom script running every night that pulls translations (as commits) and generates pull requests against the upstream repos. Weblate has the ability to automatically push the translations back, but for security reasons, I didn't want to give a 3rd party service direct push access to our repos. I've been working on a Patch to Weblate[3], which would allow it to send translations as Merge Requests (as compared to direct-push). After it is merged and deployed at hosted.weblate.org, I hope I can retire my custom script. We have setup the following projects: - Mailman Core (https://hosted.weblate.org/projects/gnu-mailman/mailman/) - Postorius* (https://hosted.weblate.org/projects/gnu-mailman/translations/) - Hyperkitty (https://hosted.weblate.org/projects/gnu-mailman/hyperkitty/) - Django-mailman3 (https://hosted.weblate.org/projects/gnu-mailman/django-mailman3/) There should be empty .po files generated for most languages supported by Django and Mailman Core. If there are any questions or bugs related to source strings, please send out an email to mailman-developers(a)python.org. The current translation %age is pretty low, hopefully we'll be ale to get it close to Mailman 2 sometime soon :) [1]: https://hosted.weblate.org/projects/gnu-mailman/ [2]: https://docs.weblate.org/en/latest/user/translating.html [3]: https://github.com/WeblateOrg/weblate/pull/3024 [*] Yeah, the URL for Postorius is a bit weird, because it was called "translations" before. At the time, I didn't know the difference between a project and a translation component in Weblate terminologies. And they don't give out permissions to change the URL, so we're maybe stuck with it. -- thanks, Abhilash Raj (maxking)

1 0

Mailman 3 installation documentation
by Abhilash Raj Oct. 7, 2019

Oct. 7, 2019

Hi All, I have been trying to work on revamping the documentation site we have at https://docs.mailman3.org. It is on https:// but I am not sure why the http->https redirect doesn't work in Readthedocs. I have set it to "serve always from https". Anyway, it might not look too different right now, but there are some small re-organizations. I have been learning some new ReST and Sphinx tricks and been trying to cross-reference and link various sections and settings. The docs site shows up Mailman's logo now (I didn't even know we could do that ;-). There is a place[1] for all supported Django settings that Postorius and Hyperkitty have. I am also planning to add some common Django settings that often people have to lookup and is not fun for people from non-python backgrounds. Hopefully, it will make lives easier for administrators. I have reverted my own stupid decision to use "sudo pip3 install" in the docs to instead use virtualenv. The installation docs are going to grow to be more comprehensive. I am also working on mailman-web project[3], which should simply installation process for all the web components using a single project and provide better guidance on Django's settings file management and howto run manage.py commands. I have added a `mailman-web` command, which, for those of you familiar with internal details of Django, is going to be our custom manage.py script. It sets up settings correctly and would hopefully reduce the pain of using `django-admin` and/or finding out the right path for `manage.py` script. It is still not ready for prime time, but it is usable. Early adopters can play with it if they like! I would really appreciate if people who have tried to manually install Mailman 3 in the past would share their experiences about what they think could be documented better. You can reply here or open an issue[2]. The user documentation are going to follow, hopefully soon :) [1]: https://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyp… [2]: https://gitlab.com/mailman/mailman-suite-doc/issues [3]: https://gitlab.com/mailman/mailman-web -- thanks, Abhilash Raj (maxking)

2 1

confirm mail rejected
by Marc Sluiter Sept. 29, 2019

Sept. 29, 2019

Hi, im trying to setup mailman and have an issue: first my environment: - I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/ - I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/ I got almost everything working (with some configuration modifications, see other mail). The only thing which doesn’t work is conformation mails, they are rejected: In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp. Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps? For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/ Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)? Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?) Thanks and greetings, Marc

4 4

Cannot show archives
by Qiuhong.Su �K秋�t Sept. 27, 2019

Sept. 27, 2019

Hi all, After I setup mailman3 and run mailman-suite, I can do: 1. Register user 2. Login 3. Create new Domain 4. Create new List 5. Subscribe to the list When I try to send email to the list by run command: echo ��test email�� | mail �Cs ��test email�� test(a)example.com<mailto:test@example.com> User test can receive this email, but I cannot find it on Archives, and other members cannot receive this email too. Can anyone help me? Thank you! Regards, Qiuhong ************************************************************************* This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. [Delta Electronics, INC. China] *************************************************************************

4 4

Linking to a forum thread from a (news) website.
by Paul Arenson Sept. 25, 2019

Sept. 25, 2019

I have been struggling to get this right and I think I have finally done it. I have a website with many opinion and news articles. I have linked from the article to a pre-written thread, such as from here: EXAMPLE WEBSITE ARTICLE https://www.tokyoprogressive.org/remembering-the-tsushima-maru-disaster-75-… to EXAMPLE THREAD ON LIST Title: Remembering the Tsushima Maru Disaster 75 Years Later https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… PROBLEM The problem is that this does not show the subsequent comment that was added. And SHOW REPLIES BY DATE does not do it either. SOLUTION I figured out that all replies are listed under Re:, so if the first comment does not have the Re:, then it gets cut off. So if I click https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… you will see all the subsequent posts. Since I want to post a link BEFORE anyone starts replying, I have to make my first post in the thread titled Re: EXAMPLE OF NEW POSTING STYLE Make sure the thread has a Re: in it. (Actually I made a mistake and wrote Re; and it still worked.) https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… Or: https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… ----------------- QUESTION Am I correct that if I want to create a thread and link to it, but make sure the first note is included, I need to make the thread title: Re: Something? -----------------

2 2

Manual setup - permissions
by Tobias Hachmer Sept. 25, 2019

Sept. 25, 2019

Hello, I'm new to mailman3 and started to setup an instance from scratch per hand, but I'm struggeling running the peaces with the correct user/permissions. I can't find anything regarding running this and that with that user in the docs, so I have the following: virtualenv_dir: /opt/venvs/mailman3 Installed packages in venv: - "Django>=1.11" - "django-haystack" - "libsass" - "mailman==3.3.0" - "mailmanclient" - "mailman-hyperkitty==1.1.0" - "postorius==1.3.0" - "hyperkitty==1.3.0" - "whoosh" - "uwsgi" I have installed the core stuff in /opt/mailman3/core, all is owned by user+group "mailman3": root@host:/opt/mailman3# tree . ├── core │ ├── etc │ │ ├── hyperkitty.cfg │ │ ├── mailman.cfg │ │ └── uwsgi.ini │ ├── log │ │ ├── bounce.log │ │ ├── debug.log │ │ ├── mailman.log │ │ ├── plugins.log │ │ └── smtp.log │ └── var │ ├── archives │ │ └── hyperkitty │ │ └── spool │ │ ├── ... │ ├── cache │ ├── data │ │ ├── mailman.db │ │ ├── postfix_domains │ │ ├── postfix_domains.db │ │ ├── postfix_lmtp │ │ └── postfix_lmtp.db │ ├── lists │ │ └── admin.lists.... │ ├── locks │ ├── master.lck │ ├── master.lck|...|...|... │ ├── master.pid │ ├── message" │ │ ├── ... │ ├── queue │ │ ├── archive │ │ ├── bad │ │ ├── bounces │ │ ├── command │ │ ├── digest │ │ ├── in │ │ ├── nntp │ │ ├── out │ │ ├── pipeline │ │ ├── retry │ │ ├── shunt │ │ └── virgin │ └── templates The django project is installed in /opt/mailman3/web, all is owned by user+group "nginx": └── web └── project ├── db │ └── mailmansuite.db ├── emails ├── fulltext_index │ └── _MAIN_0.toc ├── logs │ ├── mailmansuite.log │ ├── uwsgi-error.log │ └── uwsgi.log ├── manage.py ├── __pycache__ │ ├── settings.cpython-35.pyc │ └── urls.cpython-35.pyc ├── run │ └── uwsgi.sock ├── settings.py ├── static ├── urls.py └── wsgi.py The mailman3 core ist running with user+group "mailman3". And the uwsgi service is running as root with drops privileges to user+group "nginx". Now, running the scheduled tasks (which run from user+group "nginx") for django I ran into permission problems, because the nginx user can't access/write to the needed files in /opt/mailman3/core/... If anyone of you is able to read ansible tasks, this is how I set this up via ansible: https://github.com/freifunk-mwu/ansible-ffmwu/blob/mail/roles/service-bundl… I would appreciate any hints how to run the different peaces of mailman3 with the correct user/groups/permissions. Thanks in advance, Tobias

4 4

Re: Issues with migrating from Mailman2 to Mailman 3
by Mark Sapiro Sept. 24, 2019

Sept. 24, 2019

On 9/23/19 12:03 AM, Paul Arenson wrote: > Thank you Mark. > > I found my solution. Simplifies things. People do not have to even > think about subscribing….. <snip> > How does that sound? OK -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0