- Mailman-users - lists.mailman3.org

Starting from scratch
by Benjamin Ragheb 12 Apr '18

12 Apr '18

Hello! Over the weekend, I attempted to install the Mailman Suite on Debian Stretch. My goal is to set up some low volume mailing lists for family and friends. I ran into some problems, and I'm hoping to get some feedback on my overall approach before I make my second attempt. :-) I figured the safest thing to do would be to use pip to install the latest released version of all the components (core, postorius, hyperkitty, etc.). I copied the files from the [mailman-suite repository][1] to set up a Django project and got it mostly working with Apache and mod_wsgi. [1]: https://gitlab.com/mailman/mailman-suite Unfortunately, I was unable to log into the web interface; when I tried, I got a server error like this: > Exception Type: TypeError at /accounts/login/ > Exception Value: authenticate() takes exactly 0 arguments (3 given) Some research leads me to believe this is happening because authenticate() was changed in Django 1.10, and so I must be using a newer version of Django than the app expects. Given that I installed via Pip, I assumed the right version of Django would automatically be installed... I'm open to the possibility that I am misunderstanding how Pip works, or that postorius's and/or hyperkitty's dependency information is incorrect. The two alternatives I am weighing right now are: 1. Stay the course, and see if I can fix this by learning more about Python, Pip, Django and tinkering with the configuration. 2. Ride the bleeding edge, and install postorius and hyperkitty from git. (I'll probably stick with Mailman Core from Pip, since that seemed to work just fine.) Right now I'm leaning toward #2, because it means I'll be in a better position to patch things if I need to, and it seems like Mailman 3 is still rough enough that I will need to. Also, it looks like the master branches of both postorius and hyperkitty are now Python 3 compatible, which could save me from managing two different versions of Python. Which is the least crazy option? -- Ben

2 2

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