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 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'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
It seems, that mailman bounces the bounces, so that the list-owner never
postfix/smtpd: connect from out04.smtpout.orange.fr[18.104.22.168]
postfix/smtpd: 879D6F12E8: client=out04.smtpout.orange.fr[22.214.171.124]
postfix/cleanup: 879D6F12E8: message-id=<>
postfix/qmgr: 879D6F12E8: from=<>, size=4048, nrcpt=1 (queue active)
postfix/smtpd: disconnect from out04.smtpout.orange.fr[126.96.36.199] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
postfix/lmtp: 879D6F12E8: to=<test-bounces(a)my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command))
postfix/qmgr: 879D6F12E8: removed
What could I do please, to get the bounces? I would like to use VERP to
identify wrong addresses...
TIA for any hints,
Is it possible for a list admin to modify the welcome message for a list via Postorius? Is the process:
1. Log into Postorious
2. Click on the Templates tab.
3. Select New Template.
4. Select "The notice sent to a member when they are subscribed to the mailing list"
5. Add your text and click the save button.
Is the correct process? I am using the latest Docker release of Mailman 3.
i migrated to a new host last night and i've been getting this error from a cronjob
mail every minute. anyone have any ideas what would cause this?
ERROR 2019-04-17 14:26:33,056 27205 hyperkitty.lib.utils Failed to update the fulltext index: ord() expected a character, but string of length 0 found
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/hyperkitty/lib/utils.py", line 186, in run_with_lock
File "/usr/lib/python2.7/dist-packages/hyperkitty/search_indexes.py", line 87, in update_index
File "/usr/lib/python2.7/dist-packages/haystack/management/commands/update_index.py", line 276, in update_backend
File "/usr/lib/python2.7/dist-packages/haystack/management/commands/update_index.py", line 97, in do_update
backend.update(index, current_qs, commit=commit)
File "/usr/lib/python2.7/dist-packages/haystack/backends/whoosh_backend.py", line 178, in update
File "/usr/lib/python2.7/dist-packages/haystack/backends/whoosh_backend.py", line 126, in setup
self.index = self.storage.open_index(schema=self.schema)
File "/usr/lib/python2.7/dist-packages/whoosh/filedb/filestore.py", line 176, in open_index
return indexclass(self, schema=schema, indexname=indexname)
File "/usr/lib/python2.7/dist-packages/whoosh/index.py", line 421, in __init__
TOC.read(self.storage, self.indexname, schema=self._schema)
File "/usr/lib/python2.7/dist-packages/whoosh/index.py", line 632, in read
File "/usr/lib/python2.7/dist-packages/whoosh/index.py", line 626, in check_size
sz = stream.read_varint()
File "/usr/lib/python2.7/dist-packages/whoosh/filedb/structfile.py", line 191, in read_varint
File "/usr/lib/python2.7/dist-packages/whoosh/util/varints.py", line 102, in read_varint
b = ord(readfn(1))
im trying to setup mailman and have an issue:
first my environment:
- I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/
- I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/
I got almost everything working (with some configuration modifications, see other mail). The only thing which doesn’t work is conformation mails, they are rejected:
In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp.
Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps?
For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/
Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)?
Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?)
Thanks and greetings,
I have read documentation, but still have stupid questions, could You please help, because I can't make it working. I do not understand something important. I have no experience with python at all. I have mailman 3, python 3.5 in my debian OS system, and additional packages like uwsgi and ect. using https://buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman… about till chapter 6. I understand mailman suite has hyperkitty already. But I am not sure about:
1. Does mailman-suite have hyper-kitty inside? Because if I run $python manage.py runserver - it runs. In installed it under dedicated OS user home and fonfigured to run.
I can create lists, event add lists to hyperkitty page using: $django-admin runjob new_lists_from_mailman list server sends messages to list members as well. But nothing happens more. No emails come to hyperkitty, arciver log 0 size.
$ python manage.py runjobs -l shows the lists of the jobs, so seems nothing to add.
Except uwsgi.ini, I have only 2 configuration files in mailman-suite project directory: settings.py and mailman.cfg So I do not understand what did I configured badly.
2. If I (using Postorius web interface) add footer template to my list under regular message, something strange happens. Mailman stops to send messages for list members. No any entries in the logs. Just Mailman log writes: "unable to connect localhost port 25" and no more explanation. If I delete list's footer template (web interface), mailman starts working again. What is bad here? How to add custom footer? In mailman 2 if was working so good and was easy to setup.