I came across this really useful guide (posted to the list earlier). It has all gone really well and mailman 3 is installed. However, I have an issue, when I go to login using Postorius, I get the login page when I enter my credentials the page appears to hang and eventually goes to a Error 500 page. This totally hangs all of the mailman 3 web interface (but not apache). I then have to reboot the server to even get back to the login page.
Any tips please?
So our mailman got stuck again, but I did follow your advise. Here's
what I've found:
On 3/29/19 2:58 PM, Mark Sapiro wrote:
> On 3/29/19 2:28 PM, Dmitry Makovey wrote:
>> I've had encountered this situation now twice: mail is being stuck in
>> "out" queue and nothing in the logs indicates the issue. Is there a way
>> to ask mailman-core politely to attempt delivery (perhaps with increased
>> debugging in the logs) *without* restarting the core (which does solve
>> *this* problem but creates other problems, like availability of the
>> mailman as a whole)
> Is the "out" runner running?
# docker top mailman-core | grep -F out:
100 21681 13215 0
Mar28 ? 01:14:16
/usr/local/bin/python /usr/local/bin/runner --runner=out:0:1 -C
> ps -fwwA |grep runner=out
> If not, you should be able to start it as the Mailman user with a
> command like
> /path/to/python3 /path/to/mailman/bin/runner -C /path/to/mailman.cfg
> See 'ps -fwwA|grep runner' for examples
> If the out runner is running, is there a file named *.bak along with all
> the *.pck files in queue/out/
there is one, yes:
# ls -l /srv/mail/mailman/core/var/queue/out/*.bak
-rw-rw---- 1 100 65533 21512 Apr 14 19:45
what does it indicate and what should my steps be to resolve this (other
than restarting queues)?
> And if it's not, is there anything in Mailman's logs to indicate why it
> Also, 'mailman restart' should only take a matter of seconds, but if the
> out runner is running but not processing its queue, I think sending it a
> SIGINT should restart it.
SIGINT killed the process allright, but it didn't auto-respawn. I ended
up spawning it with:
/usr/local/bin/python /usr/local/bin/runner --runner=out:0:1 -C
but soon realized it doesn't go to background nicely so I've nohup'ed it
in the end. but it did solve my problem.
Sr System and DevOps Engineer SoM IRT
I have successfully setup a second domain with my Mailman3 setup. I also created a list using the second domain. So I have two domains with one list each. The issue I see at this point is all of the lists are shown via Postorius regardless of the list domain used. Is it possible to have only the lists to show that are part of the domain being used to access? For example:
Only listnames(a)domaina.com show up.
Only listnames(a)domainb.com show up.
Right now both domaina AND domainb lists showup regardless of the domain being used to access Postorius. The same goes for Hyperkitty as well.
Now I am seeing this in the log every few seconds:
12:12:29 [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes]
12:12:29 [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. : Traceback (most recent call last):
File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_q-1.0.1-py3.7.egg/django_q/cluster.py", line 377, in worker
res = f(*task['args'], **task['kwargs'])
File "/opt/mailman/mm/venv/lib/python3.7/site-packages/HyperKitty-1.2.3-py3.7.egg/hyperkitty/tasks.py", line 189, in _rebuild_thread_cache_votes
thread = Thread.objects.get(id=thread_id)
File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-2.1.9-py3.7.egg/django/db/models/manager.py", line 82, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-2.1.9-py3.7.egg/django/db/models/query.py", line 399, in get
hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist.
Any help? How do I identify the thread in question?
I imported an archive from a Listserv list, processed into something resembling mbox format (which I now understand not to be a standard at all) and have about 100,000 messages there. I am having a lot of trouble with these sort of errors, as you will see from my flurry of posts recently.
Yes, I am running all the jobs.
Our MailMan3 server is extremely slow and when trying to list or export members for a larger list it is throwing 'Mailman REST API not available. Please start Mailman core'. In Mailman core logs I am seeing
 [CRITICAL] WORKER TIMEOUT (pid:40)
 [INFO] Booting worker with pid: 43
Has anyone seen this issue? Is there any way to increase 'timeouts'?
Thanks for any help!
16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/somelist(a)somelist.com/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com HTTP/1.1" 200 347 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com/roster/owner HTTP/1.1" 200 634 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:01 +0000] "GET /3.1/lists/list.somelist.com/roster/moderator HTTP/1.1" 200 638 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:01 +0000] "GET /3.1/lists/somelist(a)somelist.com/config HTTP/1.1" 200 2257 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:05 +0000] "GET /3.1/lists/list.somelist.com/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:08 +0000] "GET /3.1/lists/list.somelist.com/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:08 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:10 +0000] "GET /3.1/lists/list.somelist.com/member/somelist@somelist HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:16 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:19 +0000] "GET /3.1/lists/somelist(a)somelist.com/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0"
[16/Jan/2020:16:56:26 +0000] "GET /3.1/lists/list.somelist.com HTTP/1.1" 200 347 "-" "GNU Mailman REST client v3.3.0"
[2020-01-16 16:56:58 +0000]  [CRITICAL] WORKER TIMEOUT (pid:40)
[2020-01-16 16:57:00 +0000]  [INFO] Booting worker with pid: 43
DISCLAIMER: The information contained in this message is privileged and confidential. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the message and delete/destroy any copy of this message. Information in this message that does not relate to the official business of the firm shall be understood as neither given nor endorsed by it.
Does Mailman 3 have a feature/script/function that corresponds with the sync_members script that Mailman 2 has? I have a Mailman 3 client that wants to automate the process of keeping a MM3 list synchronized with a file on the server.
Since we do run roughly 40 mailinglists on mailman3, the
python3 /usr/share/mailman3-web/manage.py runjobs minutely uses 1 CPU
core 100% all the time.
Any idea howto see why?
debian mailma3n-full package 3.2.1-1
Mailman Core Version GNU Mailman 3.2.1 (La Villa Strangiato)
Mailman Core API Version 3.0
Mailman Core Python Version 3.7.3 (default, Apr 3 2019, 05:39:12) [GCC
TU Graz, Institut für ComputerGraphik & WissensVisualisierung
Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at
Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723
I don't understand how to set up an "announce only" mailing list using
Postorius Version 1.2.4.
What I do is the following:
- Click on "Create New List"
- From "List Style", select "Announce only mailing list style."
- Fill all other fields in the form
- Click "Create list"
At this point people can subscribe to the newly created announce mailing
list. If they add themselves they end up in "List Members", and if they
email the announce mailing list, their email is relayed to all other
members, just like a normal mailing list :/
Moreover, subscribers get this message, inviting them to post to the
announce only mailing list:
> Welcome to the "Test-announce" mailing list!
> To post to this list, send your email to:
Of course, I want to keep this mailing list "read only" for members, and
I want only selected people to post to that mailing list.
Any idea on how to achieve that?
I came to know that the held messages can be restricted to be
processed after a specific no of days or can be discard after some days
using the parameter *max_days_to_hold*.
But I could see that parameter value configurable on MM2 GUI
interface in General Options but I don't see the same on the MM3 GUI
Could you please help me if I am missing something?
Thanks & Regards,
On 1/30/20 8:24 AM, Bala Mutyam wrote:
> Hi Mark,
> Thanks for the update and I managed to resolve the errors on the UI.
> I have 2 more questions about the mailman3.
> 1) how to create Mailing Lists?
You can create lists with the `mailman create` command lint tool or via
Postorius as a superuser.
> 2) super user login is not working even with correct login credentials and giving me - The username and/or password you specified are not correct.
How did you create the super user? You should do it with the django
admin createsuperuser command.
> 3) Password Reset Email urls and email confirmation web pages giving me - This site can't be reached error.
If this is an error from your browser, there is something wrong with the
host portion of the URL.
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan