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.
Since 2005, our organization has been running a customized version of
Mailman 2 with extensions that meet our particular needs. The main
novelty is support for /fixed subscription lists/, in which the list
members are predetermined (corresponding to a "committee"). Fixed list
subscribers are not offered the opportunity to unsubscribe, nor can
others add themselves to the list. A further enhancement is /hybrid
lists/ which, for example, have both a fixed and opt-in part. (This is
implemented as a fixed list residing within an opt-in one in a way which
is transparent to users). Our customizations consist of code
adjustments (patches) to 23 files.
We are considering moving to Mailman 3 and would like to do this in a
way which makes it possible to periodically upgrade our installation to
the newest Mailman version, without clobbering our customizations.
Thus, I do not think that installing via "pip" is the right approach for
us. While I'm relatively new to git and GitLab, they seem to be ideally
suited to this situation. If I understand the developer documentation
correctly, I start out by creating a "fork" and can later "fetch"
changes from the master branch and "rebase" to bring them into our branch.
I would welcome comments on what we are doing. I also wonder whether
others might be interested in support for "fixed lists", if they are
done in a way which can be "contributed" back into Mailman.
I extend our "thank you" to the developers of Mailman who have provided
the robust system which has served us well for 15 years and provides the
possibility to extend this into the future.
Manager, Electronic Services
Canadian Mathematical Society
Tel: +1 (613) 733-2662 ext. 799
Please consider the environment.
[cms web link] <https://cms.math.ca/>
Chef, services électroniques
Société mathématique du Canada
Tél : +1 (613) 733-2662 poste 799
Considérez svp l'environnement.
I am importing old archives mbox files from Mailman2. I have fixed the
archive mail address to reflect the address of the destination import.
These are the steps:
1. sed 's|oldlist@oldexample\.org|testlist@example\.org|g' mbox >
2. /opt/mailman/mm/bin/django-admin hyperkitty_import --since
01/01/1990 -l testlist(a)example.org mbox.testlist
The output of the last command is:
Computing thread structure
Synchronizing properties with Mailman
Warming up cache
The full-text search index is not updated for this list. It will
not be updated by the 'minutely' incremental update job. \
To update the index for this list, run the 'manage.py
update_index_one_list testlist(a)example.org' command.
The result is that the e-mail's are imported but not indexed.
To finalize this process I am seeking manage.py that will execute the
update index command.
I am on a Debian 10 with Mailman3 in /opt.
None of these python files can execute the needed command.
What can I do to get the newly imported posts indexed?
After mass subscribing with these settings:
Pre confirm: Yes, Pre approved: Yes, Pre Verified (sic): No
the addresses appeared in the list's 'Pending user confirmation' list. They were pre-confirmed.
The addresses did not appear in the Django Admin's non-verified addresses list. They were not verified.
Also why does Postorius lists just 'Pending Approval' and 'Pending Confirmation' but not 'Pending Verification'?
Our shop is an educational shop and left mailman many years ago for Sympa because of features in Sympa not in mailman. Currently Sympa is showing its age, and is relying on perl modules that have been EOL's and the Sympa community has not discussed (within in ear-shot of me at least) what to do about it.
We found that we are not using the extra features Sympa provides anymore and with MM3 already dockerized it seems that MM3 is a much better fit for our organization for the foreseeable future.
So I got a dockerized setup up and running in a test environment and am pleased with the results except for now I have to start thinking about migration from Sympa to MM3.
The API is useful in this effort as there are python wrappers already done and I didn't have any trouble scripting list creation with the API tools to migrate list owners, moderators and users.
Now for the question/hard part. Migrating list archives.
In Sympa the list archive is just a maildir format directory structure reflecting month/year. In MM3 the Archive is stored in the db with attributes that are likely only available as the message is processed.
I'd really rather not loose the archive data if I can help it. Does anyone have any thoughts on how I could perhaps import this?
Dear Mailman 3 users,
Currently we are hosting the website  and mailing list  of our
free software project with a shared hosting plan of a webhosting
company. As such there is no dedicated server, but we do have SSH
access (as a regular user) to the shared server. The mailing list
software (Mailman 2) is administrated separately by our hoster on
a dedicated machine. We are rather happy with this setup: we pay about
10 USD per month and have only little administration work to do.
The only problem is that our list runs on Mailman 2. We would like to
move to Mailman 3, but this does not seem to be that simple. Perhaps
someone here would be so kind to give us advice?
The number of (shared) hosters who offer Mailman 3 seems to be very
limited . Would it be a good idea to book a virtual private server
(VPS) somewhere, that runs, say, Debian, and simply install Mailman
3 through the distribution’s package system? I’m already running
a small personal box with nginx on it, and this is very little work, but
running Mailman would require sending out up to a few thousand email
messages per day (our list has a few hundred subscribers). Is this
something that one is commonly allowed to do on a VPS system? Most VPS
offers that I see are silent about mail.
If we setup such a system, can we assume that it will silently operate
without causing much administration work most of the time (like my nginx
server)? Or is maintaining a Mailman 3 server a significant burden (
seems to imply that)? If yes, are you aware of organizations that
propose Mailman 3 hosting for open source projects? Python.org seems to
host some lists for third party projects, but otherwise I haven’t seen