Dear Mailman 3 Users,
We have launched Affinity and Empathy and they now are part of our
shared and cloud Mailman 3 hosting services. Affinity replaces Postorius
and Empathy replaces Hyperkitty.
You can read more at https://mailmanhost.com
Please email me off-list if you have any questions.
I have been trying to set up a mailing list that is mostly for message
distribution, so there is a single sender of messages and multiple
receivers, but the receivers are moderated. I wouldn't mind receiver
messages being explicitly rejected but that's not an issue for now.
I looked around the interface and decided to set up the sender as a
non-member, as that appeared to permit them to be "special" and outside
of the normal access rules for the list. Before I did that I could send
a message from this sender and that would be sent to me as list owner
for moderation, so both incoming (from my mailserver) and outgoing (to
it) can be completed.
However, with a non-member who is auto-accepted the message is passed
from my mailserver to mailman and then disappears. I cannot find
anything in the logs to indicate what happened next. I have tried
setting the default non-member policy to both 'hold' and 'default' with
no change in that behaviour. The logs for the mailserver show the
message being sent to mailman; mailman's "smtp.log" shows an LMTP
message being received ok, and then nothing.
Any ideas how to find out what is going on? I can share config if that
helps but not sure what would be useful.
As a side-issue, at one point I added a regex matching the sender
address to the acceptable members list, but find that I cannot now
delete it (using postorius): If I delete the field and Save, it returns
on page refresh.
Software Manager & Engineer
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,
File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266,
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,
if link.rule.check(mlist, msg, msgdata):
File "/usr/lib/python3.8/site-packages/mailman/rules/dmarc.py", line 314,
if maybe_mitigate(mlist, address):
File "/usr/lib/python3.8/site-packages/mailman/rules/dmarc.py", line 286,
answer = is_reject_or_quarantine(
File "/usr/lib/python3.8/site-packages/mailman/rules/dmarc.py", line 217,
for record in txt_rec.items.strings)
Sep 06 22:41:32 2020 (27) SHUNTING:
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!
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" /> <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries --> <!-- WARNING: Respond.js doesn't work if you view the page via file:// --> <!--[if lt IE 9]> <script src="/static/postorius/libs/html5shiv/html5shiv.min.js"></script> <script src="/static/postorius/libs/respond/respond.min.js"></script> <![endif]--> </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.
# Application definition
INSTALLED_APPS = [
# Apps added for mailman components
# Other useful apps
# end other useful apps
urlpatterns = [
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.
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.
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 ?
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?