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
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 am making a serious attempt at installing Mailman 3 using docker. I have a CentOS 7 server setup via Linode. I am using the following documentation to setup a Mailman 3 server:
I have Docker, Postfix, and Nginx installed and working fine. The installation of the Mailman 3 container went fine. However I am getting the following error when I go to test Posterius via shell:
curl: (7) Failed connect to 172.19.199.3:8000; Connection refused
I assume this has something to do with uwsgi which I have no experience with.
Appreciate any assistance with getting Mailman 3 up and running. Thanks!
How can one do this? Raw database access gets you involved in all the usual foreign key constraints.
I don't know how to make use of this information:
After a very large import of decades of data, I need to delete just one wrong mail that is corrupt. I think it is a valid case. I could run the import again after fixing the import mbox, but it takes many hours to load.
I have been recently working on adding rich text support through markdown in Hyperkitty so that emails can be made easier to read. The core design idea in my mind when working on this was building something that doesn't bother writers of plain text emails too much, but allows people to write emails in markdown.
The supported syntax is limited Markdown, for example:
Hyperkitty's Markdown Syntax
- List items are supported
- Even nested ones
- Headers with `#` aren't supported, mostly due to their widespread use as comments in code shared on mailing lists.
- You can **emphasize** text and _itcalize_ them too
- Block code and `inline code` works.
- URLs work like they usually do.
- Images _do work_, but are disabled by default because of their potential for tracking users. They need to be enabled by administrators through a configuration flag.
While text intentionally written for Markdown rending looks pretty good, plain text sometimes isn't as good. I have applied my branch on both the Mailman installations for these two lists (mail.python.org & lists.mailman3.org).
Any feedback or bug reports on weird looking stuff is welcome here or directly [on my PR]
Abhilash Raj (maxking)