- Mailman-users - lists.mailman3.org

Can I install Mailman 3.3 on RHEL 8 ?
by Shashikanth Komandoor Jan. 25, 2020

Jan. 25, 2020

Hi Team/Sir, Can Mailman 3.3 be installed on RHEL 8? I got this query because while I was trying to install the prerequisites for Mailman 3.3 as per the website http://docs.mailman3.org/en/latest/devsetup.html I found nodejs-less is also to be installed. But I don't find the nodejs-less as part of BaseOS packages or the AppStream modules. Please suggest how to go ahead. -- Thanks & Regards, Shashi Kanth.K 9052671936

1 0

Cannot see the cron jobs for Mailman 3 Installed
by Shashikanth Komandoor Jan. 24, 2020

Jan. 24, 2020

Hi, I have setup the Mailman 3 on my RHEL 7.5 box and found it was working fine. But I found that I am not getting daily summary notifications for which I learnt after browsing through different websites, there should be an entry of *checkdb* in the cron job list. But I did not find any such nor I don't find any cron job updated after the installation of mailman 3. So, please guide how to get those cron jobs of mailman 3 installed again without disturbing the already installed setup. Thanks in advance. -- Thanks & Regards, Shashi Kanth.K 9052671936

2 3

Cannot locate manage.py
by Frank van den Heuvel Jan. 22, 2020

Jan. 22, 2020

Hello, While following https://docs.mailman3.org/en/latest/migration.html, I want to execute: python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox Of course edited with values for my list. But I already get stuck in not being able to locate "manage.py". When I run "locate manage.py", I get: /opt/mailman/mm/venv/lib/python3.7/site-packages/django/conf/project_template/manage.py-tpl /opt/mailman/mm/venv/lib/python3.7/site-packages/example_project/manage.py /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py Which one is the right one? With kind regards and thanks for your work! Frank van den Heuvel BTW: This is a debian 10.2 with Mailman3: Django Version: 2.2.9 Python Executable: /opt/mailman/mm/venv/bin/python Python Version: 3.7.3 Python Path: ['/opt/mailman/mm', '/opt/mailman/mm/', '/opt/mailman/mm/bin', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/opt/mailman/mm/venv/lib/python3.7/site-packages'] Server time: Tue, 21 Jan 2020 08:34:45 -0800 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')

2 1

start_chain not present in migrated lists
by Paul Honig Jan. 21, 2020

Jan. 21, 2020

Hi, Please let me know where I can post my question if this list is not the right place. I'm configuring a mailing list server, migrating from Mailman 2.1 to 3.2.2, and I can't get the migrated mailing lists to work. When I create new mailing lists there is no problem. Here are the versions of Mailman I run : mailman 3.2.2 mailman-hyperkitty (1.1.0) django-mailman3 (1.2.0) postorius (1.3.2) mailmanclient (3.2.2) HyperKitty (1.2.2) The command line I use the migrate the mailing list: /opt/mailman_venv/bin/mailman -C /opt/mailman_venv/var/etc/mailman.cfg import21 mltest(a)test.domain /var/vmail/mig/data/lists/mltest/config.pck When I send an email to a migrated list, of which I made myself a member, no mail is sent, and I get the following stack trace in the log: ==> /var/log/mailman/mailman.log <== Jan 21 15:02:37 2020 (15948) Uncaught runner exception: None Jan 21 15:02:37 2020 (15948) Traceback (most recent call last): File "/opt/mailman_venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman_venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman_venv/lib64/python3.6/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/opt/mailman_venv/lib64/python3.6/site-packages/mailman/core/chains.py", line 40, in process chain = config.chains[start_chain] KeyError: None Jan 21 15:02:37 2020 (15948) SHUNTING: 1579615357.5331464+c5918e305ec281d47ef0caaed070c8c4bde26ee3 It seems like the start_chain has value 'None' and that prevents the mail from processed, but I can't find where to correctly set the start_chain. Please let me know how I can remedy this issue. Kind regards, Paul Honig This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo(a)esa.int)

2 1

Handling of SPAM mails in mailman3 - Check for X-Spam Header
by Torge Riedel Jan. 19, 2020

Jan. 19, 2020

Hi, we migrated successfully to mailman3 so far. I have some questions regarding handling of SPAM mails in mailman, this is the second question: Such SPAM mails are currently hold for moderation with reason "not from a list member". Is there no check for the "X-Spam: Yes" header or is this check done later? I would prefer that a check for such a header is done first and is reported as the reason. Which is IMHO a very important information. Or maybe show "This is detected as SPAM" in big bold red letters in a new column in the list of mails to moderate for such a mail. Maybe there is more eye-candy solution for it. Sometimes mail accounts of allowed users are hacked and we do not want spread SPAM accidently. On my setup all mails are checked by rspamd before local delivery and I see that the "X-Spam" header is set for such mails. So even mails from allowed members with header "X-Spam: Yes" should be hold for moderation. Maybe this is already the case, did not gave it a try yet. Best regards Torge

2 5

Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail
by Torge Riedel Jan. 19, 2020

Jan. 19, 2020

Hi, we migrated successfully to mailman3 so far. I have some questions regarding handling of SPAM mails in mailman, here is the first, second comes in a separate post: The list moderator currently receives a copy of the original mail in the info mail he gets for moderation. This is bad in case it was a SPAM mail, cause we have seen that such an info mail is detected also as SPAM. That might rise problems cause other mail servers might block the info mail as SPAM and if this happens too often blocking the whole server. I fear. At least I see that my rspamd starts learning the info mail as SPAM. I don't want that to happen. I searched mailman web interface for a setting to disable adding a copy to the info mail. But have not found it. Is it missing or where do I have to look? Best regards Torge

3 4

Mailman runners missing - nothing in logs
by Torge Riedel Jan. 19, 2020

Jan. 19, 2020

Hi, since migration from mailman2 to mailman3 I had twice the following, last time today: When sending a mail to a list I get the following reply from postfix after a while: connect to 127.0.0.1[127.0.0.1]:8024: Connection refused Searched on that and found some posts, where the following shell command is named to check what is running: ps -fwwu mailman And I get this as output: UID PID PPID C STIME TTY TIME CMD mailman 1166 1 0 Jan07 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/master -C /opt/mailman/core/mailman.cfg mailman 1180 1166 0 Jan07 ? 00:03:09 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1 mailman 1212 1180 0 Jan07 ? 00:01:10 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1 mailman 11039 11036 0 06:25 ? 00:00:03 /usr/bin/uwsgi-core --ini mailman3.ini mailman 11064 11039 0 06:25 ? 00:00:00 /usr/bin/uwsgi-core --ini mailman3.ini mailman 11065 11039 0 06:25 ? 00:00:01 /usr/bin/uwsgi-core --ini mailman3.ini mailman 17257 1180 0 Jan12 ? 00:00:37 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1 Lots of expected runners are missing. After restarting the service the output of the same command is: UID PID PPID C STIME TTY TIME CMD mailman 11039 11036 0 06:25 ? 00:00:03 /usr/bin/uwsgi-core --ini mailman3.ini mailman 11064 11039 0 06:25 ? 00:00:00 /usr/bin/uwsgi-core --ini mailman3.ini mailman 11065 11039 0 06:25 ? 00:00:01 /usr/bin/uwsgi-core --ini mailman3.ini mailman 14430 1 13 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/master -C /opt/mailman/core/mailman.cfg mailman 14434 14430 18 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=archive:0:1 mailman 14435 14430 20 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=bounces:0:1 mailman 14436 14430 18 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=command:0:1 mailman 14437 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=in:0:1 mailman 14438 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=lmtp:0:1 mailman 14439 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=nntp:0:1 mailman 14440 14430 19 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=out:0:1 mailman 14441 14430 20 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=pipeline:0:1 mailman 14442 14430 20 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1 mailman 14443 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=retry:0:1 mailman 14444 14430 17 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=virgin:0:1 mailman 14445 14430 18 14:50 ? 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=digest:0:1 So now back to good. I checked all the logs prior to restarting the service in directory /opt/mailman/var/log, but I do not see any errors. And the master was still running, I would expect that the master will start / restart a runner in case it died? Fun fact: First time of this problem was two weeks from now, which was two weeks after migration to mailman3. I'm excited if it will happen in two weeks again. Installed packages for core: mailman (3.3.0) mailman-hyperkitty (1.1.0) Any suggestions where I should have a deeper look and maybe find the root cause of this problem? Thanks in advance Torge

2 2

Another set of new releases
by Abhilash Raj Jan. 19, 2020

Jan. 19, 2020

Hi Everyone, Hope everyone had a great weekend! I am pleased to announce new set of releases: - Postorius 1.3.2 - Django-mailman3 1.3.2 - Hyperkitty 1.3.2 This release was required as it turned out 1.3.1 releases did not includes translations in the tarballs that I created and uploaded to PyPI. They do include a couple of bugfixes and more translations. - Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1) - Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1) All three of these releases also officially drop support for Django 1.11. Although, there hasn't been any code change that breaks compatibility with 1.11. It has just been dropped form our CI machinery since our dependencies no longer support 1.11. All the releases are available on PyPI, as usual! -- Thanks Abhilash Raj

2 3

Settings for https support
by Dieter Leupold Jan. 16, 2020

Jan. 16, 2020

Hi, I configured Postorius (via Apache2) to use https, which looks fine. But the connection to hyperkitty failed with "code 400, message Bad request syntax". I tried serveral settings....without success. Could you give me an example, which settings are to configure? Thanks for your help! -- Dieter

2 1

Mailman shell tutorial
by andrew.bernard＠gmail.com Jan. 15, 2020

Jan. 15, 2020

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.

4 5