- Mailman-users - lists.mailman3.org

Sync Members of a MM3 Mailing List
by brian＠emwd.com Feb. 12, 2020

Feb. 12, 2020

Does Mailman 3 have a feature/script/function that corresponds with the sync_members script that Mailman 2 has? I have a Mailman 3 client that wants to automate the process of keeping a MM3 list synchronized with a file on the server. Thanks, Brian

4 4

task runjobs minutely uses 100% cpu
by Lars Schimmer Feb. 12, 2020

Feb. 12, 2020

Hi! Since we do run roughly 40 mailinglists on mailman3, the schedules/cronjob task python3 /usr/share/mailman3-web/manage.py runjobs minutely uses 1 CPU core 100% all the time. Any idea howto see why? debian mailma3n-full package 3.2.1-1 Mailman Core Version GNU Mailman 3.2.1 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.7.3 (default, Apr 3 2019, 05:39:12) [GCC 8.3.0] 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

4 6

Your Dashboard
by Torge Riedel Feb. 12, 2020

Feb. 12, 2020

Hi, everytime I receive a mail for moderation it says: At your convenience, visit your dashboard to approve or deny the request. So, I am wondering where this "dashboard" might be. We are managing 11 different lists (small scenario I think) and currently we have to navigate to each list and its page of mails to moderate. I like the idea of a "dashboard" were you can see a summary of mails to moderate and other stuff to have an eye on. And directly do this from this dashbard. Which is convenience. If it is already there, where do I find it? If not, do others also find such a dashboard helpful? Best regards Torge

5 6

minutely cronjobs: ModuleNotFoundError: No module named 'settings
by Bjoern Franke Feb. 10, 2020

Feb. 10, 2020

Hi, on a system running Debian 10 the minutely cronjobs fail since it was rebooted. The following is the output of django-admin >/dev/null && django-admin runjobs minutely --pythonpath /usr/share/mailman3-suite --settings settings Traceback (most recent call last): File "/usr/bin/django-admin", line 21, in <module> management.execute_from_command_line() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 364, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 308, in execute settings.INSTALLED_APPS File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 56, in __getattr__ self._setup(name) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 41, in _setup self._wrapped = Settings(settings_module) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 110, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 965, in _find_and_load_unlocked ModuleNotFoundError: No module named 'settings' I'm wondering why this module is missing and reinstalled several django packages, but none of them has explicitly a settings module. Kind regards Bjoern

2 2

Cannot setup announce-only mailing list
by Alberto Granzotto Feb. 8, 2020

Feb. 8, 2020

Dear all, I don't understand how to set up an "announce only" mailing list using Postorius Version 1.2.4. What I do is the following: - Click on "Create New List" - From "List Style", select "Announce only mailing list style." - Fill all other fields in the form - Click "Create list" At this point people can subscribe to the newly created announce mailing list. If they add themselves they end up in "List Members", and if they email the announce mailing list, their email is relayed to all other members, just like a normal mailing list :/ Moreover, subscribers get this message, inviting them to post to the announce only mailing list: > Welcome to the "Test-announce" mailing list! > > To post to this list, send your email to: > > test-announce(a)lists.dist0rtion.com Of course, I want to keep this mailing list "read only" for members, and I want only selected people to post to that mailing list. Any idea on how to achieve that? Best, Alberto

4 4

Attachement processings questions
by Lars Schimmer Feb. 7, 2020

Feb. 7, 2020

Hello, I got some questions about attachements in MM3 mailinglists and HyperKitty. Hard to find any real documentation about this in the huge load of links out there. Short: Debian Stretch system with MailMan 3.2.1-1 packages (Postorius 1.2.4, HyperKitty 1.2.2). In a mailinglist it seems some mails are not forwarded to a member, but is listed in archive in hyperkitty. That mail did include a PDF attachement, but HyperKitty does not list any attachement. All I found was "convert HTML to plaintext", but does this setting remove attachements? Is there any generel documentation about attachement processing in MM3? I would like this mailinglist to accept mails with attachements, send it to the members and archvie the attachments in HyperKitty, to. Any idea where to look? Thank you so far. 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 6

where to configure max_days_to_hold on MM3 GUI interface?
by Shashikanth Komandoor Feb. 6, 2020

Feb. 6, 2020

Hi Sir, I came to know that the held messages can be restricted to be processed after a specific no of days or can be discard after some days using the parameter *max_days_to_hold*. But I could see that parameter value configurable on MM2 GUI interface in General Options but I don't see the same on the MM3 GUI interface. Could you please help me if I am missing something? -- Thanks & Regards, Shashi Kanth.K 9052671936

3 6

Disable response to the list request address
by Dieter Leupold Feb. 6, 2020

Feb. 6, 2020

Hi all, a short question (MM3.1.1): is it possible to avoid responses when someone sends emails to the request-address (xxx-request(a)lists.xxxx.com) of a mailinglist? Thanks for your information! Dieter Leupold

2 1

Re: Mailman3 on Debian 10
by Mark Sapiro Jan. 31, 2020

Jan. 31, 2020

On 1/30/20 8:24 AM, Bala Mutyam wrote: > Hi Mark, > > Thanks for the update and I managed to resolve the errors on the UI. > > I have 2 more questions about the mailman3. > > 1) how to create Mailing Lists? You can create lists with the `mailman create` command lint tool or via Postorius as a superuser. > 2) super user login is not working even with correct login credentials and giving me - The username and/or password you specified are not correct. How did you create the super user? You should do it with the django admin createsuperuser command. > 3) Password Reset Email urls and email confirmation web pages giving me - This site can't be reached error. If this is an error from your browser, there is something wrong with the host portion of the URL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: Mailman3 on Debian 10
by Mark Sapiro Jan. 31, 2020

Jan. 31, 2020

On 1/30/20 9:22 AM, Bala Mutyam wrote: > Sorry one more issue, > > Mailman settings page giving me below error. > > Server error > An error occurred while processing your request. > > Error logs: > > ERROR 2020-01-30 17:20:11,331 16285 django.request Internal Server Error: /postorius/accounts/subscriptions/ > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 41, in inner > response = get_response(request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 187, in _get_response > response = self.process_exception_by_middleware(e, request) > 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/django/contrib/auth/decorators.py", line 23, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python3/dist-packages/postorius/views/user.py", line 306, in user_subscriptions > mm_user = MailmanUser.objects.get_or_create_from_django(request.user) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 164, in get_or_create_from_django > return self.get(address=user.email) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 86, in get > return method(*args, **kwargs) > File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 322, in get_user > return User(self._connection, content['self_link'], content) > KeyError: 'self_link' Just prior to this is a call to the REST API to GET /users/user(a)example.com (or whatever the user's address is). It appears that that user doesn't exist in core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Deliverability and Spam Filtering
by tom＠gather.coop Jan. 30, 2020

Jan. 30, 2020

Hi folks! First time poster, long time Mailman user. I am setting up a new Mailman 3 instance, and am super excited about the REST API. I plan to use it to enable tight integration with a separate web app that I maintain. As I am setting up the mail server, I am wondering about two related things: deliverability (for outgoing mail) and spam filtering (for incoming mail). What solutions have folks used for these? I know it is generally common now to outsource this critical task to a cloud provider like Mailgun or etc. Have folks needed this or is running ones own incoming and outgoing mail not a big deal? So many horror stories out there... As far as Mailgun goes, I think it should be straightforward to configure it for outgoing mail, but I'm not sure how I'd use it for incoming. Mailgun can forward mail via HTTP or to another email address. Neither I think would work out of the box. It would be great if there were a REST API endpoint for incoming mail, but I don't think such a thing exists, right? Perhaps I could add one? Another thought I had was that I could write a simple HTTP server that receives mail from Mailgun and forwards it to Mailman via LMTP. But it seems simpler to go right to Mailman's core API given that one exist already. Or am I thinking about this all wrong? Are there other more suitable services out there? I looked for cloud MTA providers but didn't turn up much except for in the large enterprise space, which I'm sure I can't afford. Thanks for any thoughts!

4 3

SUBSCRIBE_FORM_SECRET in MM3?
by Gila Halpern Jan. 30, 2020

Jan. 30, 2020

I've been looking into ways to prevent spam on my company's list, and one thing I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman configuration, which embeds a CSRF token into the form, and prevents it from being submitted until five seconds after it renders, to keep bots from subscribing. Unfortunately, the information I found pertained to Mailman 2. Does this option exist in MM3 as well, or is there a similar option?

3 2

Mass subscribe gives HTTP Error 500 when using custom template
by Jeffrey D Jan. 30, 2020

Jan. 30, 2020

Hi, I have some issues with the Mass Subscribe option on Mailman 3.2.1. When using a custom "The notice sent to a member when they are subscribed to the mailing list." template, Postorius will throw an exception after pushing the "Subscribe Users" button on Mass Subscribe. In the web interface you will see a red notification bar with the text: "HTTP Error 500: b'A server error occurred. Please contact the administrator.'". And in the Mailman.log you will see the following error message: Traceback (most recent call last): File "/usr/lib/python3.7/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 216, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ File "falcon/api.py", line 189, in falcon.api.API.__call__ File "/usr/lib/python3/dist-packages/mailman/rest/members.py", line 266, in on_post pre_approved=pre_approved) File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 520, in register list(workflow) File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 326, in _step_do_subscription self.member = self.mlist.subscribe(self.subscriber) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 494, in subscribe notify(SubscriptionEvent(self, member)) File "/usr/lib/python3/dist-packages/zope/event/__init__.py", line 31, in notify subscriber(event) File "/usr/lib/python3/dist-packages/mailman/app/membership.py", line 169, in handle_SubscriptionEvent send_welcome_message(mlist, member, member.preferred_language) File "/usr/lib/python3/dist-packages/mailman/app/notifications.py", line 52, in send_welcome_message 'list:user:notice:welcome', mlist, language=language.code)) File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 188, in get name, lookup_context, **substitutions) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 109, in get contents = protocols.get(actual_uri, **auth) File "/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line 38, in get response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) File "/usr/lib/python3/dist-packages/requests/api.py", line 75, in get return request('get', url, params=params, **kwargs) File "/usr/lib/python3/dist-packages/requests/api.py", line 60, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3/dist-packages/requests/adapters.py", line 516, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /postorius/api/templates/list/<MAILINGLIST>/list:user:notice:welcome (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f0b5ce8d8d0>: Failed to establish a new connection: [Errno 111] Connection refused')) Postorius/Mailman is running on port 8001, only Postorius still connecting on port 8000. Anyone seen something similar? Thanks in advance! Jeffrey

2 2

DMARC Munging
by Allan Hansen Jan. 30, 2020

Jan. 30, 2020

All, The munged From: header in MM3 still says 'name' via ‘listname’ <‘listaddress’> This caused me and my subscribers a lot of grief in MM2: Some mail clients use the first part up to the From for future key-ahead for new email to ’name’, hiding the address, so what they think is a personal message for ’name’, instead goes to the entire list. Red faces all around. Stephen Thurnbull earlier suggested further munging by replacing the list address in the From: header like this: 'name' via ‘listname’ <‘whoopsieaddress’> Which will return an automated reply explaining the issue. I like this option. How can I get that in? Yours, Allan Hansen allan_hansen(a)icloud.com PS: I always use sender in Reply-To.

2 3

Re: Mailman3 on Debian 10
by Abhilash Raj Jan. 29, 2020

Jan. 29, 2020

Please use mailman-users(a)mailman3.org for questions related to Mailman 3. On Wed, Jan 29, 2020, at 9:22 AM, Bala Mutyam wrote: > Hi there, > > I’m trying to install Mailman3 on Debian 10 as follows . > 1) Installed MariaDB, created databases, users for mailman3 and mailman3-web > 2) Then installed mailman3-full', 'dbconfig-mysql', 'python-pymysql', 'python3-pymysql', 'python3-mysqldb', 'nginx using Anisble script. > 3) I have removed Apache2 as it was installed with mailman3-full. > 4) Created a symbolic link for /etc/mailman3/nginx.conf and updated config files for mailman.cfg, mailman-hyperkitty.cfg, 25_mm3_macros, 455_mm3_router and 55_mm3_transport > > but the mailman service is not able to start it’s giving below error. Could you help me how to resolve it please? And also instructions for to install Mailman3 using Debian packages mailman3-full. I would like to use MySQl as backend and Exim4 as mail server. I couldn’t find new mailing list using the command line utility (/usr/sbin/newlist? > > Please see the attached Traceback. > > On webUI I’m seeing > Server error > An error occurred while processing your request. > > > *Attachments:* > * Mailman3 Errors.txt -- thanks, Abhilash Raj (maxking)

2 1

Cron of Mailman notify is not working
by Shashikanth Komandoor Jan. 29, 2020

Jan. 29, 2020

Hello, With your help, I was able to setup mailman 3.3 on my RHEL 7.5 machine and running well and good. For daily notification I have added the below line in the crontab: 00 08 * * * /var/lib/mailman/venv3/bin/mailman notify But this cron job is not working while I was able to run the same command manually at my CLI. Please help if there is any issue with mailman 3.3 or cronjob. -- Thanks & Regards, Shashi Kanth.K 9052671936

2 3

DMARC Mitigation Wrap
by Allan Hansen Jan. 27, 2020

Jan. 27, 2020

All, After a reinstall I’m back to thinking about the MM3 DMARC mitigation issue. Until munging can be improved, I will be using the option to wrap: MM3 has the option to wrap the main message with a wrap_message. It appears, however, that MM3 is oblivious to all my attempts to include whitespace, in this case a <cr>. When the enclosed message is automatically unwrapped by the receiving client, this causes the wrap and enclosed message's From: header to butt up against each other, which is rather ugly. I tried many tricks, but none worked, such as, <cr>, SPACE+, TAB+, <BLANKLINE>, SHIFT-RETURN, two RETURNS, \r\n and UTF-8 codes. They all either got ignored or copied as entered to the output message. Here’s an example. I just want to put a divider after the wrap_message main text. The From address of this message has been replaced with the list address, while the From name has 'via list' appended. Please be careful when using 'via list' addresses later for new emails, as they will be sent to the whole list.\r\n -------------------------- ----------------------------------------------------------------------\r\n From: Allan Hansen <allan_hansen(a)icloud.com <mailto:allan_hansen@icloud.com>> Subject: [Testlist] wrap with divider and BLANKLINE Which coding option am I missing? I have searched for one online. Yours, Allan Hansen allan_hansen(a)icloud.com

2 1

Header and footer templates in MM3
by Gila Halpern Jan. 26, 2020

Jan. 26, 2020

I read the earlier message from Peter Mueller about message decoration, and where the templates are in the file system. However, when I edit the header and footer templates in Postorius, those templates do not appear in the location specified. Should I be looking somewhere else? (I intend to write a program to rotate though several headers/footers, so I need to know where to have it write to.) Gila Halpern

3 3

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