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

confirm mail rejected
by Marc Sluiter 29 Sep '19

29 Sep '19

Hi, 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, Marc

4 4

Mailman 3 Installation Assistance
by brian＠emwd.com 26 Jul '19

26 Jul '19

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

Unable to get mailman3-full on Debian
by Frank Yappa 15 Jul '19

15 Jul '19

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

delete examples.com site
by enrique.terrazas＠utsa.edu 09 Jul '19

09 Jul '19

Hello, I've been working on setting up Mailman3 on a RHEL 7.5 vm using the guides and documentation found here: http://docs.mailman3.org/en/latest/index.html https://mailman.readthedocs.io/en/latest/README.html http://docs.mailman3.org/projects/postorius/en/latest/index.html http://docs.mailman3.org/projects/mailmanclient/en/latest/README.html https://hyperkitty.readthedocs.io/en/latest/index.html https://gitlab.com/mailman/mailman-hyperkitty nginx is serving the Django applications via uwsgi. I was able to get mailman, postorius + hyperkitty, running and test sending out email verifications. In an attempt to set the default domain to something other than example.com I deleted the site: example.com, I did have another site. Unfortunately, this seems to have broken the Django applications. At the moment I am preparing to delete the virtual environment and set things up again. Unless there is something that can be done in the current virtual environment to "reset" things back to start. I was also running into an issue where the verification emails were successfully sent out. The url to verify the email looks like this: http://my.domain.com:8000/accounts/confirm-email/xxxxxxxxxxxx/ Replacing my.domain.com with the domain I added. How can I get the outgoing verification emails to not reference port 8000? If I take that same link and remove the port, I get the desired page. Port 8000 is blocked at our sites permitter firewall, I don't necessarily want to open it. I'd rather the URL just obfuscate the port and send it to https... Thank you in advance for your attention and assistance. Best regards, Enrique J. Terrazas

3 4

Unable to download attachments from HyperKitty
by Derek Lambert 24 Jun '19

24 Jun '19

I’m having an issue downloading attachments from HyperKitty. The download begins as expected, but never progresses. Eventually it times out. I imagine the browser is expecting data matching the content-length header, but never receives it. Inspecting the contents of the download file reveals (address varies): <memory at 0x7f148fcb9588> I’ve been able to work around the issue with the following patch: --- env/lib/python3.7/site-packages/hyperkitty/models/email.py.orig 2018-12-06 21:38:39.544448735 +0000 +++ env/lib/python3.7/site-packages/hyperkitty/models/email.py 2018-12-06 23:01:39.923239421 +0000 @@ -309,7 +309,7 @@ def get_content(self): folder = self._get_folder() if folder is None: - return self.content + return self.content.tobytes() filepath = os.path.join(folder, str(self.counter)) if not os.path.exists(filepath): logger.error("Could not find local attachment %s for email %s", I haven't been able to replicate the issue with the HyperKitty tests, presumably the issue is somewhere in the Django <-> uwsgi <-> nginx stack. My configs are based on mailman-suite and maxking/docker-mailman. I've tried stripping out all the performance tweaks from my uwsgi and nginx configs, but no change. Versions: HyperKitty 1.2.1 Postorius 1.2.3 Django 2.1.7 nginx 1.14.1 uwsgi 2.0.18 Python 3.7.2 Has anyone come across this before? Derek Lambert

5 6

Please help - Held message is crashing mailman.
by Alex King 21 Jun '19

21 Jun '19

Hi, I've used mailman a lot in the past, and decided to install mailman3 in a recent install. I'm unimpressed so far, it seems buggy. Running on Ubuntu 18.04.2 LTS from packages, mailman3 3.1.1-9, mailman3-web 0+20170523-14, python-django-postorius 1.1.2-3. After a few messages, I now can't go to the "Held Messages" in postorius, I get a 500 error. I tried to interact on the command line, but could not work out how. Reading https://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html and https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…, I tried: # mailman shell Welcome to the GNU Mailman shell >>> command = cli('mailman.commands.cli_withlist.shell') Traceback (most recent call last): File "/usr/lib/python3.6/code.py", line 91, in runcode exec(code, self.locals) File "<console>", line 1, in <module> NameError: name 'cli' is not defined I did a lot of reading of the manual and googled, but I have no idea where the cli object is supposed to come from.....? The documentation is confusing. Anyway, after some trial and error, i found: # mailman shell Welcome to the GNU Mailman shell >>> list_manager = getUtility(IListManager) >>> m=list_manager.get("committee(a)[redacted].org") >>> from mailman.interfaces.requests import IListRequests >>> requests = IListRequests(m) >>> [x for x in requests.held_requests][0].id 8 >>> requests.get_request(8) Traceback (most recent call last): File "/usr/lib/python3.6/code.py", line 91, in runcode exec(code, self.locals) File "<console>", line 1, in <module> 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/requests.py", line 120, in get_request result.data_hash, expunge=False) 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/pending.py", line 138, in confirm value = json.loads(keyvalue.value) File "/usr/lib/python3.6/json/__init__.py", line 354, in loads return _default_decoder.decode(s) File "/usr/lib/python3.6/json/decoder.py", line 339, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib/python3.6/json/decoder.py", line 355, in raw_decode obj, end = self.scan_once(s, idx) json.decoder.JSONDecodeError: Unterminated string starting at: line 1 column 1 (char 0) It seems something was written out to disk that can't be read in for some reason (assuming a json object on disk?) How do I debug this further? How do I find the json being decoded? Any help would be appreciated. (I found mailman2 just worked, I was happy with that.) (My colleague posted a bug about this I believe but I don't have the link to that.) Thanks, Alex

3 3

Hyperkitty Archives - Sidebar years/months
by Enrique Terrazas 20 Jun '19

20 Jun '19

Hello, I’m going through importing archives from mm2 to mm3. One of the lists I’ve imported has messages going back to 11/2013. I was able to successfully import the lists settings using: mailman import21 lists(a)domain.com<mailto:lists@domain.com> /path/to/list/config.pck This successfully imported lists owners, moderators, subscribers, & settings. I then imported the messages with the following command: python /path/to/manage.py hyperkitty_import -l list(a)domain.com<mailto:list@domain.com> /path/to/list.mbox —since 10/01/2013 I used that date because it is older than the first message sent to the list: 11/13/2013 And followed that up with the update index command: python /path/to/manage.py update_index_one_list list(a)domain.com<mailto:list@domain.com> This successfully imported all the messages from 11/13/2013 through 09/30/2018. Here is where I’m facing two issues: * Messages from October 2018 were not imported * The sidebar only shows the year 2018. Fdasfds If I modify the URL to go to https://my.domain.org/hyperkitty/list/list@domain.com/2013/11 the archived emails show up fine. October 2018 shows two test messages I’ve sent but not any of the messages from October 2018 that should have been imported. Is there something additional that needs to be done to show the previous years and months in the sidebar? Thanks, Enrique

4 5

Flushing/syncing hyperkitty with mailman
by Eric Abrahamsen 20 Jun '19

20 Jun '19

I've got mailman running on Ubuntu 14.04, with systemd service files to govern the mailman and hyperkitty qcluster processes. I notice in the systemctl status call for the qcluster command that there are a bunch of errors like: [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. [Q] INFO Process-1:3 processing [rebuild_email_cache_votes] [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes] [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. Is there something more I should be doing to sync hyperkitty's database with mailman? I've got the crontab file in place, and that appears to be running without error. Anything else? Thanks, Eric

4 5

Invalid FilterAction: discard. Treating as discard
by Henrik Rasmussen 12 Jun '19

12 Jun '19

Having set the Filter content to Yes - regardless of other setting in the "Alter Messages" tab, make a HTML message come out empty. I can replicate this on my test list. I have tried debugging by changing each setting one-by-one and sending the user's mail, but no change makes the mail come out with a content. However setting "Filter content" to "no" makes the mail come out okay. With "Filter content" set to "Yes", sending another HTML mail is okay, so something in the user's mail may not be right, but I wonder why setting "Filter content" to no "solves" the problem. Afte all this setting is switching all other settings on and off, so I can't just ask the user to turn it off. May 06 11:53:32 2019 (33) ACCEPT: <250E794B36C1E646AF3D81E1F15348C79DA8CA83(a)P2KITMBX06WC03.unicph.domain> May 06 11:53:32 2019 (37) [LISTNAME](a)lists.example.com invalid FilterAction: discard. Treating as discard May 06 11:53:32 2019 (37) <250E794B36C1E646AF3D81E1F15348C79DA8CA83(a)P2KITMBX06WC03.unicph.domain> discarded by "default-posting-pipeline" pipeline handler "mime-delete": After content filtering, the message was empty May 06 17:27:35 2019 (33) ACCEPT: <250E794B36C1E646AF3D81E1F15348C79DA8CAEC(a)P2KITMBX06WC03.unicph.domain> May 06 17:27:35 2019 (37) [LISTNAME](a)lists.example.com invalid FilterAction: discard. Treating as discard May 06 17:27:35 2019 (37) <250E794B36C1E646AF3D81E1F15348C79DA8CAEC(a)P2KITMBX06WC03.unicph.domain> discarded by "default-posting-pipeline" pipeline handler "mime-delete": After content filtering, the message was empty /Henrik Rasmussen

2 9

Daily Cronjob fails
by Stefan Tatschner 08 Jun '19

08 Jun '19

Hey hey, I applied a recent Update from Debian Buster, und this night a received an email about a failing cronjob. The traceback can be reproduced using: # sudo -u www-data flock -n /var/run/mailman3-web/cron.daily /usr/share/mailman3-web/manage.py runjobs daily ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) START TRACEBACK: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) psycopg2.IntegrityError: null value in column "description" violates not-null constraint DETAIL: Failing row contains (2, hb-events(a)hackbrettl.de, hb-events, null, [hb-events] , 1, 2015-10-22 09:54:53.684306+00, hb-events.hackbrettl.de). The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py", line 36, in runjobs job().execute() File "/usr/lib/python3/dist-packages/hyperkitty/jobs/sync_mailman.py", line 35, in execute sync_with_mailman() File "/usr/lib/python3/dist-packages/hyperkitty/lib/mailman.py", line 131, in sync_with_mailman mlist.update_from_mailman() File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 192, in update_from_mailman self.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 808, in save force_update=force_update, update_fields=update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 838, in save_base updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 905, in _save_table forced_update) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 955, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 667, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1204, in execute_sql cursor = super(SQLUpdateCompiler, self).execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 899, in execute_sql raise original_exception File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 889, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/lib/python3/dist-packages/django/utils/six.py", line 685, in reraise raise value.with_traceback(tb) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) django.db.utils.IntegrityError: null value in column "description" violates not-null constraint DETAIL: Failing row contains (2, hb-events(a)hackbrettl.de, hb-events, null, [hb-events] , 1, 2015-10-22 09:54:53.684306+00, hb-events.hackbrettl.de). END TRACEBACK Appearently there is something wrong with the database. Is there anything what I can do about this? Running the migrations doesn't help: # sudo -u www-data flock -n /var/run/mailman3-web/cron.daily /usr/share/mailman3-web/manage.py migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Thanks! Stefan

3 3