November 2017 - Mailman-users - lists.mailman3.org

Find a smtp server to send out emails
by Leon March 12, 2025

March 12, 2025

Hi, This problem is not caused by mailman, but I still want to give it a shot here. I'm hosting a mailing list on top of mailman3. Emails are supposed to be sent out by AWS ses. However, ses requires that sender address must be verified, which leads to a problem that emails sent by subscribers to mailing list cannot be sent to other subcirbers, since their addresses are not verified. And it is impossible to verified every subscriber. Are there smtp service providers allowing unverified email address to send out emails, or do I have other solutions? Thanks. -- Best wishes, Leon

4 3

[MM3-users]Is it possible to grant all users the ability to Create List
by Carrie Knox July 13, 2021

July 13, 2021

Hello, Our company is evaluating mailman3 as an option for company internal list serving. One of the requirements is that anyone with access to the list server be allowed to create and manage lists. Is this possible? If so, how? Is there a "create list" role that can be added for all registered users? Thanks

5 5

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

confirm mail rejected
by Marc Sluiter Sept. 29, 2019

Sept. 29, 2019

Hi, im trying to setup mailman and have an issue: first my environment: - I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/ - I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/ I got almost everything working (with some configuration modifications, see other mail). The only thing which doesn’t work is conformation mails, they are rejected: In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp. Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps? For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/ Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)? Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?) Thanks and greetings, Marc

4 4

Auth question
by David Krantz Jan. 8, 2019

Jan. 8, 2019

Hi, I have of course activated password login as it was not possible to get the provider based logins to work (might be but not worth the time for me right now). Is there any way for an user to request a new password when it is forgotten? I presume that the Persona login is removed now. I cannot hide it in my version or at least I do not know how. cheers // David

6 25

How to get Mailman core to provide more debug info in a running environment
by Henrik Rasmussen Jan. 3, 2019

Jan. 3, 2019

Docker-mailman 0.1.1 I am using Mailman 3.1 in production and I am trying to debug a problem[1] so I tried to setting Mailman to provide more debug info in the smtp.log file[2]. I might have been doing it wrong, but in the mailman-extra.cfg I set [logging.smtp-failure] path: smtp.log and restarted Mailman, which stopped incoming mails until removing the added section. What is the correct way to get Mailman to provide more debug info in the smtp.log 1) https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… 2) http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html… Henrik Rasmussen

4 5

Templates
by David Krantz Dec. 19, 2018

Dec. 19, 2018

Hi. How do I set a template for one specific list? I want one list to have a special footer template. I have tried updating the database (template table) without effect so apparently the database is not used for templates or some kind of fallback is used to set it to the generic footer. Of course I also tried to restart mailman after that operation to try to rule out any caching-related problem. I want to use a file://-path as that is the least painful way of doing it. I also would like a solution to place a file in a special location. My current templates are in a .../var/templates/site/en/ structure with names like list:member:generic:footer.txt Cheers // David

4 14

Whitelist non subscriber
by Mark Ziranski Aug. 27, 2018

Aug. 27, 2018

Hello, I want to whitelist an email address on all lists to bypass moderation. The email address is not a subscriber. On google I found accept_these_nonmembers but I do not know how to use it. Please show me some examples how to whitelist someone(a)example.org. Thanks in advance. M.Z.

4 6

Mailman 3 localization
by Danil Smirnov July 5, 2018

July 5, 2018

Hi! I saw in the docs: Localization > > We have it! We just don’t have proper documentation here yet. > Could you please be more specific - can I switch Mailman 3 installation to Spanish? Regards, Danil Smirnov

7 13

Disabling Gravatar
by Marvin Gülker April 26, 2018

April 26, 2018

Hi everyone, I want to make you aware of a potential privacy problem in Mailman's Hyperkitty. Under the upcoming EU General Data Protection Regulation (GDPR)[1], which will be in force as of 2018-05-25, it is illegal to transmit data to third parties without a right to do so. Without going into the details, the inclusion of third party services into one's website is usually deemed such a transmission, and unless one has explicit consent of the user (e.g., by an optional (!), unticked ticking box) this is normally illegal (if one targets EU users). The GDPR does not affect private and family use (Art. 2(2)(c) GDPR), but the exact reach of that clause is yet to be determined; it certainly does not exclude company use of Mailman. I've found it's possible to disable the social login providers quite easily (we had this discussion here on the mailinglist recently), but I don't see an option to disable Gravatar. If there is one, please enlighten me, but anyway I want to propose this as a feature request against Hyperkitty. A GDPR-compliant implementation of Gravatar in Mailman would look like this: * In order to not transmit website visitor's data (IP address, browser info, etc) to Gravatar, Hyperkitty has to request the avatar image itself and not leave that to the user's browsers to do. In other words, the HTTP GET request needs to come from the server running Hyperkitty and the user's browser then just requests the avatar from the Hyperkitty server. Most likely easiest way to do this is to pre-download the avatar when an email is archived. * In order to not transmit the subscribers' data (email address, allows Gravatar to track the subscriber) to Gravatar illegally, the retrieval of the avatar image from Gravatar has to be disabled by default. Instead, an option needs to be added to the subscriber's control panel which he has to actively enable in order to have his Gravatar downloaded and thus used (privacy-by-default rule). I'm not saying Gravatar tracks people and sells the information gathered, though I have doubts on how Automattic makes money with the service. I'm just outlining the legal duties under the upcoming GDPR for service owners, which are independant of how Automattic processes the data in this specific case. Please don't dismiss this as some side feature not needed. The fines that can be imposed on service owners due to violation of the GDPR are very high (up to 20,000,000 € [that's 20 million euros, really]). Marvin [1]: http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1510481733260&uri=CELEX:… -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

5 5

configure Mysql and postfix on mailman3
by ouerheni.nouha＠gmail.com Feb. 20, 2018

Feb. 20, 2018

Hello all , I configured mailman3 following this contributer guide http://docs.mailman3.org/en/latest/devsetup.html but i'am still getting problem with the configuration of MySQL and postfix . Is this section is enough for MySQL configurations ? [database] class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://myuser:mypassword@mymysqlhost/mailman?charset=utf8&use_unicode=1htmlI will appreciated if there are some documents to provide to cotinue the intergration of mailman3 . Is there any tuto for postfix config ? Thanks in advance Ouerheni Nouha

5 4

import21: A string literal cannot contain NUL (0x00) characters.
by Henrik Rasmussen Feb. 15, 2018

Feb. 15, 2018

Docker-mailman 0.1.1. I am facing errors when using import21 to import list archives. The error message is "A string literal cannot contain NUL (0x00) characters." and the import stops, thus importing only mails up to 2009. The dublicates is mails already imported when retrying. If a mail contains illegal characters I would expect disregarding the particular mail and continue, or ignoring the nul character. bash-4.3# python manage.py hyperkitty_import --verbosity 3 --since "01.01.1970" --list-address example(a)mailman3.ku.dk /opt/mailman-web-data/tmp/example(a)mailman3.ku.dk.mbox Duplicate email with message-id '857A4D84DE6D1D41837DD9284F2729AB08F0C385(a)srv1.example.ku.dk' <857A4D84DE6D1D41837DD9284F2729AB09DA5E45(a)srv1.example.ku.dk> (149) Duplicate email with message-id '857A4D84DE6D1D41837DD9284F2729AB09DA5E45(a)srv1.example.ku.dk' <857A4D84DE6D1D41837DD9284F2729AB09E20126(a)srv1.example.ku.dk> (150) Failed adding message <857A4D84DE6D1D41837DD9284F2729AB09E20126(a)srv1.example.ku.dk>: A string literal cannot contain NUL (0x00) characters. Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 367, in execute_from_command_line utility.execute() File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 359, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py", line 305, in run_from_argv self.execute(*args, **cmd_options) File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py", line 356, in execute output = self.handle(*args, **options) File "/usr/local/lib/python2.7/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 278, in handle importer.from_mbox(mbfile) File "/usr/local/lib/python2.7/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 152, in from_mbox add_to_list(self.list_address, message) File "/usr/local/lib/python2.7/site-packages/hyperkitty/lib/incoming.py", line 149, in add_to_list email.save() File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 796, in save force_update=force_update, update_fields=update_fields) File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 824, in save_base updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields) File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 908, in _save_table result = self._do_insert(cls._base_manager, using, fields, update_pk, raw) File "/usr/local/lib/python2.7/site-packages/django/db/models/base.py", line 947, in _do_insert using=using, raw=raw) File "/usr/local/lib/python2.7/site-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/django/db/models/query.py", line 1043, in _insert return query.get_compiler(using=using).execute_sql(return_id) File "/usr/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 1054, in execute_sql cursor.execute(sql, params) File "/usr/local/lib/python2.7/site-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) ValueError: A string literal cannot contain NUL (0x00) characters. bash-4.3#

6 8

Re: Starting new thread in Postorius -> disappears
by Cameron Smith Dec. 12, 2017

Dec. 12, 2017

I would suggest that there is something very broken here: there seems to be a problem with communication between the email system (mailman core…?) and HyperKitty. On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty [1]. I don’t know if other list members received it in their email inboxes or not. Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives [1]. However, I never received an email copy of his message from the list. So, what’s going on? What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well. [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > On 2017.11.21, at 06:31 , Cameron Smith <ccsmith(a)mail2.cetsi.com> wrote: > > Thor, > > I, too, have been struggling with messages not showing up [1], although the conditions are somewhat different. > > What I have found works to make all of the messages appear is the following, which you might try: > > sudo docker-compose exec mailman-web ./manage.py runjobs yearly > > > [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > >> On 2017.11.21, at 04:41 , Thor Atle Rustad <thor.rustad(a)gmail.com> wrote: >> >>> >>> >>>> When I send a message from the Postorius interface, it is neither sent >>> out >>>> or stored. I briefly see this message: "Your reply has been sent and is >>>> being processed.", and then nothing happens. Cameron Smith Nanaimo, BC tel:1.604.803.0051

2 2

Setting up Admin Account
by Pierre Abbat Dec. 1, 2017

Dec. 1, 2017

So I installed a crontab for list and read about configuring the DB (I think I'll use SQLite). I got to http://docs.mailman3.org/en/latest/config-web.html . Because of the dollar sign, I assume that the commands are to be run as list. Here's what I did: root@lists:~# ls root@lists:~# sudo list sudo: list: command not found root@lists:~# su list This account is currently not available. root@lists:~# ls /var/list ls: cannot access '/var/list': No such file or directory root@lists:~# locate mailman-suite_project root@lists:~# mkdir /var/list root@lists:~# chown list.list /var/list root@lists:~# su list This account is currently not available. root@lists:~# man su root@lists:~# su -s /bin/bash list list@lists:/root$ cd list@lists:~$ cd mailman-suite_project bash: cd: mailman-suite_project: No such file or directory list@lists:~$ mkdir mailman-suite_project list@lists:~$ cd mailman-suite_project list@lists:~/mailman-suite_project$ python manage.py createsuperuser python: can't open file 'manage.py': [Errno 2] No such file or directory list@lists:~/mailman-suite_project$ locate manage.py /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.py /usr/lib/python2.7/dist-packages/django/conf/project_template/manage.pyc /usr/local/lib/python2.7/dist-packages/example_project/manage.py /usr/local/lib/python2.7/dist-packages/example_project/manage.pyc /usr/local/lib/python3.5/dist-packages/falcon/bench/dj/manage.py Which manage.py should I use? Pierre -- Lanthanidia deliciosa: What the kiwifruit would be if it weren't so radioactive.

4 4

Where are the subject templates hidden?
by Thor Atle Rustad Nov. 29, 2017

Nov. 29, 2017

Using Docker. Suppose I've overcome https://gitlab.com/mailman/mailman/issues/359 and I can make Mailman use the templates/site/no directory for my customized templates. Yes, it seems to be working, no hickups when national characters are used in the templates. but... the welcome message still says "Welcome to the "listname" mailing list" in English. Is it possible to change that?

3 3

LMTP not listening
by Bartosz Sawicki Nov. 25, 2017

Nov. 25, 2017

Hi everyone :), This is my first post in this group, so let me thank all of the developers for incredible work with Mailman3. Special congratulations goes to new project leader, Abhilash :) I've been using Mailman2 from over 15 years, and recently decided that it is time to upgrade. For several days I'm playing with all of the components of the system. Currently everything looks to be working nicely :) Mailman-core, Mailman-suite (Postorius, Hyperkitty) installed directly, not using docker containers. The last step was integration with MTA. I've configured Postfix and Mailman-core according to: https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#mailman-… But messages send to the list address are not delivered to the list :( I've started to investigate whats happening and realize that Postfix can not connect to mailman using LMTP. It seems that mailman is not listening on port 8024. Nov 24 13:12:31 lists postfix/lmtp[2737]: connect to 127.0.0.1[127.0.0.1]:8024: Connection refused I've checked log files, but haven't realize anything unusual . Any ideas where I could try to find cause of the problem ? My mailman.cfg file MTA section: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost lmtp_port: 8024 smtp_host: localhost smtp_port: 25 regrds.

3 2

Understanding solved issues in Running releases of Docker-mailman
by Henrik Rasmussen Nov. 24, 2017

Nov. 24, 2017

Newbie-question: This is more or less a GitHub / GitLab question, but specific to Mailman. Now using Running releases<https://github.com/maxking/docker-mailman/blob/master/README.md#rolling-rel…> of Docker-mailman (and in general using Docker-mailman), I am wondering, how I can tell which issues having been solved in each release? My goal is to understand when issues like (currently, but not limited to) Mailman-core issues #256<https://gitlab.com/mailman/mailman/issues/256>, #322<https://gitlab.com/mailman/mailman/issues/322>, #359<https://gitlab.com/mailman/mailman/issues/359> (all which states Closed in the Mailman-core Issue log) and Mailman-core issues #406<https://gitlab.com/mailman/mailman/issues/406>, #410<https://gitlab.com/mailman/mailman/issues/410> and MR !322<https://gitlab.com/mailman/mailman/merge_requests/322> (which all states Open) have been solved and included in the Docker-mailman latest running release and normal release. I pulled the latest Running release<https://github.com/maxking/docker-mailman/blob/master/README.md#rolling-rel…> today, but as I have never been able to recreate the problems (above stated issues) my users experienced on several lists, I would like to make sure they have been solved, before I make a new attempt migrate my Mailman 2 lists to Mailman 3. -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark

2 1

Time Stand Still
by Barry Warsaw Nov. 23, 2017

Nov. 23, 2017

Somewhen in the dark recesses of intarweb history, I found myself as the project leader for both Jython (née JPython) and GNU Mailman. I'd been involved with Jython since it was invented by Jim Hugunin around the time he came to work with us at Pythonlabs. I'd been contributing to Mailman since we inherited John Viega's Python-based Dave Matthews Band list server, and put it to use replacing python.org's Majordomo installation. I'd enjoyed both projects, but knew I could not lead both, so I had to make a choice. I chose to turn over Jython to a team that's done a much better job over the years than I ever could have. Something about email, and especially the communication and collaboration patterns that it facilitates, really fascinated me. I know, I know, but we all have our lapses of sanity. Mine has lasted almost 20 years, a bit more than "momentary" perhaps. I've rarely gotten paid to work on Mailman, but it did provide me some great opportunities. Most notably it led to my 10 year stint at Canonical. I was originally hired on there to integrate mailing lists with Launchpad, and Mailman was the obvious choice. I learned a ton doing that project, and working within the constraints of integrating the two Python-based systems, especially since Launchpad was originally not free software and Mailman was GPL'd. Later, the Zope-based Launchpad source code was released under the AGPL, making much of the monkeypatching unnecessary, but by then the system was solid and reliable, and you don't fix what's not broken. Except, I guess I did. I took a lot of the lessons from that work, along with a good hard look at all the problems with Mailman 2, and began to break another cardinal rule of software development: second system syndrome. The result is Mailman 3. It took forever, and we're still not at complete feature parity with Mailman 2, but at least it's Real Enough to be used at many Real Sites, including python.org and lists.fedoraprojects.org. It would be ridiculous for me to take significant credit for this. I have to acknowledge the amazing user community -- you! -- for all the support, patches, suggestions, feedback, patience, criticism, donations, and contributions that you've given to the project, and to me personally over the years. And my deepest gratitude goes to all the core developers that have stayed or come and gone, but most especially the current Cabal: Abhilash Raj, Aurelien Bompard, Florian Fuchs, Mark Sapiro, Stephen J. Turnbull, Terri Oda. You should know that each and every one of them is truly awesome, both in what they contribute technically, and in their amazing friendships. Mailman is infinitely better because of their involvement, and I've loved spending time with them over the years at the Pycon sprints, making releases and sharing teas and meals. My blog is called We Fear Change, and that's humorously taken from a 90's bit in Mike Myer's excellent Wayne's World movie (a phrase actually uttered by the brilliant Dana Carvey as Garth). The irony of course is that while we all may fear change, it's the one constant thing we can count on. And in fact, we *require* change to thrive, because if you aren't changing, you aren't alive. Time, and being engaged with life's vagaries, means there's no alternative to change; it must be embraced. And so, with a vague reference to the many (good!) changes in my personal and professional life, I'm announcing that I'm stepping down from the project leadership role of GNU Mailman, effective... nowish! And it's with unanimous agreement among the GNU Mailman Steering Committee (a.k.a. the Mailman Cabal), that we are announcing Abhilash Raj as the new project leader. If you don't recognize Abhilash's name, you probably aren't paying attention, at least to Mailman 3. Abhilash came to us in 2013 as a Google Summer of Code student, and he's become one of the project's most valuable contributors. His list of accomplishments is long, and it includes everything from redesigning the website, to integrating CI with our GitLab build system, porting our code to the SQLAlchemy ORM, adding MySQL support, revving up adoption through his Docker images, along with his great coding work on Core, Postorius, HyperKitty, and mailmanclient. This transition is good for the project too. Email, its defining protocols and standards, and its role in our daily lives, has changed profoundly since the early days of Mailman. A fresh perspective and enthusiasm will help keep Mailman relevant to the changing ways we -- especially the FLOSS and tech communities -- communicate. Please join me in supporting Abhilash in every way possible as he takes over in this new role as project leader. I'll be here when and if needed, even as I create space in my "spare" time for... Something Else. I look forward to the vision that Abhilash will bring to the project, and I know that he will do a great job. To me, Mailman has always been about collaboration, and the best way for it to succeed is for you to continue to contribute your insights, experiences, opinions, and skills with positive intention. -Barry https://www.wefearchange.org/

2 1

Starting new thread in Postorius -> disappears
by Thor Atle Rustad Nov. 22, 2017

Nov. 22, 2017

I have had this working before, so I guess it's a simple setup error. When I send a message from the Postorius interface, it is neither sent out or stored. I briefly see this message: "Your reply has been sent and is being processed.", and then nothing happens. I have installed maxking's docker-mailman and copied my old setup with basic stuff like passwords and such. The only new thing is that I'm now running in userspace by putting in /etc/subuid and subguid: mailman:10000:65536 and in /etc/docker/daemon.json: { "userns-remap": "mailman" } So I get the following ownership in /opt/mailman: drwxrwsr-x 3 10100 10000 4096 nov. 21 09:00 core drwx------ 19 10070 10000 4096 nov. 21 09:27 database drwxr-sr-x 5 10100 10101 4096 nov. 21 09:24 web (I have created a user named mailman with uid 10100 so, in reality, it says "mailman" there instead of 10100 but I guess that is irrelevant here)

3 4

Mailman Core 3.1.1 and Postorius 1.1.1 released
by Abhilash Raj Nov. 19, 2017

Nov. 19, 2017

Hello Everyone, I am pleased to announce the release of Mailman Core 3.1.1 and Postorius 1.1.1. Python 2.7 is the only supported version for Postorius 1.1.1 and Python 3.5-3.6 are supported for Mailman Core 3.1.1. Both of these are bugfix releases and include some improvements. For a full list of changes, please see [1] for Core and [2] for Postorius. [1]: http://mailman.rtfd.io/en/release-3.1/src/mailman/docs/NEWS.html [2]: http://docs.mailman3.org/projects/postorius/en/latest/news.html For more information about GNU Mailman, please see our wesbite at one of the following: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ https://mirror.list.org/ Documentation for Mailman 3 is available at: http://docs.mailman3.org/en/latest/ Both of these can be downloaded from PyPI. https://pypi.org/project/mailman/ https://pypi.org/project/postorius/ thanks, Abhilash Raj

1 0

Which crontab?
by Pierre Abbat Nov. 15, 2017

Nov. 15, 2017

According to http://docs.mailman3.org/en/latest/config-core.html, I have to add "@daily mailman digests --send" to the crontab. Which crontab does it go in? In the system crontab, the thing after the time is the username, and there's no user named "mailman" in /etc/passwd. Or should I put a script in / etc/cron.daily/? Pierre -- loi mintu se ckaji danlu cu jmaji

2 10

Rolling releases for Container Images and Funding Campaign for Mailman
by Abhilash Raj Nov. 14, 2017

Nov. 14, 2017

Hi Everyone, As you all know I have been working on container images for Mailman 3. We now have a new "rolling" tag for both mailman-core and mailman-web images. These images have latest source installed for every Mailman component. You can find more information about them on the website [3]. New images are available on quay.io and, moving forward, the rest of the image builds will also be moved to Quay[4][5]. These images are built using git-heads *only* if they are passing our test suite and are re-generated weekly. You should be aware that while all these components are tested with their individual test suites, their combination might sometimes not be stable. This will get you updates/bug-fixes much faster :) As most of you already know, Mailman 3 is the new and improved version with extra features, better security and much better architecture. We released Mailman Suite 3.0 in April 2015 and have come a long ways since then. Mailman Suite 3.1, release May 2016, was aimed to provide feature-parity with Mailman 2.x series and we think we _almost_ hit that goal. Apart from no monthly password reminders, Mailman 3 has a much better Administrator/User interface, REST API for scripting, a really awesome archiver, support for multiple domains, support for external plugins, support for SSO/social login and so much more! I love working on Mailman and would enjoy being able to do so full time for next 6-8 weeks. Mailman 3 is not very far from becoming the default version everyone would use, but it still needs some work to get there. I need help from you, the users of Mailman, to get us there. If you or your organization would like to move to (or, already moved to) Mailman 3, I urge you to donate[1] to us. There are options to donate using Credit Card, Paypal, Bitcoin, Wire Transfer (of any currency), Check and money order. If this campaign succeeds, here is a road map of what I intend to get done: - Move Django apps(UI/Archiver) to Python 3 (or bilingual) - Fork `mailman import` command to provide an upgrade path to Mailman 3.x from Mailman 2.x - Fix MySQL compatibility in Core - Changes in Postorius: - Add support for missing options that are already exposed in Core’s API - e.g. Support for setting templates - Find the commonly used options that are not exposed in Core, add them to Core's API and add to Postorius - Add Admin Dashboard project from GSoC 2014 (maybe?) - Add better testing of container images and provide deployment instructions for Kubernetes & Docker Swarm - Improve the container images to work with new micro-services architecture, to achieve scaling and redundancy in services. - Administrator/User documentation for Postorius & Mailman - (optional) Fork [mmcli](https://github.com/rajeevs1992/mailmancli) project from Rajeev, fix if there is anything missing and add it as an additional command line tool to work with Mailman Core. Maybe pull it under Mailman umbrella. Except for these, if there is something more important that is preventing the adoption of Mailman 3 from your end, we can discuss them. I'd like to mention that I have been working on Mailman 3 for quite some time now and I intend to implement every single item on the list. You donations would help it get done much sooner, hopefully in time for 3.2 release schedule (at PyCon US 2018). You can follow the progress of this campaign here[2]. [1]: https://my.fsf.org/civicrm/contribute/transact?reset=1&id=22 [2]: https://wiki.list.org/x/17892025 [3]: https://asynchronous.in/docker-mailman/#rolling-releases [4]: https://quay.io/repository/maxking/mailman-web [5]: https://quay.io/repository/maxking/mailman-core -- Abhilash Raj maxking(a)asynchronous.in

3 6

Django 2.0 (and newer) requires Python 3; how about archiver and list handler Django apps?
by ddw David Wilson Nov. 13, 2017

Nov. 13, 2017

Hi all; LTS Django version 1.11, the last supporting Python 2.7, was released earlier this year. I noticed that in December 2017, Django version 2.0 will be released, which apparently will require Python 3.X Taken from the Django web site, 'We recommend using the latest version of Python 3. The last version to support Python 2.7 is Django 1.11 LTS.' Given that the utilities to archive and also handle email lists are both Django applications, which apparently have *not* yet been updated to Python 3, if I understand correctly? *This leads me to wonder if this presents a problem moving forward and staying compatible with the current versions of Django (in addition to Mailman 3.0)?* Many thanks in advance for any light you can shed in this area. Best regards. Dave Wilson

2 1

Re: integrating mm3 with postfix / lmtp
by Mark Sapiro Nov. 13, 2017

Nov. 13, 2017

On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: > > No to the domains part and I think virtual alias maps is needed: > > mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: reject: RCPT from pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 <test123@xxx>: Recipient address rejected: User unknown in virtual mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP helo=<[10.0.0.29]> (above slightly sanitized for return to the list) The issue here is your list domain cannot be a virtual_mailbox_domain or a virtual_alias_domain. I have the same issue on mail.python.org where we have both Mailman 2 and Mailman 3 lists @python.org. and python.org is a virtual_alias_domain. I have a group of MRs for a branch that implements "alias_domains" to deal with this. Basically it works by creating another (virtual_alias_maps) postfix_vmap mapping to map list addresses @python.org to addresses @x.python.org. Then the postfix_domains and postfix_lmtp maps have the x.python.org domain and there is a patch to mailman/runners/lmtp.py to map the x.python.org domain back to python.org. The various MRs are <https://gitlab.com/mailman/mailman/merge_requests/202> for the core, <https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the REST bindings used by Postorius and <https://gitlab.com/mailman/postorius/merge_requests/186> to be able to set an alias_domain via Postorius. That's not all implemented at mail.python.org. What's there is the basic Postfix config, a bash script the generate the new mappings from the old and a simple patch to mailman/runners/lmtp.py. So, the bottom line is it can be done and it's in process, but it won't really be supported until Mailman 3.2. In the mean time, you just need to have a separate domain for your lists that isn't a virtual_*_domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 15

HyperKitty: discussions not updating, misreporting stats
by Cameron Smith Nov. 13, 2017

Nov. 13, 2017

These are a couple of HyperKitty issues that I have talked about in August [1]. I’ve been doing a bit more experimentation in the last few days and am reporting my findings. The two issues are: — Missing messages: HyperKitty doesn’t show all of the messages in a discussion - Misreporting of discussion statistics: HyperKitty doesn’t update the number of participants and comments in a discussion I’m using the latest Docker setup. Neither of these issues are solved by updating or rebuilding indexes: sudo docker exec mailman-web ./manage.py update_index sudo docker exec mailman-web ./manage.py rebuild_index However, if I stop and then restart the containers (sudo docker-compose down; sudo docker-compose up -d), the discussion statistics are updated and properly display the number of participants and comments in all discussions. This does not, however, solve the problem of missing messages. I have discovered two methods of displaying the missing discussion messages: add a new message to the thread in HyperKitty; I’m not convinced that this works *every* time, but it at least works *most* times run the yearly cron job; this seems to work *every* time: sudo docker exec mailman-web ./manage.py runjobs yearly [1]: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Cameron Smith

2 1