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.
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
is there a tutorial or some examples for using the mailman shell? Is there detailed documentation on it?
Anything I try to do such as the following fails:
$ mailman shell
Welcome to the GNU Mailman shell
>>> command('mailman shell --details')
Traceback (most recent call last):
File "<console>", line 1, in <module>
NameError: name 'command' is not defined
I execute the shell as user mailman and from within the same venv that all the programs run under.
I haven't found out where I could choose or edit default list values
(when creating new list).
For example I would like that all new lists would be with *private
archive* (and change this when it is needed).
This is great that I can choose not to advertise list in Index (which I
can choose from list creation interface) but I would like to choose
other options too.
Right now only solution is to create list and then choose Archiving and
then select "private archives".
Another thing is that I would like to choose default subscription policy
If anyone has encountered this problem, let me know!
All the best
I am in the process to migrate an old 2.1 installation to 3.2.1 (Debian 10.1)
Following the 2.1 to 3 docs:
- Create a new list
- Use the import21 command
The command runs successfully (at least no errors in stdout). There is a problem when sending an email to the newly imported list, the message never get send to the members. I do get moderation emails, and if i do a mass subscribe, the welcome email is received by the new members.
In a fresh 3 new list (not imported from 2.1) this does not happen.
I already tried looking for clues in the logs
But i haven't seen anything useful yet.
Any hints on this?
I'm running a Mailman 3.1.0 installation on a CentOS 7 machine. Using
I do have problems with some lists occasionally going into some kind of
shunt mode, where alla mails sent to them gets shunted. In the Mailman
log I get entries for each shunted email:
Mar 17 11:54:11 2017 (6217) Uncaught runner exception: Multiple rows
were found for one_or_none()
Mar 17 11:54:11 2017 (6217) Traceback (most recent call last):
File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line
171, in _one_iteration
File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line
264, in _process_one_file
keepqueued = self._dispose(mlist, msg, msgdata)
line 37, in _dispose
process(mlist, msg, msgdata, pipeline)
line 53, in process
handler.process(mlist, msg, msgdata)
line 121, in process
process(mlist, msg, msgdata)
line 70, in process
archiver_set = IListArchiverSet(mlist)
line 33, in __call__
return self.__implementation(*args, **kw)
File "/usr/lib/python3.4/site-packages/zope/component/_api.py", line
156, in adapter_hook
return sitemanager.queryAdapter(object, interface, name, default)
line 348, in queryAdapter
return self.adapters.queryAdapter(object, interface, name, default)
85, in wrapper
return function(args, config.db.store, *args[1:], **kws)
line 607, in __init__
ListArchiver.name == archiver_name).one_or_none()
line 2733, in one_or_none
"Multiple rows were found for one_or_none()")
sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for
Mar 17 11:54:11 2017 (6217) SHUNTING:
And so far my Google-fu hasn't been good enough to give me any useful
answers to why this happens. If I dump one of the pickles using qfile I
cannot see any complaints.
Most of the times, if I remove and recreate a failing list and run
unshunt the shunted emails get processed and sent.
Anyone seen something similar?
Anders Nilsson, Ph.D. <andersn(a)control.lth.se>
Dep. of Automatic Control, Lund University
Phone: +46 (0)46 222 87 94, Fax: +46 (0)46 13 81 18
Mob: +46 (0)703 22 57 67
Hope everyone had a great weekend!
I am pleased to announce new set of releases:
- Postorius 1.3.1
- Django-mailman3 1.3.1
- Hyperkitty 1.3.1
These are all bugfix releases and include several fixes each. The full changelogs are available at:
- Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1)
- Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1)
Most notable fixes include a fix for PostgeSQL support in Hyperkitty, ability to delete a MailingList in Hyperkitty and list settings changes are immediately reflected in Hyperkitty (like making a List private).
It also includes support for Python 3.8 and Django 3.0 in Postorius and Django-maialman3. Hyperkitty doesn't yet support either of them due to some dependencies not yet supporting Django 3.0 and a bug in Python 3.8.0 causing a test case failure. I hope that we are able to support the latest and greatest as soon as possible, I am excited to be able to play with Django's aync capabilities.
Finally, since our i18n workflow has been setup, we have lots of new translations coming in. This release also includes more parts of Postorius being translatable, including section headers. I am really happy to see Mailman 3 move closer to Mailman 2 in terms of i18n. If you want to help us improve the coverage, head on to Weblate.
All the releases are available on PyPI, as usual!
 Fun Fact: The bug was due to a code that I contributed ;-). It is now fixed and will be soon out with Python 3.8.1 sometime this month.
Abhilash Raj (maxking)
i start by saying that i browsed through the archives in here for the past three days, and re-read the mailman 3 docs several times, as well the postfix docs.
the thread closest to my problem is this one https://firstname.lastname@example.org/thread/… ; i was not sure if it was good to re-open though.
i have a postfix + dovecot setup using the "separate domains and non-unix accounts".
postfix/smtpd: NOQUEUE: reject: RCPT from wout1-smtp.messagingengine.com[184.108.40.206]: 550 5.1.1 <list-name(a)domain.com>: Recipient address rejected: User unknown; from=<some(a)email.com> to=<list-name(a)domain.com> proto=ESMTP helo=<wout1-smtp.messagingengine.com>
postfix main.cf relevant portion for virtual users
# deliver mail for virtual users to Dovecot's LMTP socket
virtual_transport = lmtp:unix:private/dovecot-lmtp
# setup virtual domains and non-unix accounts
virtual_mailbox_domains = /etc/postfix/vhosts
virtual_mailbox_base = /var/spool/vmail
virtual_mailbox_maps = hash:/etc/postfix/vmaps
virtual_uid_maps = static:1001
virtual_gid_maps = static:1001
virtual_alias_maps = hash:/etc/postfix/valias
postfix `main.cf` mailman settings
transport_maps = regexp:/opt/mailman/var/data/postfix_lmtp
local_recipient_maps = regexp:/opt/mailman/var/data/postfix_lmtp
relay_domains = regexp:/opt/mailman/var/data/postfix_domains
question: i tried to add the `alias_domain` to mailman using Mailman Core REST APIs because I read about https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#unusual-… ; entering the mailman console and doing `dump_json('http://localhost:9001/3.0/domains/example.com/lists')` was giving me error that `dump_json` is not an available module.
is that the way to go? should I add a an `alias_domain` to Mailman in order for it to output a `postfix_vmap` when doing `mailman aliases`? and then add it to postfix `main.cf` like so
virtual_alias_maps = hash:/etc/postfix/valias, regexp:/opt/mailman/var/data//postfix_vmap
or do you suggest as a simple viable solution to create a new unix account and setup postfix to use local domains?
thanks and hopefully my confusion arose from reading all these threads will dissipate soon!
I'm new to MM3. I installed version 3.1.1 on Ubuntu 18.04. All looks
fine. But i miss the setting "pass_mime_types" at content filtering.
Also i don't find the settings for bounce processing. Are these features
no longer supported at version 3.1.1?
Thanks for your information!