- Mailman-users - lists.mailman3.org

Log rotation
by Darren Smith 11 Apr '18

11 Apr '18

Hey everyone, So I have a question about log rotation... Our mailman.log has grown to over 5 gigs. It's time to add this to log rotation. We added what we thought might work to the /etc/logrotate.d/mailman script, but when we ran it with a -f, we learned that the -f flag doesn't keep old logs. That in itself is fine - a normal scheduled log rotation won't have that problem. My problem is that doing the rotation caused the mailman not to be able to write to the log anymore. It appears that it no longer has a handle to the file. To overcome this with, say, nginx, there is a command in logrotate that you can add that restarts the service. I have found, however, that restarting the mailman service can be VERY problematic. There is so much going on that it takes a very long time to stop, and I have seen several instances where the service never shuts down cleanly - even after 3-4 minutes. The service thinks it is shut down, but there are several threads that haven't yet completed. If they are killed, then you have to go clean up the master.lck files etc. It seems like a bad way of doing things and a good way to somehow corrupt data. Anyway - after rambling... 1) Has anyone come up with a good log rotation strategy that doesn't necessitate a restart of the service? 2) Has anyone seen problems stopping and restarting the service? Is there a way to help with this problem? Thanks, Darren

3 5

"Approved:" header from mailman2 times
by Dmitry Makovey 10 Apr '18

10 Apr '18

Hi, is there any equivalent to "Approved" header that was present in MM2 in MM3 land? Google is not very helpful in that. -- Sr System and DevOps Engineer SoM IRT

3 3

update_index
by Darren Smith 03 Apr '18

03 Apr '18

Hello, If I'm reading the docs correctly, when we run manage.py update_index, it should be an incremental index of new emails that have been added since the last time update_index was run - can anyone confirm that this is the expected behavior? Or is there another command line option that I am missing? Right now we are indexing EVERYTHING every time that this is run. Probably this wouldn't be much of a problem except that we are importing all of our old archives (they go back to 1998 and comprise over 40.5 million emails) into the new system. As of now we have around 700,000 emails imported into hyperkitty, and since it is indexing everything it is taking around 1 hour and 10 minutes. Obviously we can't run that once a minute. Right now we're doing once a day, meaning that new emails won't be indexed until the next day. Fast forward to when we have all 40 million imported...the full index process will take (we estimate) around 4 days or so. So...can anyone help with how to get the update_index to do only emails added since the last time the update_index was run? Thanks! Darren

2 4

Mailman 3 with AWS auto scaling and potentially load balancing
by Chris McMacken 30 Mar '18

30 Mar '18

After doing a lot of googling I can't seem to find solid answers to a couple of basic mailman hosting questions so I thought I would ask here. I'm looking to build an auto scaling group so that my mailman services can self heal if the EC2 instance goes away. What state if any is stored locally on the filesystem that would need to be backed up and restored when an instance is replaced? I'm also interested in a high availability deployment so I would like to do some basic load balancing to ensure that this requirement is met but I haven't been able to find much on this topic for mailman 3. Can someone point me in the direction of a write up on this problem or comment on it?

2 5

Re: Templates and docker-mailman
by Hathaway, John W. 22 Mar '18

22 Mar '18

Hah, adding the extension did the trick. Should have inferred that. Thanks! John W. Hathaway | IT Director LOCKRIDGE GRINDAL NAUEN P.L.L.P. 100 Washington Avenue S | Suite 2200 | Minneapolis MN 55401 V: 612-339-6900 | F: 612-339-0981 | www.locklaw.com<http://www.locklaw.com/> This e-mail may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient or otherwise have received this message in error, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you are not the intended recipient or otherwise have received this message in error, please notify us immediately by e-mail, discard any paper copies and delete all electronic files of the message.

1 0

TypeError: authenticate() takes exactly 0 arguments (3 given)
by Bjoern Franke 22 Mar '18

22 Mar '18

Hi, after migrating from a PIP install to Debian Backports packages, I get the following error: https://pastebin.com/tCnTuKYz The whole config of mailman3-suite: https://pastebin.com/nzJufYBN Regards Bjoern

2 4

Templates and docker-mailman
by jwhathaway＠locklaw.com 20 Mar '18

20 Mar '18

I have mailman installed through docker-mailman and I'm trying to get rid of the footer decoration in our messages. Based on earlier threads, I have placed an empty file on the host running Docker at: /opt/mailman/core/var/templates/site/en/list:member:generic:footer But this is not being honored by the mailman container. I have restarted all of the containers. Is there something else I need to do?

3 3

Re: Getting rid of held messages from the command line
by Mark Sapiro 19 Mar '18

19 Mar '18

On 03/19/2018 02:22 PM, Aymeric Mansoux wrote: > > Ah, so if I understand you correctly, as long as I'm on 3.1.1, I could > run into this issue again, but then: Yes, this issue will recur with Mailman 3.1.1 and a MySQL database. > - Would patching 3.1.1 with 5477a201 be enough to prevent further issues > until the next stable is released? I think so. The only potential issue is if mailman/database/alembic/versions/4bd95c99b2e7_fix_template_password.py is not in 3.1.1. I think it is, so I think it's OK, but if not, you'd need to modify mailman/database/alembic/versions/3f31035ed0d7_further_increase_pendedkeyvalue_value_.py to point to the 3.1.1 head of the alembic versions. > - How can I clean the current pendedkeyvalue table? With phpMyAdmin or the mysql command. I think you can just delete those entries from the pendedkeyvalue table. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Getting rid of held messages from the command line
by Aymeric Mansoux 17 Mar '18

17 Mar '18

Hello, We're currently running some of Mailman software, as available via pip, namely: - mailman 3.1.1 (pip3) - postorius 1.1.2 (pip2) - hyperkitty 1.1.4 (pip2) - mailmanclient 3.1.1 (pip3) So far so good, however, for some reasons, a couple of our lists have started to accumulate held messages that cannot be manipulated via the REST API. Regardless if we use the web interface or mailmanclient, it ends up with: Mar 14 10:58:32 2018 (24287) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.5/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/local/lib/python3.5/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "/usr/local/lib/python3.5/dist-packages/falcon/api.py", line 244, in __call__ responder(req, resp, **params) File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get resource = self._make_collection(request) File "/usr/local/lib/python3.5/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection for resource in collection] File "/usr/local/lib/python3.5/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> for resource in collection] File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict resource = self._make_resource(request.id) File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 70, in _make_resource resource = super()._make_resource(request_id) File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 39, in _make_resource results = requests.get_request(request_id) File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/local/lib/python3.5/dist-packages/mailman/model/requests.py", line 120, in get_request result.data_hash, expunge=False) File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/local/lib/python3.5/dist-packages/mailman/model/pending.py", line 138, in confirm value = json.loads(keyvalue.value) File "/usr/lib/python3.5/json/__init__.py", line 319, in loads return _default_decoder.decode(s) File "/usr/lib/python3.5/json/decoder.py", line 339, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib/python3.5/json/decoder.py", line 355, in raw_decode obj, end = self.scan_once(s, idx) json.decoder.JSONDecodeError: Unterminated string starting at: line 1 column 1 (char 0) Mar 14 10:58:32 2018 (24287) 127.0.0.1 - - "GET /3.1/lists/xx(a)xx.xx/held HTTP/1.1" 500 59 Is there a way to manipulate/see/remove these mails differently? Right now this prevent moderation of any held messages (note: some lists do not suffer from this and the held panel or mailmanclient works perfectly fine). Thanks!

3 4

disable sign-ups
by Peter Münster 14 Mar '18

14 Mar '18

Hi, I would like to add new accounts only manually, the mailman3 site should not be open for sign-ups. So I've added this code to settings.py: --8<---------------cut here---------------start------------->8--- from allauth.account.adapter import DefaultAccountAdapter class MyAccountAdapter(DefaultAccountAdapter): def is_open_for_signup(self, request): return False ACCOUNT_ADAPTER = 'MyAccountAdapter' --8<---------------cut here---------------end--------------->8--- It seems to work, but the user experience is not optimal: the user can click on "Sign Up", and then gets to "Server Error (500)". This is the log: --8<---------------cut here---------------start------------->8--- ERROR 2018-01-31 21:53:47,116 6769 django.request Internal Server Error: /accounts/signup/ Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 34, in _wrapper return bound_func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 30, in bound_func return func.__get__(self, type(self))(*args2, **kwargs2) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 210, in dispatch return super(SignupView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 79, in dispatch **kwargs) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 182, in dispatch if not self.is_open(): File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 191, in is_open return get_adapter(self.request).is_open_for_signup(self.request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 501, in get_adapter return import_attribute(app_settings.ADAPTER)(request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/utils.py", line 150, in import_attribute pkg, attr = path.rsplit('.', 1) ValueError: need more than 1 value to unpack ERROR 2018-01-31 21:53:47,116 6769 django.request Internal Server Error: /accounts/signup/ Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 34, in _wrapper return bound_func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 30, in bound_func return func.__get__(self, type(self))(*args2, **kwargs2) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 210, in dispatch return super(SignupView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 79, in dispatch **kwargs) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 182, in dispatch if not self.is_open(): File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 191, in is_open return get_adapter(self.request).is_open_for_signup(self.request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 501, in get_adapter return import_attribute(app_settings.ADAPTER)(request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/utils.py", line 150, in import_attribute pkg, attr = path.rsplit('.', 1) ValueError: need more than 1 value to unpack --8<---------------cut here---------------end--------------->8--- Do you have any hints, how to avoid such errors please? TIA for any help, -- Peter

3 2

Internal Server Error: /hyperkitty/api/mailman/archive: ValueError: A string literal cannot contain NUL (0x00) characters.
by Henrik Rasmussen 14 Mar '18

14 Mar '18

This could potentially be associated with [1] and [2], but it does not regard import21. When mails are released or otherwise archived I get an Internal Server Error regarding "ValueError: A string literal cannot contain NUL (0x00) characters." in the web/mailmanweb.log, but unlike importing corrupted archives, this is mails coming from the users in the daily life. Would it be possible for Mailman to check for NUL characters and skip those before archiving? ERROR 2018-03-13 10:38:12,602 39 django.request Internal Server Error: /hyperkitty/api/mailman/archive Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", line 39, in inner response = get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python2.7/site-packages/hyperkitty/views/mailman.py", line 68, in _decorator return func(request, *args, **kwargs) File "/usr/local/lib/python2.7/site-packages/django/views/decorators/csrf.py", line 58, in wrapped_view return view_func(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/hyperkitty/views/mailman.py", line 114, in archive add_to_list(mlist_fqdn, msg) 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. [1] https://gitlab.com/mailman/hyperkitty/issues/155 [2] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/….

1 1

A short link to this page -- TinyURL
by John Griessen 14 Mar '18

14 Mar '18

The wiki page has a convenient TinyURL. Is it feasible to make TinyURLs for archived list threads such as: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…

3 2

Database running VERY hot
by Darren Smith 12 Mar '18

12 Mar '18

Hello all, We had an old installation of Mailman 2.1 across three servers with over 32,000 mailing lists on them. Due to circumstances beyond my control, we had to shut them down and quickly set up Mailman 3 on a new server. We have Mailman3 set up on a single server this time, as we were having problems with a 3-server setup and Hyperkitty and archives. Long story short, it is up and running, and our users are starting to come back. However, we do not have very many users hitting Postorius and Hyperkitty yet, and we are seeing a distressing number of 504 gateway timeouts. We noticed that there is a significant number of queries to the API whenever hitting Postorius's front page to load the mailing lists, and then on every load. It looks as if it makes a single call to the API to get information about a single list, and does this 10 times - once for each list - to render the page. This gets much worse when users set the view to 200 per page, as they are inclined to do with 32,000 mailing lists... What we've done, actually, is to override the front page and point the users to a different set of static pages where we have all of our lists categorized and searchable, and when they find the list they are looking for, we have a link back to postorius. It has taken a lot of the stress off of the server. However, I still see where the database at times can run VERY hot. We have set up this server to run with PostgreSQL. When I do a ps aux | grep postgres, I find a lot of processes that have been spawned to take care of mailman - a dozen or so. However, one of the threads is taking up about 85% of the load, another thread about 14%, and little dribbles here and there from the rest of the threads. Here are the questions: 1) Has anyone run into problems like these? I would think that maybe this is an issue having so many mailing lists, but honestly there aren't that many people using the system yet. It is going to ramp up as the users realize that we are live again, but we aren't getting that much traffic. 2) Is there any configuration that I can set, especially with regards to the database, so that it can be used more efficiently and not throttle through one or two threads? Please let me know what further information I can provide. Thanks in advance for any help or advice! Silas

5 11

Deactivate list without deleting it?
by Colin Watson 03 Mar '18

03 Mar '18

Hi, I'm experimenting with a port of Launchpad's mailing list infrastructure to Mailman 3. If Barry's reading, he may remember that this is no trivial task, so I'm very definitely not promising that it will be done any time soon. :-) However, for the most part it looks relatively tractable with the aid of the plugin improvements in Mailman 3.2.0; I have the rough outline of a plugin that implements much the same feature set as our current pile of monkey-patches against Mailman 2.1 in a much nicer way. One of the major things I haven't figured out yet is list deactivation and reactivation. In our current 2.1-based code, you can deactivate a list in a reversible way, which basically tars up the list directory so that the list archives can be restored later. This isn't a native operation in 2.1, but it could be done because everything lived on the filesystem. In 3, it's less trivial. We could go to some effort to dump things out of the HyperKitty database and restore it on reactivation, but that seems rather complex and a bit silly. Ideally, I'd like mailing lists to have a "deactivated" state in addition to full deletion. In this state, the list would appear nonexistent for most purposes: incoming email would be rejected, Postorius would deny its existence, etc. There'd need to be corresponding extensions to the IArchiver interface which caused the archiver to put its archives of that list into a corresponding deactivated state, in which it would retain the messages but queries for them would return 404 or similar; these extensions would need to be optional, since while it should be relatively easy to do this in HyperKitty it could be hard or impossible for other archivers, and perhaps this should be a separate operation from deactivating the list itself since people may want to close a list while leaving its archives accessible. Has there been any discussion of this in the past, or any advice as to implementation strategy? Thanks, -- Colin Watson [cjwatson(a)ubuntu.com]

3 7

configure Mysql and postfix on mailman3
by ouerheni.nouha＠gmail.com 20 Feb '18

20 Feb '18

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 15 Feb '18

15 Feb '18

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

Number of archives in list
by kawhite＠ancestry.com 15 Feb '18

15 Feb '18

Hi, I am importing hundreds of thousands of mbox archive files and I want to know if there is a way to call a list and see how many archives got imported / are in the list now (is there a hyperkitty command to gets stats such as number of archives on a list?) Thanks in advance,

2 1

"mailman start" hangs
by Peter Münster 14 Feb '18

14 Feb '18

Hi, When starting mailman in a terminal, then it works: --8<---------------cut here---------------start------------->8--- $ mailman start Starting Mailman's master runner $ --8<---------------cut here---------------end--------------->8--- But from "cron", it seems to hang. Output of pstree: --8<---------------cut here---------------start------------->8--- |-cron(3022)---cron(21962)-+-mailman(21986) | `-sendmail(22043)---postdrop(22044) --8<---------------cut here---------------end--------------->8--- So it seems, that mailman does not go into the background, and the email with the output is never sent... How could I solve this issue please? TIA for any hints, -- Peter

3 3

list of subscribers
by Peter Münster 08 Feb '18

08 Feb '18

Hi, Where on the web interface is it possible to see the list of subscribers of a mailing list please? TIA for any hint, -- Peter

4 14

Just starting with mailman3
by Loring 01 Feb '18

01 Feb '18

I am just starting with mailman 3 where can I find good documentation on getting started? -- Richmond Loring rloring(a)bnl.gov Advanced Systems Engineer

2 1

confirm-email: error NoReverseMatc
by Peter Münster 31 Jan '18

31 Jan '18

Hi, When confirming the email address after sign-up, I get this error: --8<---------------cut here---------------start------------->8--- ERROR 2018-01-31 09:31:57,143 28537 django.request Internal Server Error: /accounts/confirm-email/Ng:1egno5:_T5eipR8TTan-zWjLK8EhYuetjQ/ Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 283, in post resp = self.login_on_confirm(confirmation) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 332, in login_on_confirm redirect_url=self.get_redirect_url) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/utils.py", line 157, in perform_login get_login_redirect_url(request, redirect_url)) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/utils.py", line 50, in get_login_redirect_url url = url() File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 362, in get_redirect_url self.request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 176, in get_email_confirmation_redirect_url return self.get_login_redirect_url(request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 156, in get_login_redirect_url return resolve_url(url) File "/usr/lib/python2.7/site-packages/django/shortcuts.py", line 205, in resolve_url return urlresolvers.reverse(to, args=args, kwargs=kwargs) File "/usr/lib/python2.7/site-packages/django/core/urlresolvers.py", line 579, in reverse return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, **kwargs))) File "/usr/lib/python2.7/site-packages/django/core/urlresolvers.py", line 496, in _reverse_with_prefix (lookup_view_s, args, kwargs, len(patterns), patterns)) NoReverseMatch: Reverse for '' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: [] ERROR 2018-01-31 09:31:57,143 28537 django.request Internal Server Error: /accounts/confirm-email/Ng:1egno5:_T5eipR8TTan-zWjLK8EhYuetjQ/ Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 283, in post resp = self.login_on_confirm(confirmation) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 332, in login_on_confirm redirect_url=self.get_redirect_url) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/utils.py", line 157, in perform_login get_login_redirect_url(request, redirect_url)) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/utils.py", line 50, in get_login_redirect_url url = url() File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 362, in get_redirect_url self.request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 176, in get_email_confirmation_redirect_url return self.get_login_redirect_url(request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 156, in get_login_redirect_url return resolve_url(url) File "/usr/lib/python2.7/site-packages/django/shortcuts.py", line 205, in resolve_url return urlresolvers.reverse(to, args=args, kwargs=kwargs) File "/usr/lib/python2.7/site-packages/django/core/urlresolvers.py", line 579, in reverse return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, **kwargs))) File "/usr/lib/python2.7/site-packages/django/core/urlresolvers.py", line 496, in _reverse_with_prefix (lookup_view_s, args, kwargs, len(patterns), patterns)) NoReverseMatch: Reverse for '' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: [] --8<---------------cut here---------------end--------------->8--- What could be the reason, and how could I solve this issue please? Since it's perhaps related, here is my urls.py: --8<---------------cut here---------------start------------->8--- from django.conf.urls import include, url from django.contrib import admin from postorius.views.list import list_index urlpatterns = [ url(r'^postorius/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), url(r'^admin/', include(admin.site.urls)), url(r'^$', list_index, name='list_index'), ] --8<---------------cut here---------------end--------------->8--- TIA for any help, -- Peter

2 4

setup of URLs
by Peter Münster 29 Jan '18

29 Jan '18

Hi, I would like to point "https://my-domain.org/" to the list of mailing-lists of this domain. How should I setup my Apache configuration and/or the urlpatterns please? With my actual configuration, the above URL is always rewritten to https://my-domain.org/postorius/lists/ These are my urlpatterns: urlpatterns = [ url(r'^$', RedirectView.as_view( url=reverse_lazy('list_index'), permanent=True)), url(r'^postorius/', include('postorius.urls')), url(r'^archive/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), url(r'^admin/', include(admin.site.urls)), ] TIA for any help, -- Peter

4 4

Where is postorius.wsgi?
by Peter Münster 28 Jan '18

28 Jan '18

Hi, I try to install Postorius, but I don't find the file postorius.wsgi. Where should I get it please? This is, what I've done so far: - git clone https://gitlab.com/mailman/postorius.git - cd postorius - python3 setup.py install - cd example_project - virtualenv venv - . venv/bin/activate - pip3 install -r requirements.txt - in venv/lib/python3.6/site-packages/django_mailman3/lib/mailman.py: replace "urllib2" by "urllib.error" - python3 manage.py migrate - python3 manage.py createsuperuser - python3 manage.py compilemessages - python3 manage.py collectstatic Now I try to follow https://postorius.readthedocs.io/en/latest/deployment.html#apache-with-mod-… but I don't find postorius.wsgi ... TIA for any help. Kind regards, -- Peter

5 10

OperationalError: database is locked
by cyp＠trojina.si 25 Jan '18

25 Jan '18

On our installation, we are often gettting Internal Server Error (500). The logs look like this: ERROR 2018-01-09 13:52:57,640 1604 django.request Internal Server Error: /hyperkitty/list/test(a)seznami.cjvt.si/ Traceback (most recent call last): File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/exception.py", line 42, in inner response = get_response(request) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/HyperKitty-1.1.0-py2.7.egg/hyperkitty/lib/view_helpers.py", line 133, in inner mlist = MailingList.objects.get(name=mlist_fqdn) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 379, in get num = len(clone) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 238, in __len__ self._fetch_all() File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 1087, in _fetch_all self._result_cache = list(self.iterator()) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 54, in __iter__ results = compiler.execute_sql() File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/sql/compiler.py", line 835, in execute_sql cursor.execute(sql, params) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/sqlite3/base.py", line 337, in execute return Database.Cursor.execute(self, query, params) OperationalError: database is locked Does this suggest I should switch from sqlite to postgres (https://stackoverflow.com/a/26864360)? I'm happy to do that, but how do I migrate the data between the databases (after installing postgres and creating the database)? I've found this doc (http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html#data…), but I don't think I understand this and I haven't used alembic: these instructions are just for when you modify the model within the same database, right? Thanks in advance!

4 9

Solved issues not in Docker-mailman rolling releases
by Henrik Rasmussen 25 Jan '18

25 Jan '18

I am currently using Docker-mailman rolling releases and with great respect to the maintainer's time it was my impression from @maxking that rolling releases was likely to be one week behind the development. In my report of https://gitlab.com/mailman/mailman/issues/444 @msapiro commented that #444 is a duplicate of #406 (closed) which was fixed by !322 (merged), but !322 was merged a month ago. Thinking that I wasn't up to speed, I did a `docker pull quay.io/maxking/mailman-core:rolling` only got 'XXXXXXXXXXXX: Already exists'. Also `docker images` shows 'quay.io/maxking/mailman-core rolling 1654a3226db8 7 weeks ago 179.3 MB'. Not to be umpolite, did I misunderstand the concept?

2 3

Postorius: Show only own lists
by Thor Atle Rustad 23 Jan '18

23 Jan '18

Imagine an installation with 500+ mailing lists and almost as many local admins that are supposed to maintain their own local lists with a few local members. As site admin, I see all 500+ lists, but I was expecting *local* admins to see only the lists they maintain. I have set all lists to "advertised = False", so they are hidden from ordinary view. Is there a way to show only relevant lists to local admins? I am running docker running release. mailman info GNU Mailman 3.2.0a1 (La Villa Strangiato) Thor Atle Rustad

4 6

mailing list aliases
by Dmitry Makovey 20 Jan '18

20 Jan '18

I'm running mailman 3.3.0 and seeing odd behavior for "Settings/Message Acceptance/Acceptable aliases". Two things strike me as odd: 1. whenever I change content of that field interface keeps on wrapping it in more and more square brackets: [u'[u\'[u"[u\\\'foo(a)my.com\\\']"]\']'] whereas I've started with simple foo(a)my.com. I've checked with mailmanclient library and it seems like this is happening at the core level not just an interface: ml.settings['acceptable_aliases']=['foo(a)my.com'] ml.save() print ml.settings['acceptable_aliases'] am I using it wrong or is there a bug? 2. Related to #1 - we've migrated our mailing lists from foo(a)my.com to foo(a)lists.my.com however we've preserved old addresses. But in new setup mail sent in gets stopped for moderation with: "X-Mailman-Rule-Hits: implicit-dest" . What's the best course of action here to get mailing list respond to multiple email addresses? -- Sr System and DevOps Engineer SoM IRT

3 3

why am I seeing "Access to the archiving API endpoint was forbidden"
by Dmitry Makovey 19 Jan '18

19 Jan '18

Running docker-based MM3 I get quite a few messages in mailmanweb.log: ERROR 2018-01-19 19:09:07,467 401 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.19.199.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured which points to the docker host making those requests. But I have no scripts/code dunning on host to do that. I've posted to this list earlier (see "mailman-web: ResponseNotReady" and "Getting connection refused on postfix trying to connect to mailman-core:lmtp") my woes with public vs private IPs in my setup and my "hack" was to set up docker-compose with explicit domainname and hostname: mailman-core: domainname: my.com hostname: mailman ... networks: mailman: aliases: - mailman.my.com where mailman.my.com is the public IP of the service. so I think I'm in the weird state where mailman-core container starts off communication on a private docker IP and finishes it off on what it thinks is public someplace... not sure where is that coming from. I ran a cross-ping for all containers to confirm they all see only private IPs and they do: core, web & nginx cross-pinging each-other and mailman.my.com all show private docker IPs so why would any packet be routed from external? can I allow more than a single IP for MAILMAN_ARCHIVER_FROM ? ITMT I've moved MAILMAN_ARCHIVER_FROM to settings_local.py and hardwired it to be 172.199.19.1 and I believe there are no errors in log files... but again - that's a lot of tiptoeing and tapdancing around the IP assignment in docker so I'm looking for input to simplify the setup. -- Sr System and DevOps Engineer SoM IRT

1 0

MM3 & postfix ... (mail loops back to myself)
by Dmitry Makovey 18 Jan '18

18 Jan '18

Hi, I've been running Postfix+MM3 setup for a while now. However it turns out one portion of functionality has been broken all this time: member subscription via "confirmation". Quick notes on setup: I've got 2 VMs: smtp.my.com mailman.my.com I'm running mailing lists under: lists.my.com DNS for lists.my.com A: - same as mailman.my.com MX: - smtp.my.com So when somebody sends a message to foo(a)lists.my.com they receive confirmation email (which is fine and normal). That mail suggests user needs to reply to foo-confirm+randomstuff(a)lists.my.com. Whenever user does that - postfix refuses to deliver *that* mail with reason: Action: failed Status: 5.4.6 Diagnostic-Code: X-Postfix; mail for lists.my.com loops back to myself I've got transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains and postfix_domains contains: /^lists\.my\.com$/ lists.my.com and postfix_lmtp contains: foo(a)lists\.my\.com$/ lmtp:[mailman.my.com]:8024 ... what am I missing? -- Sr System and DevOps Engineer SoM IRT

3 2

Hyperkitty: AttributeError: 'NoneType' object has no attribute 'subject'
by Alex McLean 14 Jan '18

14 Jan '18

I'm getting a 500 server error with some threads in hyperkitty, e.g. this one: https://we.lurk.org/hyperkitty/list/tidal@we.lurk.org/thread/3IN5NFFFPVAQSR… The following appears in the log, any pointers much appreciated! ERROR 2018-01-13 12:29:53,855 6056 django.request Internal Server Error: /hyperkitty/list/tidal(a)we.lurk.org/thread/4ECEUJRXMJ2U7EPKRMU6V6A3FVL523BC/ Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/exception.py", line 41, in inner response = get_response(request) File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/lib/view_helpers.py", line 136, in inner return func(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/views/thread.py", line 193, in thread_index return render(request, "hyperkitty/thread.html", context) File "/usr/local/lib/python2.7/dist-packages/django/shortcuts.py", line 30, in render content = loader.render_to_string(template_name, context, request, using=using) File "/usr/local/lib/python2.7/dist-packages/django/template/loader.py", line 68, in render_to_string return template.render(context, request) File "/usr/local/lib/python2.7/dist-packages/django/template/backends/django.py", line 66, in render return self.template.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 207, in render return self._render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/loader_tags.py", line 177, in render return compiled_parent._render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/loader_tags.py", line 72, in render result = block.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 529, in render return self.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 322, in render return nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 1040, in render output = self.filter_expression.resolve(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 708, in resolve obj = self.var.resolve(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 849, in resolve value = self._resolve_lookup(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 890, in _resolve_lookup current = getattr(current, bit) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/thread.py", line 108, in subject return self.cached_values["subject"]() File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 61, in __call__ return self.get_or_set(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 57, in get_or_set value = self.rebuild(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 49, in rebuild value = self.get_value(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/thread.py", line 223, in get_value return self.instance.starting_email.subject AttributeError: 'NoneType' object has no attribute 'subject' ERROR 2018-01-13 12:29:53,855 6056 django.request Internal Server Error: /hyperkitty/list/tidal(a)we.lurk.org/thread/4ECEUJRXMJ2U7EPKRMU6V6A3FVL523BC/ Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/exception.py", line 41, in inner response = get_response(request) File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/lib/view_helpers.py", line 136, in inner return func(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/views/thread.py", line 193, in thread_index return render(request, "hyperkitty/thread.html", context) File "/usr/local/lib/python2.7/dist-packages/django/shortcuts.py", line 30, in render content = loader.render_to_string(template_name, context, request, using=using) File "/usr/local/lib/python2.7/dist-packages/django/template/loader.py", line 68, in render_to_string return template.render(context, request) File "/usr/local/lib/python2.7/dist-packages/django/template/backends/django.py", line 66, in render return self.template.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 207, in render return self._render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/loader_tags.py", line 177, in render return compiled_parent._render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/loader_tags.py", line 72, in render result = block.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 529, in render return self.nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 322, in render return nodelist.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 1040, in render output = self.filter_expression.resolve(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 708, in resolve obj = self.var.resolve(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 849, in resolve value = self._resolve_lookup(context) File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 890, in _resolve_lookup current = getattr(current, bit) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/thread.py", line 108, in subject return self.cached_values["subject"]() File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 61, in __call__ return self.get_or_set(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 57, in get_or_set value = self.rebuild(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 49, in rebuild value = self.get_value(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/thread.py", line 223, in get_value return self.instance.starting_email.subject AttributeError: 'NoneType' object has no attribute 'subject'

2 3

Django logins for new subscribers
by Alex McLean 13 Jan '18

13 Jan '18

Hi all, I'm moving our groups to mailman3 (http://we.lurk.org). Enjoying it so far! I've mass-subscribed people via postorius. However the subscribers don't have django (postorius/hyperkitty) logins. It seems they only exist on the mailman side, not the django side. If they go through the process of creating an account in postorius, they can configure their mailing list subscriptions, but this is a bit fiddly. Is this expected behaviour? It would be great if they could be sent a temporary link to set a password and go. Best wishes, alex

3 4

hyperkitty connection issues
by Dmitry Makovey 11 Jan '18

11 Jan '18

I'm using docker-based deployment of mailman. things appear to be functioning for the most part, but recently I've started getting reports from users stating that mail from *some* subscribers to the list gets queued for moderation with reason "n/a". Not sure if that's related, but I've also noticed that my logs are filling up with Connection to HyperKitty failed: ("Connection broken: ConnectionResetError(104, 'Connection reset by peer')", ConnectionResetError(104, 'Connection reset by peer')) (full dump: https://gist.github.com/droopy4096/1538d34ed7b6709252e8c3e82aaca69d ) what's the best angle to troubleshoot this situation? Note: I have restarted containers within the last 24 hours and still am observing above behavior (both mail issues and connection issues in logs) -- Sr System and DevOps Engineer SoM IRT

2 1

Hyperkitty import from mailman2
by Sten Aus 03 Jan '18

03 Jan '18

Hi I have installed mailman3 - it looks very great! Now I wanted to try import from mailman2 mbox, so i did: python2 manage.py hyperkitty_import --settings settings --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox It shows that it have sucessfully imported all emails and I can see them from database (sqlite3), but I cannot see them from GUI (hyperkitty). Only thing I can see is this inactive "test" list. I have tried that I create list before importing, still same result. All new emails are archiving to another lists (which are not imported, but new installations). Any help is appreciated! All the best Sten

4 8

Postorius 1.1.2 security release
by Abhilash Raj 29 Dec '17

29 Dec '17

Hi Everyone, I am pleased to announce that Postorius 1.1.2 is released and is up on PyPI[1]. This release fixes a security bug that sets the password of a user in Core to their display name. It is recommended that you upgrade to this version. Postorius (Django) and Mailman Core both have different notion of "user" and "password". When a user account in created in Postorius, it creates a user in Core using the REST API. This bug, causes the password of user created in Core to be set to their display name instead. However, as of now, there are no use cases of the user password in Core and it is present only for historical reasons. So, while this bug is a serious one, it wouldn't result in any real-world exploit. Along with the bug-fix, this release includes a new command that resets *all* user passwords in Core to a random value. Again, there are no use cases of these passwords so resetting *all* of them isn't going to cause any inconvenience to users. This command should be run after the upgrade: $ cd mailman-suite/mailman-suite_project/ $ python manage.py reset_passwords Python 2.7 is the only supported Python version for this release. All versions of Django <=1.11 is supported. For more information about GNU Mailman and Postorius, please see our website: http://list.org The source code is available on Gitlab: https://gitlab.com/mailman/ [1]: https://pypi.org/project/postorius -- thanks, Abhilash Raj

3 4

Schedule for a resolution of #406, #410 and #437
by Henrik Rasmussen 15 Dec '17

15 Dec '17

I was wondering when #406<https://gitlab.com/mailman/mailman/issues/406>, #410<https://gitlab.com/mailman/mailman/issues/410> and #437<https://gitlab.com/mailman/mailman/issues/437> could be fixed. It seems that it would not be far, as !322<https://gitlab.com/mailman/mailman/merge_requests/322> is ready to be merged. On another note, why doesn't mailman3.org seem to be affected by these problems, with so many members wide spread across the world, when I have at least three lists with only 1794, 646 and 317 members affected by it. -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark

3 3

help for new installation.
by claudio.jofre＠yandex.com 12 Dec '17

12 Dec '17

Hello everyone. A few days ago, I am trying to install and configure mailman 3, in a Centos7. and the truth has not been achieved. I am already a little desperate. I'll tell you First I install the hyperkitty-el.repo repository and install mailman 3, hyperkitty and postorius. Initially when reviewing and making some minor modifications to the mailman configuration file, the service apparently rises without major problems. The problem occurs when I try to configure the web interfaces. Initially the apache server did not start, with a series of errors. Following the instructions of the document published here: http://www.admin-magazine.com/Archive/2015/29/Mailman-3.0-a-long-time-comin… I managed to eliminate the initial errors, which prevented to raise the Apache server. However, when trying to access the web pages, in the case of hyperkitty, I get an error 500 with an "internal server error". In the case of postorius, I get an error 403 forbidden. In the mail, I receive a log, with the following content: Traceback (most recent call last): File "/ usr / bin / django-admin", line 5, in <module> management.execute_from_command_line () File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line utility.execute () File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 303, in execute settings.INSTALLED_APPS File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 48, in __getattr__ self._setup (name) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 44, in _setup self._wrapped = Settings (settings_module) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 92, in __init__ mod = importlib.import_module (self.SETTINGS_MODULE) File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module __import __ (name) ImportError: No module named settings In the Apache logs, it also shows the following: [Mon Dec 11 21: 48: 41.875069 2017] [authz_core: error] [pid 15333] [client my-client-ip: 33584] AH01630: client denied by server configuration: / etc / postorius / sites / default / srv when I execute the command: django-admin check throws me the following: django.core.exceptions.ImproperlyConfigured: Requested setting DATABASES, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. checking the ports, I can see that python has open ports 8000 in 127.0.0.1, and 8001 in external ip, for more than I have looked for information, documentation, etc, about the procedure of the installation. all the documentation I found, part of the premise of an installation, clean from git, by pip, but none from the yum and rpm. So it is difficult for me to determine what to apply, and what not. apparently no one has installed, or has had problems in the installation from repositories, or I am omitting some step (most likely) that I could not determine. the bad thing, is that in postfix, I have everything configured, with digital signatures, so I would not like to lose all that work, as to start with an installation from 0. If you can help me, it would be very helpful. since I made the request of help in another list, of dev, to which it is supposed that the consultations should be made, according to the historical mails, but I never received answer. Of course, thank you very much for any help and guidance they can give me.

3 7

Re: Starting new thread in Postorius -> disappears
by Cameron Smith 12 Dec '17

12 Dec '17

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

Postorius: Dropdown menus problem
by Thor Atle Rustad 05 Dec '17

05 Dec '17

In my latest iteration I installed Maxking docker-mailman by downloading the files (git clone https://github.com/maxking/docker-mailman.git) and building the images myself by modifying docker-compose.yaml like this: services: mailman-core: container_name: mailman-core build: context: ./core dockerfile: Dockerfile-alternate Same thing goes for mailman-web. Only modification was changing the uid/gid in the images to make it equal to the local user on the host. Now a few things are not working. In Postorius <server>/postorius/lists/<listname>) there is a menu row (Subscription requests|Held messages|Members|Settings|Mass operations|Banned addresses etc). The two items Members and Mass operations should normally show a drop-down menu when clicked, but here nothing happens. Same thing for the Admin menu (can't access Logout, amongst other things). In Hyperkitty, messages are not loaded properly. In various places on the page I see spinning discs indicating something is loading, but nothing happens. Any ideas? Thor

2 2

Setting up Admin Account
by Pierre Abbat 01 Dec '17

01 Dec '17

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 29 Nov '17

29 Nov '17

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 25 Nov '17

25 Nov '17

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 24 Nov '17

24 Nov '17

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 23 Nov '17

23 Nov '17

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 22 Nov '17

22 Nov '17

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 19 Nov '17

19 Nov '17

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 15 Nov '17

15 Nov '17

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 14 Nov '17

14 Nov '17

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 13 Nov '17

13 Nov '17

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 13 Nov '17

13 Nov '17

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 13 Nov '17

13 Nov '17

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