July 2019 - Mailman-users - lists.mailman3.org

Exim, Mailman3 and missing Message-ID:
by Robert Lister July 29, 2019

July 29, 2019

Just a note that may help some people. After a bit of a learning curve, managed to get Mailman3 working in Debian 10 using the Debian package. I have mailman3-full + exim4 + apache2 setup: I did quite a lot of testing and getting it working, then when all seemed well, declared success and made it live. As (bad) luck would have it, the very first real message bounced: :-( 2019-07-25 20:53:09 1hqjnY-0005ms-RD <= xxxxxxx(a)ntlworld.com H=cloudi.spamtitan.com [52.26.55.167] P=esmtps X=TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no S=7854 DKIM=ntlworld.com 2019-07-25 20:53:09 1hqjnY-0005ms-RD ** mylist(a)lentil.org R=mailman3_router T=mailman3_t H=127.0.0.1 [127.0.0.1]: LMTP error after DATA: 550 No Message-ID header provided 2019-07-25 20:53:09 1hqjnZ-0005mx-3F <= <> R=1hqjnY-0005ms-RD U=Debian-exim P=local S=9222 The user forwarded me the bounce, which contained the original message and headers, and indeed the original message did not contain a Message-ID: header. (Oddly, his message to me reporting the error using the same mail client DID contain a Message-ID: header.) Mail client: X-Mailer: Microsoft Outlook 16.0 So it seems in certain circumstances, Outlook doesn't put a Message-ID: header in its messages. The change from Mailman2.x to Mailman3 means it's now using LMTP to deliver to mailman instead of a local submission seems to have exposed this issue. Exim tries to be helpful for "locally submitted" messages: <https://www.exim.org/exim-html-current/doc/html/spec_html/ch-message_proces…> "12. The Message-ID: header line If a locally-generated or submission-mode incoming message does not contain a Message-ID: or Resent-Message-ID: header line, and the suppress_local_fixups control is not set, Exim adds a suitable header line to the message. If there are any Resent-: headers in the message, it creates Resent-Message-ID:. The id is constructed from Exim's internal message id, preceded by the letter E to ensure it starts with a letter, and followed by @ and the primary host name." However: "Note: Messages received over TCP/IP on the loopback interface (127.0.0.1 or ::1) are not considered to be locally-originated. Exim does not treat the loopback interface specially in any way." Therefore, Mailman3 using LMTP means exim will NOT "fix up" this problem before mailman3 receives the message. My solution for now (apart from telling people not to use old broken Outlook!) is to modify the exim mailman3_transport so that any message with a missing Message-ID: will have one generated by exim before it's passed to LMTP. This reproduces the same behaviour exim uses for locally submitted messages. (headers_remove ensures that we end up only with one Message-ID: header and not two, then we put back either the original Message-ID, or if that's not there, use Exim's ID to generate a new Message-ID header.) Here's an updated version of the example at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#exim # /etc/exim4/conf.d/main/25_mm3_macros # The colon-separated list of domains served by Mailman. domainlist mm_domains=list.example.net MM3_LMTP_PORT=8024 # MM3_HOME must be set to mailman's var directory, wherever it is # according to your installation. # debian default is /var/lib/mailman3 MM3_HOME=/opt/mailman/var MM3_UID=list MM3_GID=list ################################################################ # The configuration below is boilerplate: # you should not need to change it. # The path to the list receipt (used as the required file when # matching list addresses) MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} # /etc/exim4/conf.d/router/455_mm3_router mailman3_router: driver = accept domains = +mm_domains require_files = MM3_LISTCHK local_part_suffix_optional local_part_suffix = \ -bounces : -bounces+* : \ -confirm : -confirm+* : \ -join : -leave : \ -owner : -request : \ -subscribe : -unsubscribe transport = mailman3_transport # /etc/exim4/conf.d/transport/55_mm3_transport mailman3_transport: driver = smtp protocol = lmtp allow_localhost hosts = localhost port = MM3_LMTP_PORT rcpt_include_affixes = true mailman3_transport: driver = smtp protocol = lmtp allow_localhost hosts = localhost port = MM3_LMTP_PORT rcpt_include_affixes = true headers_remove = message-id headers_add = "Message-ID: ${if def:header_message-id:{$h_message-id:}{<E${message_exim_id}@${qualify_domain}>}}"

4 6

import21 / hyperkitty_import: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()
by Christian Schwarz July 29, 2019

July 29, 2019

Hi all, after upgrading from Mailman 2.1 to Mailman 3 (Debian Buster), one (but not all) of the lists causes the following exception. The list was imported using import21 and archives were imported using manage.py hyperkitty_import. Jul 29 10:19:43 2019 (761) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.7/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 216, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ File "falcon/api.py", line 189, in falcon.api.API.__call__ File "/usr/lib/python3/dist-packages/mailman/rest/lists.py", line 402, in on_get archiver_set = IListArchiverSet(self._mlist) File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 135, in __call__ adapter = self.__adapt__(obj) File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 151, in __adapt__ adapter = hook(self, obj) File "/usr/lib/python3/dist-packages/zope/component/_api.py", line 156, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/registry.py", line 348, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 353, in queryAdapter return self.adapter_hook(provided, object, name, default) File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 363, in adapter_hook result = factory(object) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 607, in __init__ ListArchiver.name == archiver_name).one_or_none() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3017, in one_or_none "Multiple rows were found for one_or_none()" sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() I got that from the log file /var/log/mailman3/mailman.log. The Installation also sends emails to me, indicating some kind of exception in the except branch (see below). What can I do to debug this? Thanks, Christian --------------------------------------------- Internal Server Error: /postorius/lists/LISTNAMEREDACTED/ KeyError at /postorius/lists/LISTNAMEREDACTED/ 'file' Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 41. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 187. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in view 68. return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/generic.py" in dispatch 65. return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in dispatch 88. return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py" in get 252. 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 File "/usr/lib/python3.7/_collections_abc.py" in __contains__ 666. self[key] File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in __getitem__ 151. return self._get(key) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in _get 90. return self.rest_data[key] File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in rest_data 76. response, content = self._connection.call(self._url) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call 99. raise HTTPError(url, response.status, content, response, None) During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 41. response = get_response(request) File "/usr/lib/python3/dist-packages/postorius/middleware.py" in __call__ 39. return self.get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 43. response = response_for_exception(request, exc) File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in response_for_exception 93. response = handle_uncaught_exception(request, get_resolver(get_urlconf()), sys.exc_info()) File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in handle_uncaught_exception 135. extra={'status_code': 500, 'request': request}, File "/usr/lib/python3.7/logging/__init__.py" in error 1412. self._log(ERROR, msg, args, **kwargs) File "/usr/lib/python3.7/logging/__init__.py" in _log 1519. self.handle(record) File "/usr/lib/python3.7/logging/__init__.py" in handle 1529. self.callHandlers(record) File "/usr/lib/python3.7/logging/__init__.py" in callHandlers 1591. hdlr.handle(record) File "/usr/lib/python3.7/logging/__init__.py" in handle 905. self.emit(record) File "/usr/lib/python3/dist-packages/django/utils/log.py" in emit 118. reporter = ExceptionReporter(request, is_email=True, *exc_info) File "/usr/lib/python3/dist-packages/django/views/debug.py" in __init__ 246. self.template_info = getattr(self.exc_value, 'template_debug', None) File "/usr/lib/python3.7/tempfile.py" in __getattr__ 614. file = self.__dict__['file'] Exception Type: KeyError at /postorius/lists/LISTNAMEREDACTED/ Exception Value: 'file'

1 1

import21: ModuleNotFoundError: No module named 'Mailman'
by Christian Schwarz July 29, 2019

July 29, 2019

Hi, I am migrating a Mailman 2.1 setup to Mailman 3 (Debian Buster). Most mailing lists can be imported successfully using the `import21` subcommand, as described in the docs. Some mailing lists fail with the following error: sudo -u list mailman import21 REDACTEDLIST(a)example.org /var/lib/mailman/lists/REDACTEDLIST/config.pck Traceback (most recent call last): File "/usr/bin/mailman", line 11, in <module> load_entry_point('mailman==3.2.1', 'console_scripts', 'mailman')() File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/decorators.py", line 17, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/lib/python3/dist-packages/mailman/commands/cli_import.py", line 64, in import21 pickle_file, encoding='utf-8', errors='ignore') ModuleNotFoundError: No module named 'Mailman' Note again: most mailing lists of the installation work fine. And this particular pck file is fairly recently modified. Has this happened before? Any suggestions how to debug this? Thanks, Christian

2 3

Mailman 3 Installation Assistance
by brian＠emwd.com July 26, 2019

July 26, 2019

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: https://xiaoxing.us/2018/01/02/Deploy-Mailman-3-on-AWS-using-Docker/ 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 http://172.19.199.3:8000/postorius/lists/ 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! Brian Carpenter

4 28

Ldap integration with Mailman 3
by sandeep kumar July 18, 2019

July 18, 2019

Hi Team Is anyone using Ldap authentication for Mailman 3. It would be helpful if any such inputs -- Regards Sandeep Kumar +91-9642669192

1 0

Default posting pipeline
by Andrew Bernard July 16, 2019

July 16, 2019

What is a posting pipeline, and what is the difference between detault-posting-pipeline and default-owner-pipeline and virgin? Where to read about this? Andrew

2 1

Delete a single email or thread from hyperkitty archive
by andrew.bernard＠gmail.com July 15, 2019

July 15, 2019

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: https://gitlab.com/mailman/hyperkitty/commit/6e3e6a5270f37543a757d76c0aee12… 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. Andrew

4 7

RHEL 7 + Mailman 3 : Need help and guidance
by vgandhi＠fdu.edu July 15, 2019

July 15, 2019

Hi, We would like to use the latest Mailman 3 in our environment. We are planning to set up RHEL 7 virtual machine. I am trying to figure out best method (if possible - step-by-step guide) for installing and configuring Mailman3 on RHEL 7 . Can someone please provide me some guidance or point me in direction. Thank you.

4 5

Unable to get mailman3-full on Debian
by Frank Yappa July 15, 2019

July 15, 2019

When trying apt-get install on Debian, I get E: Unable to locate package mailman3-full. What am I doing wrong? I have run apt-get update.

3 2

unable to un-subscribe
by Steven Jones July 13, 2019

July 13, 2019

Please fix / unsubscribe me, thanks regards Steven

1 0