- Mailman-users - lists.mailman3.org

messages go to shunt queue
by Danil Smirnov 10 Sep '20

10 Sep '20

Hi guys, I've faced weird Core behaviour after the last upgrade of the docker images. All the messages sent to a list now go straight to shunt queue with the following error in the logs: --- Sep 06 22:41:32 2020 (27) Uncaught runner exception: 0 Sep 06 22:41:32 2020 (27) Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/usr/lib/python3.8/site-packages/mailman/core/chains.py", line 57, in process if link.rule.check(mlist, msg, msgdata): File "/usr/lib/python3.8/site-packages/mailman/rules/dmarc.py", line 314, in check if maybe_mitigate(mlist, address): File "/usr/lib/python3.8/site-packages/mailman/rules/dmarc.py", line 286, in maybe_mitigate answer = is_reject_or_quarantine( File "/usr/lib/python3.8/site-packages/mailman/rules/dmarc.py", line 217, in is_reject_or_quarantine for record in txt_rec.items[0].strings) KeyError: 0 Sep 06 22:41:32 2020 (27) SHUNTING: 1599432092.4326646+4cbb58a0dd5d9705946ca583835e63ec175536e3 I'm witnessing the same behaviour in two different installations for all the messages sent to list (with plain text body like "it's a test"). --- Any insight would be greatly appreciated! Danil Smirnov

2 2

Please help: Mailaman3 -
by Jane Anara 06 Sep '20

06 Sep '20

Hello everyone, I hope my questions don't sound ridiculous. In my team, I have been tasked with moving our mailman installations from version 1:2.1 to the current version, mailman3. I followed the documentations online and installed all the components, created a Django project and configured settings.py and url.py. However, when I run the development server, I receive the following on the body of Postorius main page: Page not found This page either doesn't exist, or it moved somewhere else. Clicking on the "Lists" menu link, I receive the following: HTTP Error 404: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>example.com</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> <link rel="stylesheet" href="/static/postorius/libs/fonts/font-awesome/css/font-awesome.min.css" type="text/css" media="all" />    </head> <body> <nav class="navbar navbar-expand-md navbar-light bg-light navbar-default"> <div class="container"> <div class="navbar-header"> <button type="button" class="navbar-toggler collapsed" data-toggle="collapse" data-target="#header-nav" aria-expanded="false"> <span class="sr-only">Toggle navigation</span> <span class="fa fa-bars"></span> </button> <a class="navbar-brand" href="/mailman3/lists/"><span><img src="/static/postorius/img/mailman_logo_small_trans.png" alt="Mailman logo"/> Postorius</span></a> </div> <div class="collapse navbar-collapse" id="header-nav"> <ul class="nav navbar-nav mr-auto"> <li class="nav-item"><a href="/mailman3/lists/" class="nav-link"> <span class="fa fa-envelope"></span> Lists </a></li> <li class="nav-item"><a href="/archives/" class="nav-link"> <span class="fa fa-comment"></span> Archives </a></li> </ul> <ul class="nav navbar-nav navbar-right"> <li class="nav-item"><a class="nav-link" href="/accounts/login/?next=/3.1/lists"> <span class="fa fa-sign-in"></span> Login </a></li> <li class="nav-item"><a class="nav-link" href="/accounts/signup/?next=/3.1/lists"> <span class="fa fa-user-plus"></span> Sign Up </a></li> </ul> </div> </div> </nav> <div class="container" role="main"> <h1>Page not found</h1> <div class="alert alert-danger">This page either doesn't exist, or it moved somewhere else.</div> </div> <footer class="footer"> <div class="container"> <p class="text-center"> <a href="https://postorius.readthedocs.org">Postorius Documentation</a> • <a href="http://list.org">GNU Mailman</a> • Postorius Version 1.3.3 • Happy Mailman Day! </p> </div> </footer> <script src="/static/postorius/libs/jquery/jquery-1.11.3.min.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.11.0/umd/popper.min.js" integrity="sha384-b/U6ypiBEHpOf/4+1nzFpr53nxSS+GLCkfwBdFNTxtclqqenISfwAzpKaMNFNmj4" crossorigin="anonymous"></script> <script src="/static/postorius/libs/bootstrap/js/bootstrap.min.js"></script> <script src="/static/django-mailman3/js/main.js"></script> <script src="/static/postorius/js/script.js"></script> </body> </html> So far, the Postorious component is where there seem to be issues, all other link or component produce no errors thus far. Please advice on how I can troubleshoot this. I herein include the relevant sessions of my settings.py file and url.py which I have tweaked with various configurations to no avail. settings.py: # Application definition INSTALLED_APPS = [ # Apps added for mailman components 'hyperkitty', 'postorius', 'django_mailman3', 'mailmanclient', # Other useful apps 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', # end other useful apps 'django.contrib.sites', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.messages', 'django.contrib.staticfiles', ] url.py: urlpatterns = [ #Django admin path('admin/', admin.site.urls), path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), path('', include('django_mailman3.urls')), path('accounts/', include('allauth.urls')), #path('postorius', include('postorius.urls')), #path('lists/', list_index), path('search/', include('haystack.urls')), #url(r'^$', list_index), ] Note that when I uncomment the lines relating to list_index or use configurations similar to that on mailman-suit, I get: NameError: name 'list_index' is not defined. Looking forward to any help anyone can render. Thank you! Regards, Jane.

2 5

Struggling with log rotation in Docker context
by skenny＠scss.tcd.ie 05 Sep '20

05 Sep '20

I'm running Mailman 3 via maxking's Docker implementation, and had an incident recently where something went badly wrong, and the file uwsgi-error.log filled up. As a consequence, so did the file system where that file resides,and things ground to a halt. The file is visible on the Docker host as /opt/mailman/web/logs/uwsgi-error.log. I am unsure about how to rotate this file correctly. I could use logrotate on the host, but I can't locate any documentation that describes how to signal the relevant processes inside the mailman-web container. (Maybe this should be done within the container?) I'd be grateful for any good advice on this. Stephen

2 5

mailman procesing small amount of mail, then stop process them like 30 seconds, and then loop back
by mathias.bedu＠epitech.eu 04 Sep '20

04 Sep '20

Hi, I am currently trying to optimize my mailman installation, which is working. The only issue is that i see that mailman seems to process a few number of messages (around 50 each times), then stopping, and then processing few next messages. I spend quite some times searching for eventual parameters that could slow down. I precise that the machine itself is largely more powerful than what mailman is using. So my question is : could you give me some leads for potentials parameters or stuff like this that i could modify to optimize the installation ? Best regards, Mathias

2 2

Unsubscribe Notifications Clarification
by Brian Carpenter 03 Sep '20

03 Sep '20

I am trying to understand how Mailman 3 handles unsubscribe notifications. From my testing I see the following behavior: 1. If list member sends email to listname-leave@listname, an unsubscribe notification is sent to both list owner and list member if list settings have them enabled. 2. If list list member is a registered user of Postorius and he uses Postorius to unsubscribe, then no notification is sent out to either list owner or list member, even if list settings has unsubscribe notifications enabled. Is this correct? Brian

2 2

adding imprint / private policy link to postorius
by Thomas Stein 03 Sep '20

03 Sep '20

Hello one and all. Is it possible to add an imprint link to the postorius start page? I guess it is, but it would be nice if someone could me point to the right direction / documentation. Something like they have: https://lists.openrailwaymap.org/mailman3/postorius/lists/ cheers, t.

2 2

Timeout in Postorius when trying to approve or reject moderated messages
by Sebastian Hagedorn 30 Aug '20

30 Aug '20

Hi, I just set up a new Mailman 3 Suite installation (GNU Mailman 3.3.1 (Tom Sawyer)) on CentOS 7 using the virtualenv installation guide: https://docs.mailman3.org/en/latest/install/virtualenv.html I encountered a few issues, but I was able to resolve all of them, I think. All three components of the suite are up and running. The backend is a MariaDB database, the frontend is Apache with mod_wsgi. I can send messages to the server, and they are delivered to list members. One thing that I can't figure out is why I can't approve or reject messages that are held for moderation. In case it matters, I'm trying to moderate the list using the "root" account. Discarding works, but when I try to either accept or reject a message, there is a timeout. I can't find anything in mailman.log, mailmansuite.log or even /var/log/httpd/access_log. I managed to reject and approve messages manually using mailmanclient and the REST API, so the issue appears to be somewhere between Postorius 1.3.3 and mailmancore. Any ideas? -- .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.

4 6

Throttle outgoing emails to a certain rate?
by arvid.teichtmann＠gmx.de 21 Aug '20

21 Aug '20

Is there a possibility to throttle the sending of outgoing emails to a certain rate, e.g. 100 emails per hour, or to split them up into corresponding chunks? I run Mailman 2.1.33 on a hosted server and the provider only allows me to send a maximum of 100 emails per hour. The excess emails are also simply discarded and the sender and list administrator get a bunch of error emails. This is very annoying, especially because I didn't know about it and the problem only now occurs occasionally during operation... ;-( Thanks for all hints.

3 2

Spam sign ups
by Seth Seeger 21 Aug '20

21 Aug '20

Hello all, I've suddenly started getting a slow but steady stream of fake sign ups. They fail because I'm getting a bounce back from the mail host saying that the email address they signed up with doesn't exist. I know this was asked a while back on this list, but I'm hoping there might be an update? Any way to add an am-I-human test to the sign up? Thanks, Seth

2 1

mailman not starting, status is active (exited)
by Ricardo Kleemann 19 Aug '20

19 Aug '20

Hi, After quite a long time with no issues, I’ve started having a problem where mailman won’t start and I don’t see any clear error message I’m running on Ubuntu, not sure which mailman version (forgot how to determine). Here is the status info sudo systemctl status mailman ● mailman.service - LSB: Mailman Master Queue Runner Loaded: loaded (/etc/init.d/mailman; generated) Active: active (exited) since Wed 2020-08-19 07:38:59 PDT; 2h 46min ago Docs: man:systemd-sysv-generator(8) Process: 2351 ExecStop=/etc/init.d/mailman stop (code=exited, status=0/SUCCESS) Process: 2386 ExecStart=/etc/init.d/mailman start (code=exited, status=0/SUCCESS) Aug 19 07:38:59 relay1 systemd[1]: Starting LSB: Mailman Master Queue Runner... Aug 19 07:38:59 relay1 systemd[1]: Started LSB: Mailman Master Queue Runner Any ideas? thanks Ricardo

3 2