- 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

Adding a domsin
by Allan Hansen Jan. 13, 2020

Jan. 13, 2020

Hi all, I’m still working on setting up my lists in a domain that was added after MM3 installation. It’s mostly working but the Postorius page and the ‘noreply’ emails still sport the old domain name. I hav looked at all the py and cfg files where the old name appeared, and they no longer hold the old name. My coadmin now tells me that the database has a table with the old name. Any suggestion as to whether that can cause the issue and if it’s safe to change the table. Yours, Allan Hansen P.O. Box 2423 Cypress, CA 90630

3 3

Cannot setup HTTPS support for mailman3-web
by jean-christophe manciot Jan. 11, 2020

Jan. 11, 2020

Ubuntu 20.04 mailman3 3.2.2-1 mailman3-web 0+20180916-10 python3-django 2:2.2.9-2ubuntu1 In ```/etc/mailman3/uwsgi.ini``` (example.org is defined in the local /etc/hosts as 10.0.0.1): ``` [uwsgi] # Port on which uwsgi will be listening. ### suwsgi: uwsgi protocol over TLS uwsgi-socket = example.org:8430 # https://uwsgi-docs.readthedocs.io/en/latest/HTTPS.html?highlight=ssl https = /etc/ssl/example.org.crt,/etc/ssl/example.org_rsakey.pem.decrypted,HIGH ... # Drop privileges and don't run as root. uid = www-data gid = www-data ... ``` I suppose that uwsgi reads the certificate & its private key before dropping root privileges. Right now, uwsgi cannot access them as ```www-data```. In ```/etc/mailman3/mailman-web.py``` (symlinked to django settings.py) : ``` ... SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_SCHEME', 'https') # Other security settings # SECURE_SSL_REDIRECT = True # If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT # contains at least this line: # SECURE_REDIRECT_EXEMPT = [ # "archives/api/mailman/.*", # Request from Mailman. # ] # SESSION_COOKIE_SECURE = True # SECURE_CONTENT_TYPE_NOSNIFF = True # SECURE_BROWSER_XSS_FILTER = True # CSRF_COOKIE_SECURE = True # CSRF_COOKIE_HTTPONLY = True # X_FRAME_OPTIONS = 'DENY' ... POSTORIUS_TEMPLATE_BASE_URL = 'https://example.org:8430' ``` In ```/etc/nginx/sites-enabled/example.org.conf``` ``` ... location / { include /etc/nginx/uwsgi_params; # upstream app server uwsgi_pass suwsgi://example.org:8430; } ``` uwsgi is listening on the right address/port: ``` # networks-list-connections.sh | grep :8430 tcp 0 0 10.0.0.1:8430 0.0.0.0:* LISTEN 33 54336045 1768187/uwsgi ``` Despite those settings and all the relevant systemd services restarted, I get ```502 Bad Gateway``` while browsing to ```https://example.org/postorius/lists/?all-lists``` (or any other page) with the following error nginx message: ``` *1 peer closed connection in SSL handshake while SSL handshaking to upstream, client: 10.0.0.1, server: example.org, request: "GET /postorius/lists/?all-lists HTTP/2.0", upstream: "suwsgi://10.0.0.1:8430", host: "example.org", referrer: "https://example.org/postorius/lists/" ``` Of course, without those specific https/suwsgi settings, everything works fine. What am I missing/doing incorrectly? Does uwsgi need access to the certificate/private key while running as non-root for instance?

3 3

Default values for new lists
by Sten Aus Jan. 11, 2020

Jan. 11, 2020

Hi 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 to "Moderate". If anyone has encountered this problem, let me know! All the best Sten

4 5

bounce processing on this list
by Mark Sapiro Jan. 9, 2020

Jan. 9, 2020

I have just installed the latest Mailman core for this list. This version now actually processes bounces. As a result of the huge backlog of unprocessed, queued bounces, some members may receive one or more bounce probe messages. As long as the probes don't bounce, your subscription will be unaffected and you can ignore the probe message. Sorry for the noise. Hopefully it's just a one time catch-up. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

FILTER_VHOST for 3.2.1 not working after install
by Élodie BOSSIER Jan. 8, 2020

Jan. 8, 2020

Hello, I'm using Mailman 2.1.29 since several years and all was perfect except the virtual_host which was "faked" : it was possible to have several mailing list by domain linked to their own domain and url but not same mailing list name for multiple domains. Example (with lighttpd) : - at http://ml.bossier.fr/listinfo we can see ONLY mailing list "test2@", "Test3@" and "Test4@" for @ml.bossier.fr - and at http://ml.franceserv.fr/listinfo we can see ONLY mailing list "bar@", "newsletter@" and "test@" for @ml.franceserv.fr Each url_host have their "own" mailing list. It's the main reason I would like migrate and use Mailman 3 and be able to have "test(a)ml.bossier.fr" and "test(a)ml.franceserv.fr". So I installed Mailman 3.2.1 and I have set "FILTER_VHOST = True" into /etc/mailman3/mailman-web.py then : mailman create --language fr --owner admin(a)franceserv.fr --domain test(a)ml.franceserv.fr mailman create --language fr --owner admin(a)franceserv.fr --domain test2(a)ml.bossier.fr And I have this result (with nginx as front) : - at http://ml.franceserv.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" - and at http://ml.bossier.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" (same result) And it's my problem, I would like be able to see the linked mailing list to their own url. I would like with Mailman 3.2.1 see into : - "example1.com/postorius/lists/" only the mailing list related to example1, - and into "example2.com/postorius/lists/" only the mailing list related to example2 as Mailman 2.1.x do it. I don't understand what I missed, could you help me please ? Best regards, Élodie PS. Sorry for my english language I'm french.

2 1

Migration from 2.1 to 3
by brunol＠agro.uba.ar Jan. 8, 2020

Jan. 8, 2020

Hi, I am in the process to migrate an old 2.1 installation to 3.2.1 (Debian 10.1) Following the 2.1 to 3 docs: - Create a new list - Use the import21 command The command runs successfully (at least no errors in stdout). There is a problem when sending an email to the newly imported list, the message never get send to the members. I do get moderation emails, and if i do a mass subscribe, the welcome email is received by the new members. In a fresh 3 new list (not imported from 2.1) this does not happen. I already tried looking for clues in the logs [logging.smtp] path: debug.log level: debug [logging.smtp-failure] path: debug.log level: debug [logging.error] path: debug.log level: debug But i haven't seen anything useful yet. Any hints on this?

4 14

Hyperkitty - not sending from GUI & reply-thread
by sunil soprey Jan. 8, 2020

Jan. 8, 2020

With latest release (HK 1.3.1), does anyone have an issue with no emails from reply-thread? I able to send/receive emails to/from mailman. I see MTA delivered emails, just no emails from HK GUI. No errors logs (py exception) nor mailman. ideaS? Versions: mailman-hyperkitty (1.1.0) - Mailman archiver plugin for HyperKitty INSTALLED: 1.1.0 (latest) HyperKitty (1.3.1) - A web interface to access GNU Mailman v3 archives INSTALLED: 1.3.1 (latest) mailman (3.3.0) - Mailman -- the GNU mailing list manager INSTALLED: 3.3.0 (latest) postorius (1.3.1) - A web user interface for GNU Mailman INSTALLED: 1.3.1 (latest) django-mailman3 (1.3.1) - Django library to help interaction with Mailman INSTALLED: 1.3.1 (latest) mailmanclient (3.3.0) - mailmanclient -- Python bindings for Mailman REST API INSTALLED: 3.3.0 (latest) f

2 1

Re: [Mailman-Users] MM3 startup issues
by Mark Sapiro Jan. 7, 2020

Jan. 7, 2020

Restoring original Subject:, and doesn't this thread belong on mailman-users(a)msailman3.org - CCing there. On 1/5/20 11:51 PM, Allan Hansen wrote: > > Thanks again, Mark! > My responses below. > >> On 1/4/20 5:47 PM, Allan Hansen wrote: >>> >>> a. The server was set up with the wrong domain name (our fault), so I had to add the ‘correct’ one. I had seen the command ‘Add Domain’ in >>> the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? >> >> >> What are the setytings in Postorius -> Settings -> Archiving? > > Archive policy: Private archives > Archive archivers: hyperkitty, prototype Are the messages in Mailman's var/archives/prototype/LIST@DOMAIN/new directory? Are there messages in Mailman's var/archives/hyperkitty/spool/ directory? What's the setting for base_url in mailman-hyperkitty.cfg? Are there any errors in var/logs/mailman.log? >>> b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That’s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. >> >> >> Set >> >> FILTER_VHOST = True >> >> in settings_local.py >> > > Yes, Brian told me to do the same. This is the what I wrote back: > > hansen@rccrmail:/opt/mailman/mm$ sudo vi settings.py > > Edited the setting to: > # Only display mailing-lists from the same virtual host as the webserver > FILTER_VHOST = True You shouldn't edit settings.py. You should override the setting by putting it in settings_local.py. > Then Brian told me to restart qcluster: > hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster qcluster is not what you need to restart. You need to restart whatever is supporting the wsgi interface to Django. This may be uwsgi or gunicorn or ??. Whatever it is, that's what needs to be restarted. > I then logged in, but the same lists are showing. It either takes the system a long time to reset or it has ignored the > setting. > Just tried it again, and the lists are all showing. Do I need to manually recompile the file? > >> >>> c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: >>> >>> Something went wrong >>> Mailman REST API not available. Please start Mailman core. >> >> >> Postorius is unable to access core's REST API. Is Mailman running? > > Well, I was able to post to the lists, so I assume it is. Listing at processes, I see a bunch of postgres, python3, nginx, django-adminp but > nothing explicitly with a ‘mailman’ string. If you do `ps ax|grep runner=`, what do you see? If you don't see at least three processes with `--runner=rest:0:1`, stop Mailman and start Mailman. >> If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's >> called - defined as `filename` in the `file` handler in the LOGGING >> definition in settings(_local).py. > > hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log > return Site.objects.get_current(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 60, in get_current > return self._get_site_by_request(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 45, in _get_site_by_request > SITE_CACHE[domain] = self.get(domain__iexact=domain) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/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/db/models/query.py", line 408, in get > self.model._meta.object_name > django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. This is because of the domain change. In settings(_local).py you have a setting for SITE_ID. Possibly, setting that in settings_local.py to a value one greater that the current setting will do. To be certain of the correct value, you need to look at the django_site table in mailman's database. That table has 3 columns, id, domain and name. The id for the row of your domain is what needs to be set as SITE_ID. > [ABH] At this point I click to accept a subsription request: > > ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not available > Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen > chunked=chunked, > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 416, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse > response.begin() > File "/usr/lib/python3.7/http/client.py", line 296, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.7/http/client.py", line 265, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without response > > So yes, the REST API is not there. How can I get it going? Stop Mailman and then start it. > Before we added the new domain, I was able to accept subscription requests to the previous domain’s lists. No more. > > Yours, > > Allan -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 3

MM3 shunting mails
by Anders Nilsson Jan. 3, 2020

Jan. 3, 2020

I'm running a Mailman 3.1.0 installation on a CentOS 7 machine. Using RPMs from https://repos.fedorapeople.org/repos/abompard/hyperkitty/el-7/x86_64/ 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 self._process_one_file(msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line 264, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/lib/python3.4/site-packages/mailman/core/pipelines.py", line 53, in process handler.process(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 121, in process process(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 70, in process archiver_set = IListArchiverSet(mlist) File "/usr/lib/python3.4/site-packages/zope/component/hookable.py", 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) File "/usr/lib64/python3.4/site-packages/zope/interface/registry.py", line 348, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3.4/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.4/site-packages/mailman/model/mailinglist.py", line 607, in __init__ ListArchiver.name == archiver_name).one_or_none() File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", line 2733, in one_or_none "Multiple rows were found for one_or_none()") sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() Mar 17 11:54:11 2017 (6217) SHUNTING: 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 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? Regards, Anders Nilsson -- 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

4 4

Mark a list to prevent it being shown as inactive on HyperKitty
by Steven Maddox Jan. 3, 2020

Jan. 3, 2020

Lo Folks, Subject says it all really, is there anyway to mark a list as one which should never be shown as inactive on the HyperKitty web interface? We've got a list which we consider to be "active", it's just that there might be the odd month here or there which it won't show activity. Failing having such a setting (as described above)... maybe there is a way of changing what it considers to be 'inactive' (I'm assuming that it is 30 days?). At the moment (in order to counteract commit 156f4cda) I've dropped this into templates/hyperkitty/bottom.html to uncheck the "Hide Inactive" checkbox... but that doesn't actually stop HyperKitty from considering it inactive - just shows it in dark grey. <script> document.querySelector("input[type='checkbox'][value='inactive']").checked = false; </script> -- Steven Maddox Lantizia

2 1

Weekend releases
by Abhilash Raj Dec. 26, 2019

Dec. 26, 2019

Hi Everyone, Hope everyone had a great weekend! I am pleased to announce new set of releases: - Postorius 1.3.1 - Django-mailman3 1.3.1 - Hyperkitty 1.3.1 These are all bugfix releases and include several fixes each. The full changelogs are available at: - Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1) - Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1) Most notable fixes include a fix for PostgeSQL support in Hyperkitty, ability to delete a MailingList in Hyperkitty and list settings changes are immediately reflected in Hyperkitty (like making a List private). It also includes support for Python 3.8 and Django 3.0 in Postorius and Django-maialman3. Hyperkitty doesn't yet support either of them due to some dependencies not yet supporting Django 3.0 and a bug in Python 3.8.0 causing a test case failure[1]. I hope that we are able to support the latest and greatest as soon as possible, I am excited to be able to play with Django's aync capabilities. Finally, since our i18n workflow has been setup, we have lots of new translations coming in. This release also includes more parts of Postorius being translatable, including section headers. I am really happy to see Mailman 3 move closer to Mailman 2 in terms of i18n. If you want to help us improve the coverage, head on to Weblate[2]. All the releases are available on PyPI, as usual! [1] Fun Fact: The bug was due to a code that I contributed ;-). It is now fixed and will be soon out with Python 3.8.1 sometime this month. [2] https://hosted.weblate.org/projects/gnu-mailman/ -- thanks, Abhilash Raj (maxking)

3 4

postfix virtual domain and mailman 3
by work＠andrefincato.info Dec. 25, 2019

Dec. 25, 2019

hi everyone! i start by saying that i browsed through the archives in here for the past three days, and re-read the mailman 3 docs several times, as well the postfix docs. the thread closest to my problem is this one https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ; i was not sure if it was good to re-open though. i have a postfix + dovecot setup using the "separate domains and non-unix accounts". problem: ``` postfix/smtpd[26356]: NOQUEUE: reject: RCPT from wout1-smtp.messagingengine.com[64.147.123.24]: 550 5.1.1 <list-name(a)domain.com>: Recipient address rejected: User unknown; from=<some(a)email.com> to=<list-name(a)domain.com> proto=ESMTP helo=<wout1-smtp.messagingengine.com> ``` postfix main.cf relevant portion for virtual users ``` # deliver mail for virtual users to Dovecot's LMTP socket virtual_transport = lmtp:unix:private/dovecot-lmtp # setup virtual domains and non-unix accounts virtual_mailbox_domains = /etc/postfix/vhosts virtual_mailbox_base = /var/spool/vmail virtual_mailbox_maps = hash:/etc/postfix/vmaps virtual_uid_maps = static:1001 virtual_gid_maps = static:1001 virtual_alias_maps = hash:/etc/postfix/valias ``` postfix `main.cf` mailman settings ``` transport_maps = regexp:/opt/mailman/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/var/data/postfix_domains ``` question: i tried to add the `alias_domain` to mailman using Mailman Core REST APIs because I read about https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#unusual-… ; entering the mailman console and doing `dump_json('http://localhost:9001/3.0/domains/example.com/lists')` was giving me error that `dump_json` is not an available module. is that the way to go? should I add a an `alias_domain` to Mailman in order for it to output a `postfix_vmap` when doing `mailman aliases`? and then add it to postfix `main.cf` like so ``` virtual_alias_maps = hash:/etc/postfix/valias, regexp:/opt/mailman/var/data//postfix_vmap ``` or do you suggest as a simple viable solution to create a new unix account and setup postfix to use local domains? thanks and hopefully my confusion arose from reading all these threads will dissipate soon!

2 1

content filtering in version 3.1
by Dieter Leupold Dec. 20, 2019

Dec. 20, 2019

Hi, I'm new to MM3. I installed version 3.1.1 on Ubuntu 18.04. All looks fine. But i miss the setting "pass_mime_types" at content filtering. Also i don't find the settings for bounce processing. Are these features no longer supported at version 3.1.1? Thanks for your information! -- Dieter Leupold

2 4

Please update your Mailman installations: CVE-2019-19844
by Abhilash Raj Dec. 19, 2019

Dec. 19, 2019

Hey Mailman Users, A new Django vulnerability was disclosed yesterday[1] which can lead to account hijacks via password reset emails. The fix has been released as a part of Django 3.0.1, 2.2.9, and 1.11.27. We do not support Django 3.0.1, so, please upgrade to 2.2.9 or 1.11.27, depending on which version of Mailman components you are using. If you are using a virtualenv based installation, you can install the new versions using `pip` (venv) $ pip install -U django==2.2.9 or similar for 1.11.27. You can also upgrade django-allauth to 0.41.0, which also fixes this issue[2]. I hope distro packages will soon have updated packages with the fixes. I have also published new versions of Container Images, 0.3.2 (or, 0.3) both have been updated. See more details about updating the containers here[3]. [1]: https://www.djangoproject.com/weblog/2019/dec/18/security-releases/ [2]: https://github.com/pennersr/django-allauth/blob/master/ChangeLog.rst#0410-2… -- thanks, Abhilash Raj (maxking)

1 0

No Message-ID and Postfix
by Seth Seeger Dec. 18, 2019

Dec. 18, 2019

Hello everyone, I have two mailing list members who use an old Android tablet or a Windows 10 mail program, and when they reply to an email, their submission gets rejected: 550 No Message-ID header provided (in reply to end of DATA command) I found this note on how to solve it with Exim: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… https://gitlab.com/mailman/mailman/issues/448 https://gitlab.com/mailman/mailman/merge_requests/540/diffs?commit_id=fa811… Has anyone solved this for Postfix? Thanks, Seth

2 1

"Must issue a STARTTLS command first" issue during social login 'send_email_confirmation'
by jean-christophe manciot Dec. 18, 2019

Dec. 18, 2019

Ubuntu 20.04 mailman3 3.2.2-1 postfix 3.4.7-2 ```/etc/mailman3/mailman.cfg``` ``` [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 smtp_user: user smtp_pass: 'password' smtp_secure_mode: SecureMode.STARTTLS lmtp_host: 127.0.0.1 lmtp_port: 9024 configuration: python:mailman.config.postfix ``` The ```smtp_secure_mode``` value is based on https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/connection.ht…. I am able to send emails using a mail client located on a remote device with the same user/password credentials. Yet, trying to perform a social login leads to: ``` ERROR 2019-12-17 11:44:00,414 211904 django.request Internal Server Error: /accounts/github/login/callback/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/allauth/socialaccount/providers/oauth2/views.py", line 73, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/allauth/socialaccount/providers/oauth2/views.py", line 143, in dispatch return complete_social_login(request, login) File "/usr/lib/python3/dist-packages/allauth/socialaccount/helpers.py", line 152, in complete_social_login return _complete_social_login(request, sociallogin) File "/usr/lib/python3/dist-packages/allauth/socialaccount/helpers.py", line 167, in _complete_social_login ret = _login_social_account(request, sociallogin) File "/usr/lib/python3/dist-packages/allauth/socialaccount/helpers.py", line 55, in _login_social_account signal_kwargs={"sociallogin": sociallogin}) File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 144, in perform_login send_email_confirmation(request, user, signup=signup) File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 312, in send_email_confirmation signup=signup) File "/usr/lib/python3/dist-packages/allauth/account/models.py", line 60, in send_confirmation confirmation.send(request, signup=signup) File "/usr/lib/python3/dist-packages/allauth/account/models.py", line 166, in send get_adapter(request).send_confirmation_mail(request, self, signup) File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 450, in send_confirmation_mail ctx) File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 137, in send_mail msg.send() File "/usr/lib/python3/dist-packages/django/core/mail/message.py", line 291, in send return self.get_connection(fail_silently).send_messages([self]) File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 110, in send_messages sent = self._send(message) File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 126, in _send self.connection.sendmail(from_email, recipients, message.as_bytes(linesep='\r\n')) File "/usr/lib/python3.7/smtplib.py", line 867, in sendmail raise SMTPSenderRefused(code, resp, from_addr) smtplib.SMTPSenderRefused: (530, b'5.7.0 Must issue a STARTTLS command first', 'user@mysite') ``` Any suggestion?

3 3

Mass subscribe question
by Brian Carpenter Dec. 17, 2019

Dec. 17, 2019

Does mass subscribing bypass a list's subscription policy? I had a list owner mass subscribe a large number of invalid mailboxes which resulted in us terminating their service since Mailman 3 has no bounce processing that helps to clean a list up nor a mass invite function that a user can use instead of mass subscribing. If mass subscribing does bypass the subscription policy then I beg you to make mass inviting and bounce processing a HIGH priority. I am really disappointed that Mailman 3 did not come out with a bounce process feature right out of the gates. But the fact it still doesn't have one on Mailman 3.3 seems scandalous. Brian

1 0

UnicodeEncodeError: 'ascii' codec can't encode character
by Marvin Gülker Dec. 16, 2019

Dec. 16, 2019

Hi, I've accidentally sent from an unregisted address to one of my lists. Mailman correctly held the message back for moderation, but when I go to the page for held messages in postorios, I receive a 500 error. I've included an except from the log below. To me, it looks as if it errors on processing my last name (which has a non-ascii character in it). This is Postorius 1.1.2 on Ubuntu 18.04 LTS from the repos. I've searched on the tracker for the problem and found one ticket[1], but it has something with logging so I suppose this is a different problem. Ideas? And how do I discard the message without access to the held messages page? Python version is 3.6.8. Log excerpt: Dec 09 13:21:04 2019 (3090) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.6/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 214, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get resource = self._make_collection(request) File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict resource = self._make_resource(request.id) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 78, in _make_resource resource['msg'] = msg.as_string() File "/usr/lib/python3.6/email/message.py", line 158, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text msg.set_payload(payload, charset) File "/usr/lib/python3.6/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode character '\ufffd' in position 269: ordinal not in range(128) Dec 09 13:21:04 2019 (3090) 127.0.0.1 - - "GET /3.0/lists/tsc-devel(a)lists.secretchronicles.org/held?count=10&page=1 HTTP/1.1" 500 59 -- Blog: https://mg.guelker.eu

3 15

admin/login/ cannot be accessed
by jean-christophe manciot Dec. 14, 2019

Dec. 14, 2019

Ubuntu 20.04 python3-django 2:2.2.6-1ubuntu1 python3-django-hyperkitty 1.3.1 (built from sources) mailman3-full 3.2.2-1 Nginx server configuration: ``` ... ######## # Static ######## location /favicon.ico { alias <mysite_dir>/static/hyperkitty/img/favicon.ico; } location /static/favicon.ico { alias <mysite_dir>/static/postorius/img/favicon.ico; } location /static/ { alias <mysite_dir>/static/; } ####################### # Upstream uwsgi server ####################### location / { include /etc/nginx/uwsgi_params; uwsgi_pass 127.0.0.1:<uwsgi_server_port>; } ... ``` where: - <mysite_dir> is a symlink to <django_dir>/static - <uwsgi_server_port> matches the one defined in ```/etc/mailman3/uwsgi.ini```: ``` [uwsgi] # Port on which uwsgi will be listening. uwsgi-socket = 127.0.0.1:<uwsgi_server_port> ``` All 3 systemd services run fine: - mailman3 - mailman3-web - qcluster I'm trying to login to the django administration pages. I get the django administration login page at: https://mysite/admin/login/ Logging in with the admin credentials leads to: ``` This site can’t be reached The webpage at https://mysite/admin/login/ might be temporarily down or it may have moved permanently to a new web address. ERR_HTTP2_PROTOCOL_ERROR ``` This is very strange because it is the URL which I used to get the login page in the first place. If I launch a test web server at another port with: ``` <django_dir># python3 manage.py runserver <mysite_ip_address>:8080 Performing system checks... System check identified no issues (0 silenced). December 11, 2019 - 17:50:48 Django version 2.2.6, using settings 'settings' Starting development server at http://<mysite_ip_address>:8080/ Quit the server with CONTROL-C. ``` and access it at ```http://<mysite_ip_address>:8080/admin/login/``` to login with the same credentials as before, I get through and all the django administration lines appear, although in a degraded layout: ``` Site administration Accounts Email addresses Add Change Authentication and Authorization Groups Add Change Users Add Change Django Mailman 3 Mail domains Add Change Profiles Add Change ... ``` Any idea what could be happening here?

2 6

bounces with empty message-id
by Peter Münster Dec. 12, 2019

Dec. 12, 2019

Hi, It seems, that mailman bounces the bounces, so that the list-owner never sees them: --8<---------------cut here---------------start------------->8--- postfix/smtpd[12002]: connect from out04.smtpout.orange.fr[193.252.22.213] postfix/smtpd[12002]: 879D6F12E8: client=out04.smtpout.orange.fr[193.252.22.213] postfix/cleanup[11841]: 879D6F12E8: message-id=<> postfix/qmgr[10092]: 879D6F12E8: from=<>, size=4048, nrcpt=1 (queue active) postfix/smtpd[12002]: disconnect from out04.smtpout.orange.fr[193.252.22.213] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 postfix/lmtp[11846]: 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[10092]: 879D6F12E8: removed --8<---------------cut here---------------end--------------->8--- What could I do please, to get the bounces? I would like to use VERP to identify wrong addresses... TIA for any hints, -- Peter

3 8

Hyperkitty Error
by Brian Carpenter Dec. 11, 2019

Dec. 11, 2019

I am seeing the following error being repeated every 2 seconds in the uwsgi-error.log: 01:22:05 [Q] INFO Process-1:19112 processing [compute_thread_positions] 01:22:05 [Q] ERROR Failed [compute_thread_positions] - 'DiGraph' object has no attribute 'node' : Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/django_q/cluster.py", line 381, in worker res = f(*task['args'], **task['kwargs']) File "/usr/lib/python3.6/site-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors obj = graph.node[msgid]["obj"] AttributeError: 'DiGraph' object has no attribute 'node' I am running the docker version of Mailman, version 1.3.0. Any suggestions? Thanks, Brian

3 4

Default moderation for new members
by Seth Seeger Dec. 11, 2019

Dec. 11, 2019

Hello everyone, I’m loving Mailman3 so far! Great work on it. I’d like to have new members who join my lists have their posting ability set to moderated. (After their first legitimate post, they would set to be unmoderated.) I haven’t been able to find this, though I’m suspecting the language has changed. Thanks, Seth

2 3

HyperKitty async tasks runner: systemd qcluster service fails eventually
by actionmystique＠gmail.com Dec. 9, 2019

Dec. 9, 2019

Ubuntu 20.04 mailman3 3.2.2-1 python3-django-hyperkitty 1.3.0-1ubuntu1 According to [Hyperkitty Asynchronous tasks paragraph](https://hyperkitty.readthedocs.io/en/latest/install.html#asynchronous-tasks), we can start a qcluster systemd service file: ``` [Unit] Description=HyperKitty async tasks runner After=network.target remote-fs.target [Service] ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings User=<user> Group=<group> Restart=always [Install] WantedBy=multi-user.target ``` Starting it works fine: ``` # systemctl restart qcluster # systemctl status qcluster ● qcluster.service - HyperKitty async tasks runner Loaded: loaded (/etc/systemd/system/qcluster.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2019-12-04 15:09:46 CET; 2ms ago Main PID: 1055959 ((go-admin)) Tasks: 0 (limit: 9284) Memory: 0B CGroup: /system.slice/qcluster.service └─1055959 (go-admin) Dec 04 15:09:46 samsung4-ubuntu systemd[1]: Started HyperKitty async tasks runner. ``` However, the service fails after a few seconds: ``` # systemctl status qcluster ● qcluster.service - HyperKitty async tasks runner Loaded: loaded (/etc/systemd/system/qcluster.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2019-12-04 15:09:48 CET; 1min 1s ago Process: 1055961 ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings (code=exited, status=1/FAILURE) Main PID: 1055961 (code=exited, status=1/FAILURE) Dec 04 15:09:48 samsung4-ubuntu systemd[1]: qcluster.service: Service RestartSec=100ms expired, scheduling restart. Dec 04 15:09:48 samsung4-ubuntu systemd[1]: qcluster.service: Scheduled restart job, restart counter is at 5. Dec 04 15:09:48 samsung4-ubuntu systemd[1]: Stopped HyperKitty async tasks runner. Dec 04 15:09:48 samsung4-ubuntu systemd[1]: qcluster.service: Start request repeated too quickly. Dec 04 15:09:48 samsung4-ubuntu systemd[1]: qcluster.service: Failed with result 'exit-code'. Dec 04 15:09:48 samsung4-ubuntu systemd[1]: Failed to start HyperKitty async tasks runner. ``` The corresponding log file is empty and I cannot find any issue in the other logs. Any suggestion? Also, another doc paragraph [Running the task queue (required)](http://docs.mailman3.org/en/latest/config-web.html#running-the-t…) talks about another required command "python manage.py qcluster"; so which one is it?

3 9

Source Installation Assistance
by Brian Carpenter Dec. 6, 2019

Dec. 6, 2019

I am trying to install Mailman 3 from source using: https://docs.mailman3.org/en/latest/index.html My first question is where is the best place to get assistance or ask questions regarding the installation process? I am not sure if mailman-users is that place anymore. Thanks, Brian

4 6

Cannot start lmtp runner due to error while attempting to bind on address ('127.0.0.1', 8024): address already in use
by actionmystique＠gmail.com Dec. 4, 2019

Dec. 4, 2019

Ubuntu focal 20.04 mailman3 3.2.2-1 In ```/etc/mailman3/mailman.cfg```: ``` # Where the LMTP server listens for connections. Use 127.0.0.1 instead of # localhost for Postfix integration, because Postfix only consults DNS # (e.g. not /etc/hosts). # Configuration is for a system where Mailman and the MTA are on the same host lmtp_host: 127.0.0.1 lmtp_port: 8024 ``` Stopping mailman3 and checking that no lmtp runner is active: ``` # systemctl stop mailman3 # ps -aux |grep mailman|grep -Pv "(postgres|grep)" www-data 855395 0.0 0.4 82856 37904 ? Ss 13:01 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini www-data 855411 0.0 0.3 156588 25724 ? Sl 13:01 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini www-data 858518 0.0 0.2 82856 22532 ? Ss 13:52 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini ``` Starting mailman3 and checking all active mailman3 runners: ``` # ps -aux |grep mailman|grep -Pv "(postgres|grep)" www-data 855395 0.0 0.4 82856 37904 ? Ss 13:01 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini www-data 855411 0.0 0.3 156588 25724 ? Sl 13:01 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini www-data 858612 0.0 0.2 82856 22532 ? Ss 13:54 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini list 858626 17.8 0.9 103248 74680 ? Ss 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/master --force -C /etc/mailman3/mailman.cfg list 858628 27.2 0.7 87176 62244 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 list 858629 28.6 0.8 89116 64044 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 list 858630 29.2 0.8 90184 64972 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 list 858631 27.0 0.7 87560 62420 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 list 858632 28.8 0.8 89620 64508 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=lmtp:0:1 list 858633 26.6 0.7 84464 60800 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 list 858634 26.2 0.7 81964 58580 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 list 858635 28.4 0.7 88692 63648 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 list 858636 26.4 0.7 83308 59820 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 list 858637 26.8 0.7 84076 60828 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 list 858638 29.2 0.8 90176 64964 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 list 858639 27.4 0.7 87564 62528 ? R 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 ``` We clearly see that lmtp runner is active; then it exits after a few seconds: ``` # ps -aux |grep mailman|grep -Pv "(postgres|grep)" www-data 855395 0.0 0.4 82856 37904 ? Ss 13:01 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini www-data 855411 0.0 0.3 156588 25724 ? Sl 13:01 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini www-data 858612 0.0 0.2 82856 22532 ? Ss 13:54 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini list 858626 2.7 0.9 103248 74680 ? Ss 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/master --force -C /etc/mailman3/mailman.cfg list 858628 4.3 0.9 103260 74704 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 list 858629 4.3 0.9 103256 74964 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 list 858630 4.3 0.9 103256 74920 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 list 858631 4.3 0.9 103256 74804 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 list 858633 4.4 0.9 103924 75444 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 list 858634 4.3 0.9 103256 74392 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 list 858635 4.3 0.9 103260 74876 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 list 858636 4.4 0.9 182412 79472 ? Sl 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 list 858637 4.4 0.9 103256 74964 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 list 858638 4.5 0.9 103256 74808 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 list 858639 4.4 0.9 103256 74776 ? S 13:54 0:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 ``` The systemd service status gives a clue: ``` # systemctl status mailman3 ● mailman3.service - Mailman3 server Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-12-02 13:54:45 CET; 2min 51s ago Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 858617 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=exited, status=0/SUCCESS) Main PID: 858626 (python3) Tasks: 14 (limit: 9284) Memory: 688.5M CGroup: /system.slice/mailman3.service ├─858626 /usr/bin/python3 /usr/lib/mailman3/bin/master --force -C /etc/mailman3/mailman.cfg ├─858628 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 ├─858629 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 ├─858630 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 ├─858631 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 ├─858633 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 ├─858634 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 ├─858635 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 ├─858636 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 ├─858637 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 ├─858638 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 └─858639 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: self.lmtp.start() Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: File "/usr/lib/python3/dist-packages/aiosmtpd/controller.py", line 60, in start Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: raise self._thread_exception Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: File "/usr/lib/python3/dist-packages/aiosmtpd/controller.py", line 40, in _run Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: ssl=self.ssl_context)) Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: File "/usr/lib/python3.7/asyncio/base_events.py", line 579, in run_until_complete Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: return future.result() Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: File "/usr/lib/python3.7/asyncio/base_events.py", line 1374, in create_server Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: % (sa, err.strerror.lower())) from None Dec 02 13:54:52 samsung4-ubuntu mailman3[858617]: OSError: [Errno 98] error while attempting to bind on address ('127.0.0.1', 8024): address already in use ``` Of course the port is already in use: it is used by dovecot. ``` tcp6 0 0 ::1:8024 :::* LISTEN 0 1317360 129620/dovecot tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 0 1316324 129620/dovecot ``` I must be missing something.

3 5

Changelog and/or Release Notes
by Brian Carpenter Nov. 28, 2019

Nov. 28, 2019

Now that I am using Mailman 3.3, where can I find the release notes and/or changelog for core, postorius and hyperkitty under Mailman 3.3? Thanks! Brian

2 2

Re: [Mailman-Users] Mailman 3 Ready?
by Stephen J. Turnbull Nov. 27, 2019

Nov. 27, 2019

Allan Hansen writes: > What is the best, easiest, guaranteed-to-work way to get this > Mailman 3 up and running (OS, add-ons, options, etc.). When I tried > myself, I saw a lot of options that I really did not really care to > have because I did not know the consequences of each. I’m an > application programmer, not a systems programmer. It's email, there are no guarantees. I hate to say that, but that's the way it is. In particular, I'm concerned about the "iRedMail" integration, which may be a complete wildcard from my point of view. With respect to the relevant iRedMail components, I can say that Mailman 3 is perfectly happy with Postfix as MTA (it's the recommended configuration, although I use Exim4 for historical reasons), and I've been satisfied with a small-scale set of lists (about 10 active ones, with at most 20 subscribers total) using Apache+mod_swgi to host Postorius and HyperKitty. The problem would be if your friend (is that the Frank in the CC? hi, Frank!) really really wants to manage Mailman 3 through iRedAdmin -- that will get messy I suspect, and pragmatically speaking, we can't support it, we don't have the cycles. So he'd be on his own, especially since the iRedMail folks have their own bespoke mailing list manager. I would recommend avoiding iRedAdmin integration, and just using Postorius since the subscribers and non-site-admin moderators (if any) will need to use Postorius anyway. Ignoring the iRedAdmin issue, the absolute simplest is 1. Install any Linux distribution with a Docker package. 2. Install the distribution's Docker package. 3. Download and install Mailman Project's Mailman 3 container. 4. Upgrade the container manually (ie, download and reinstall) as appropriate. For reference, what I would recommend to my friends, who would give me hands-on access in emergencies: 1. Install the Debian distribution. (What I use.) 2. Pin the Mailman 3 packages to "experimental". The idea would be to get Mailman 3 upgrades as fast as possible, even at the risk of packaging issues. (My experience with default-to-experimental system for several years was that this happened at most once a year, and the three or four cases all got fixed within days.) 3. Install the Mailman 3 packages. 4. Adjust any dependencies that need non-"stable" versions. 5. Upgrade via apt or whatever occasionally. 6. When Mailman 3 is working well, downgrade the pins to a more stable level. Since you do have such a friend, there's probably a similar process that works for his distribution-of-choice. > The problem is that my MacOS users are getting tripped up by the > mangling, as it is hidden by the mail clients. I have instructed > them to remove previous recipients regularly from the list of such, > if they contain the ‘via list’ string. But they don’t read my > emails, and we see many embarrassing email ssent to the lists that > are meant for one-on-one communication. I guess we could provide a setting where reply-to goes *only* to author, instead of to author *and* list as we currently recommend. But that is going to make you (or list owners) the focus of user ire because their intended replies to list go only to author. What do you think? tl;dr The rest is me blowing off steam. :-) > The fact that the mangling will continue is a disappointment. It's a disappointment to the sane people at the IETF, too, including the rep from Yahoo!, who's a very smart lady (I may be biased, she gave me a kitten once. ;-) Yahoo! is violating the original concept (DMARC "p=reject" was supposed to be used *only* for "transactional" mail, i.e., direct private communication between a business and its clients), but I see her point: when you've had a hundred million or so address books hacked and sold to spammers, and the spammers are sending literally millions of "recommendation from a friend" spams per hour for days on end, you use the tools to hand. > I’m inclined to tell all my AOL and Yahoo users and others in the same > boat to find another email service. I know the feeling. I'm lucky in that respect: the Ministry of Education prohibits use of yahoo mailboxes at Japanese universities. (Which is a WTF of a different kind: yahoo.co.jp is a franchise, not controlled by yahoo.com, and doesn't use p=reject at least at the time MoE issued that policy.) Mail is just hard. It was designed for a "friendly network of users", not for today's rather hostile open Internet, and even if they had envisioned this in the 70s when the message format and SMTP mail transmission protocol were designed, the fundamental problem is that pretty much everyone has a genuine need, even if only occasional, to receive messages from untrusted and even unknown senders.

1 0

Setting up From: field as list address
by Steven Maddox Nov. 25, 2019

Nov. 25, 2019

Hi folks, I'm trying to configure our mailman3 lists (via postorious) in a way that'll mean they'll behave in the way way that I've witnessed on another 3rd party list (one running mailman2). This is where (when receiving a message from the list) the From: is the list itself, and the person who actually sent it bizarrely appears as a CC:, for example... From: Steven Madox via Shropshire LUG <shropshire(a)mailman.lug.org.uk> Subject: [Shropshire LUG] Whatever To: shropshire(a)mailman.lug.org.uk CC: s.maddox(a)lantizia.me.uk At the moment our settings are the default/recommended... I *was* just going to set munging to 'Reply goes to list' which would just set a 'Reply-To' header... until I realised that... a) that won't help Thunderbird users as it just ignores Reply-To if it came from a list b) doesn't fix the issue with people having their own SPF/DKIM set on their mail domains So ultimately I'm starting to see why this 3rd party mailing list (another linux user group, a neighbouring one just south of us) does it this way... if anyone knows the mailman3 equivalent setting? p.s. I've read both the mailman2 and 3 notes related to why munging is not recommended, but I'd still like to know how this is done - to keep our options open more than anything. -- Steven Maddox Lantizia

2 3

[Mailman-Users] Mailman 3 Ready?
by Stephen J. Turnbull Nov. 25, 2019

Nov. 25, 2019

Reply-To set to mailman-users(a)mailman3.org. Allan Hansen writes: > I need to upgrade from Mailman 2.1 - my hardware needs upgrading > (badly) and the address mangling is having my subscribers rip their > hair out. That's not going to go away. We have ARC support in Mailman 3, but (a) like most envelope manipulation, that should be done in boundary MTAs, not in Mailman, and (b) ARC implementation is not universal. *Very likely* some of your subscribers are going to lose mail if you depend on ARC, rather than munge from. > I need to get this done before they start on my already thinning > hair! I sympathize. I tell the little kids I meet that my hair grows out of the bottom of my face, not the top (it's very alliterative in Japanese[1], the kids frequently don't get it but the accompanying adults usually laugh). > I’m ready and eager to move on to MM3 on a Linux box. The obvious "turn-key" installation is to use the Docker containers, which Abhilash keeps fairly up-to-date. But see comment below about universal working solutions. Which distro do you have? Are you using the distro's packages of Mailman 3 (not yet a good idea, unfortunately), or installing from source? > I have looked into it a few times now and I keep running into the > same blocks. I don't see much moving either. I was hoping someone > (Mailman developing community) would come up with a better working > solution. It's email. There are no universal working solutions. > [Some third party wrote:] My concern is that the Mailman3 is not > ready. There are too many dead ends and undocumented stuff. Who is this guy and has he consulted us? I'd like to do an archive search if he's done so to see what the issues are. > For Mailman2 I have a working integration with iRedMail, that does > not seem to work with 3. What's iRedMail? How does it fit into the community your lists serve? > So, is MM3 ready for the big screen? Works for us, for values of us including python.org. > If so, is there some way/how/where/when that my friend can get help > helping me with the installation other than the published > installation docs, which did not work for us? mailman-users(a)mailman3.org is the Mailman 3 version of this list. If your friend is the type to get his hands dirty with code, and has the time for development activity, mailman-developers(a)python.org would also be useful. You might be better off getting bids from consultants. There's a page listing them on wiki.list.org. > I have looked for both free and commercial alternatives to MM, There are sites that support MM commercially. I think the prices are reasonable, of course YMMV on that. Again, there's a page for those services on wiki.list.org. Footnotes: [1] "hage dakara hige o" -- the vowels are pronounced as Spanish or Italian, the consonants as in English.

1 0

Create new list styles via Postorius
by Torge Riedel Nov. 23, 2019

Nov. 23, 2019

Dear all, I have found this documentation on list styles: https://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html Is there any way to create and configure list styles via Postorius web interface? Thanks in advance Torge

2 1

Advice
by jk＠ascii.com Nov. 20, 2019

Nov. 20, 2019

We are seeking a consultant to help migrate us from Mailman 2.1.9 to 3 > Mailing list (Core + Postorius) + web-forum (Hyperkitty). Any recommendations is appreciated - Jerry

3 2

Adding / manipulating users
by Seth Seeger Nov. 19, 2019

Nov. 19, 2019

Hello, Thank you for your help with the moderation status. My next question - I have two lists from Yahoo to import. I’ve migrated them through groups.io and have a convenient export. I now have all the data in formats I can handle. (json file for members, mbox for archives.) What’s the best way to import hundreds of users, setting their mail delivery status and moderation status at the same time? (There doesn’t seem to be a command line option for adding members anymore where you can also set their delivery status.) I’ve looked at the documentation, but couldn’t figure out what to do. Thanks, Seth

2 3

postorius ssl-certificates for virtual hosts
by Wolfgang Bock Nov. 18, 2019

Nov. 18, 2019

Hello, On my server are several virtual hosts running with different lists per host. The appropriate webaddress is in general: https://lists.[domain]/mailman3/postorius/lists/[listname].lists.[domain]. My domains: [domain-1] starts with a b* [domain-2] starts with a s* [domain-3] starts with a t* If I use the webadress https://lists.[domain-1]/mailman3/postorius/lists/[listname].lists.[domain-… and I do a click on the https-symbol in the address line of my browser I get the secury-information " every thing is ok" and the certificate-information is about the wildcard-certificate I just created for the right domain. Different result is for the webadress https://lists.[domain-2]/mailman3/postorius/lists/[listname].lists.[domain-…. In this case I get an information like "you are using a wrong certificate" clicking on the https-symbol references tot he certificate of [domain-1] I set in my apache2 configuration a symbolic link to apache.conf in the /etc/mailman3/directory and made this active. What did I wrong?? If I set use_https to yes in mailman.cfg I get on the website for all lists: postorius: Something went wrong Mailman REST API not available. Please start Mailman core. In the logs I found … mailman.log Nov 14 23:04:25 2019 (28584) command runner started. Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=0&page=1 HTTP/1.1" 200 90 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=10&page=1 HTTP/1.1" 200 606 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.1/domains HTTP/1.1" 200 1438 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - code 400, message Bad HTTP/0.9 request type ('\x16\x03\x01\x02\x00\x01\x00\x01ü\x03\x03\x00³m\x98¶\x02¨\\Å^\x11£ì{\x94«§*\x 9cÅýÎk\x9f¡ã\x89s/õë') Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "........ü...³m.¶.¨\Å^.£ì{.«§*.ÅýÎk.¡ã.s/õë .Ô$M...b¥øDR.Ï...G¹PpÖ.'W°û-Óìü¶.>......À,À0..Ì©Ì¨ÌªÀ+À/..À$À(.kÀ#À'.gÀ" 400 mailman-web.log ERROR 2019-11-14 22:20:41,471 1405 postorius.middleware Mailman REST API not available Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call response, content = Http().request(url, method, data_str, headers) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, in request (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, in _request (response, content) = self._conn_request(conn, request_uri, method, body, headers) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, in _conn_request conn.connect() File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1012, in connect self.sock = self._context.wrap_socket(sock, server_hostname=self.host) File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket session=session File "/usr/lib/python3.7/ssl.py", line 853, in _create self.do_handshake() File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake self._sslobj.do_handshake() ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1056) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 706, in list_index choosable_domains = _get_choosable_domains(request) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 560, in _get_choosable_domains return [(d.mail_host, d.mail_host) for d in domains] File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 560, in <listcomp> return [(d.mail_host, d.mail_host) for d in domains] File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 121, in __getattr__ return self._get(name) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 87, in _get return self.rest_data.get(key) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 76, in rest_data response, content = self._connection.call(self._url) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 109, in call raise MailmanConnectionError('Could not connect to Mailman API') mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API [pid: 1405|app: 0|req: 963/963] 2a02:8108:483f:b9c0:94f1:d2bb:9642:b6d0 () {62 vars in 1310 bytes} 22:20:41 2019] GET /mailman3/postorius/lists/ => generated 3901 bytes in 89 msecs (HTTP/1.1 503) 5 headers in 180 bytes (1 switches on core 0)

2 6

[Django] ERROR (EXTERNAL IP): Internal Server Error:
by Wolfgang Bock Nov. 18, 2019

Nov. 18, 2019

Hello, I got an errormessage via mail to root@[domain-01]. The complete text is attached in a utf-8-text-file. In the lines ...6, 8, 12, 119, 138, 141, 149, 150, 151, 155, 161, 162, 165, 166, 169, 187, 247, 251, 321 ....you can find links to different domains anonymised as [domain-01], [domain-02], [domain-03], [domain-04]. I don't know how to solve this problem. Regards Wolfgang

2 2

Mailing lists sometimes do not honor moderation_action of non-members
by Alan So Nov. 14, 2019

Nov. 14, 2019

We notice that sometimes mailing lists do not honor moderation_action of non-members. Instead, it follows the default action of the lists. It looks like we can sometimes fix the issue by adding/removing the non-members or adding/removing them as owner in certain order but we are not sure about exactly what we have to do. So, it looks like that it is not caused by the list configuration. We have already verified from the web UI, mailman client and the DB table member that moderation_action of the corresponding non-members are set correctly. Any clues for us to provide further information to troubleshoot the issue and any recommended workaround to get around the issue? Thanks a lot.

3 14

Python error, debian package, again
by Lars Schimmer Nov. 6, 2019

Nov. 6, 2019

Hi! I did filed #248 in https://gitlab.com/mailman/hyperkitty/issues and tried to resolve this issue. Furst converted the database as noted in the ticket, no solution. Second search all unicode subject lines in DB for the specific mailinglist, and delete them all via hyperkitty web interface, no success, error still appears. As the error happens 10-12 time on strange times (6am 2:20 pm, 4:20pm), it does not look like a fixed cron job. Abhilash Raj (maxking) mentionend, it maybe a issue with mailman core trying to deliver the message to hyperkitty. But how can I remove those broken messages, or twitch hyperkitty to accept and discard them? Those 30-60 error messsages/day are really annoying and on the other side do not look fine for mailman3 to break at such a easy task. (could have discarded those messages, also). So, please, howto fix this? thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- 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

2 3

When mass subscribing using format John Doe <john.doe@example.com>, "Members" show some with real name, others without.
by Henrik Rasmussen Oct. 30, 2019

Oct. 30, 2019

GNU Mailman 3.2.0 (La Villa Strangiato): A list administrator asked me why some people is subscribed with full name and some are not, when he is mass subscribing people using the format John Doe john.doe(a)example.com. He had experienced this a lot of times. I tested this several times on my test lists, and one member, who already had his name registrered in Account (Postorius top right), and thus also in Django, kept being subscribed without real name, while the others was subscribed with full name in Members -> Subscribers. It seems (I’m not certain about this) that the one’s without real name is the one’s already having an account and thus registred in Django (admin/auth/user/), while the ones subscribed with full name associated is the ones not having an account already. However, as soon as the member (the one with the account) went to Account and changed his real name, the name was immediately associated with the subscription in Members -> Subscribers. I expect this to be by design, but why isn’t the name associated with the subscription when mass subscribing in the first place, taken from the account? Henrik Rasmussen

2 1

High Server Load problem
by Brian Carpenter Oct. 30, 2019

Oct. 30, 2019

For about a week now, I am seeing very high server loads and it seems to have something to do with the following process hanging: uwsgi --ini /opt/mailman-web/uwsgi.ini I am using the docker version of Mailman. When this process hangs, the server load just goes sky high and both Postorius and Hyperkitty no longer responds. I don't have very many sites on this server and I am running about 30 lists. I really need some assistance here as this needs to be fixed. I am seeing nothing in the logs that is explaining why this process is hanging and why the server load goes through the roof. Running docker-compose restart mailman-web kills the hanged process and the server load goes down. Postorius and Hyperkitty starts responding again. This seems to happen once a day. Brian

2 4

Rendering HTML for moderation
by Gila Halpern Oct. 30, 2019

Oct. 30, 2019

Hi, new member here doing some research for my boss. Does Mailman 3 allow HTML rendering in the moderation queue, or only plain text? I'm asking because our list mod doesn't have time to check each image in a submission individually, so we currently don't allow images, but the boss wants to allow them.

2 1

Mangled digests on Mailman3
by Mark Dadgar Oct. 29, 2019

Oct. 29, 2019

So since I upgraded to Mailman3 recently, I’m getting reports of mangled digests even with with plaintext digests turned on. Running 3.2.1 from the ubuntu packages. This list was imported from mailman 2.1.x. Example below. Any thoughts on how to fix this? - Mark ----- mark(a)pdc-racing.net | 408-348-2878 From: tr*****-request(a)pdc-racing.net <mailto:trackjunkies-request@pdc-racing.net> Subject: tr***** Digest, Vol 267, Issue 464 Date: October 19, 2019 at 5:49:46 PM PDT To: tr*****(a)pdc-racing.net <mailto:trackjunkies@pdc-racing.net> Reply-To: tr*****(a)pdc-racing.net <mailto:trackjunkies@pdc-racing.net> Send tr***** mailing list submissions to tr*****(a)pdc-racing.net <mailto:trackjunkies@pdc-racing.net> To subscribe or unsubscribe via email, send a message with subject or body 'help' to tr*****-request(a)pdc-racing.net <mailto:trackjunkies-request@pdc-racing.net> You can reach the person managing the list at tr*****-owner(a)pdc-racing.net <mailto:trackjunkies-owner@pdc-racing.net> When replying, please edit your Subject line so it is more specific than "Re: Contents of tr***** digest..." Today's Topics: 1. Re: PGE phasing out EV-A (XXXXX) ---------------------------------------------------------------------- Date: Sun, 20 Oct 2019 00:49:38 +0000 From: XXXXX Subject: [PDC] Re: PGE phasing out EV-A To: tr***** - The Single Biggest Drag On US GDP <tr*****(a)pdc-racing.net <mailto:trackjunkies@pdc-racing.net>> Message-ID: <0bca2bfb8e294ea5b910d7ae6d2a698c(a)Progent.com <mailto:0bca2bfb8e294ea5b910d7ae6d2a698c@Progent.com>> Content-Type: multipart/related; boundary="_005_0bca2bfb8e294ea5b910d7ae6d2a698cProgentcom_"; type="multipart/alternative" --_005_0bca2bfb8e294ea5b910d7ae6d2a698cProgentcom_ Content-Type: multipart/alternative; boundary="_000_0bca2bfb8e294ea5b910d7ae6d2a698cProgentcom_" --_000_0bca2bfb8e294ea5b910d7ae6d2a698cProgentcom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGVyZSBhcmUgdGhlIFNNVUQgcmF0ZXMuIFNvY2lhbGlzbSB3b3JrcyENCg0KVGltZS1vZi1EYXkg KDUtOCBwLm0uKSBSYXRlIGRldGFpbHMNCiBOb24tc3VtbWVyDQpPY3RvYmVyIDEgLSBNYXkgMzEN Ck9mZi1wZWFrDQpNaWRuaWdodCDigJMgNSBwLm0uDQokMC4wOTY5IGtXaA0KQWxsIGRheSB3ZWVr ZW5kcyBhbmQgaG9saWRheXMNClBlYWsNCjUgcC5tLiDigJMgOCBwLm0uDQokMC4xMzM4IGtXaA0K T2ZmLXBlYWsNCjggcC5tLiAtIG1pZG5pZ2h0DQokMC4wOTY5IGtXaA0KIFN1bW1lcg0KSnVuZSAx IC0gU2VwdGVtYmVyIDMwDQpPZmYtcGVhaw0KTWlkbmlnaHQg4oCTIG5vb24NCiQwLjExNjYga1do Etc.

2 1