- Mailman-users - lists.mailman3.org

Any known limit of number of lists that one can be owner/member of?
by Alan So May 15, 2019

May 15, 2019

We have just migrated hundreds of lists from Mailman 2 to Mailman 3. It was smooth in most of the cases. However, we just notice that there are some abnormal behaviour of Postorius for particular users who are owner/member of a large number of lists. We further look into a particular user who is owner of 84 lists. When the user login Postorius, only 50 lists are displayed no matter what the number of "Results per page" is chosen. Prev/Next page cannot be clicked as there is only 1 page. When I use the following mailman client snippet, it also displays the same 50 lists: lists = client.find_lists('xxx(a)yyy.com', 'owner') for m_list in lists: print(m_list.fqdn_listname) Did we hit any limit of find_lists? Is it a bug or are something wrong during the migration? When the user use "Mailman settings", the page can still display all lists though (it's slow as it probably did a lot of SQL queries!).

2 7

Re: Archive Policy not reflecting in Hyperkitty
by Abhilash Raj May 14, 2019

May 14, 2019

Are you using images with "rolling" tags? If yes, you should try to switch to "0.2" tag and the new release will be tagged with the same one. To update, you can do: $ docker pull ... $ docker pull .. $ docker-compose stop $ docker-compose rm $ docker-compose up -d This should basically get you up and running with the new image you pulled. -- thanks, Abhilash Raj (maxking)

2 2

Archive Policy not reflecting in Hyperkitty
by Nathan Dixon May 7, 2019

May 7, 2019

So the issue I am seeing is that when I set a lists archive policy to prviate, it isn't reflecting that in Hyperkitty. I am running the docker installation of Mailman, postorius and hyperkitty. So I go into the docker instance of mailman-core and run this: python3 manage.py shell from hyperkitty.models.mailinglist import MailingList MailingList.objects.all().values_list('name', 'archive_policy') And all my lists are showing '2', regardless of how I set the mailing list archive policy. This might be a duplicate of https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Am I missing something in my install? Or is this a bug? Many thanks for your attention, -- *Nathan Dixon* MEng Senior Software Architect m: +44 (0)7402 690311 t: +44 (0)20 81231252 e: nathan.dixon(a)evadon.com w: www.evadon.com This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and not necessarily those of Evadon. Please note that whilst we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free. Please be advised that we expressly reserve the right to monitor email content for the purposes of ensuring compliance with legal requirements and company policies and your sending to, or receiving from, us of any email constitutes your agreement to these terms. Evadon Dynamics Limited, registered in England No. 09494097. Registered Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, S1 2BJ

3 5

Moderate mails from owner
by Henrik Rasmussen May 7, 2019

May 7, 2019

I assume this is by design, but is it correct that a list owner, who are not member, will always be allowed to post to the list, even though "Default action to take when a member posts to the list" and "Default action to take when a non-member posts to thelist" are both set to "Hold for moderation"? The owner is set as also moderator, by the way, which seems redundant. I have a list administrator who would like to be moderated when sending to the list, but there is no Member Options on Owners (nor Moderators). A workaround may be to create a new account for the owner and let the current owner be member instead of owner, as she will then be moderated. /Henrik Rasmussen

4 16

Creating and placing custom templates
by kelly.close＠lrewater.com May 2, 2019

May 2, 2019

I know there are previous threads related to this topic but none were very recent so I thought I'd start a new one. I've referenced two of the old ones below. I am attempting to implement a custom footer on one of my lists. This seems like it should be straightforward but I'm clearly doing something wrong, since the default footer keeps coming through despite my efforts. I've referenced the docs as well as these two posts, to no avail. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Here's what I'm doing: I found my templates folder and verified it matched what is set in the mailman.cfg file - on my Ubuntu Bionic system it is /var/lib/mailman3/templates/ In that folder I created the following folders and made sure they were properly owned (by list:list) /var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/ Into that en/ folder I placed a file called "list:member:regular:footer" It is a text file with just one line of text in it (a link to a website). Also, because there was a mention in one of the earlier posts that this file should have a .txt extension, I also put the same file in there named "list:member:regular:footer.txt". I have two of my own emails subscribed t my "f2p2-test" list at the domain udfcd-lists.org. When I post to the list, and check my other email for the disseminated post, it still has the default footer. I have restarted the mailman3 service. Can anyone spot an obvious error here or offer troubleshooting suggestions? Thank You! ~Kelly

2 1

We're in Season of Docs!
by Stephen J. Turnbull May 1, 2019

May 1, 2019

So, we're in Season of Docs! Currently, Abhilash and I are registered as mentor/admins. I don't think we need more admins, but more mentors is always a good thing. Hey, users! You don't need to be a programmer to mentor docs, of course, and it may be a *good* thing to *not* be a programmer and even *not* a Mailman developer. :-) Suggestions as to doc projects we *really oughtta do!* are very welcome. (I can't believe we got in with the thin doc proposal I put together literally at the last minute, but here we are. ;-) Feel free to get in touch with us on mailman-developers (reply-to set; please respect) if you're interested in mentoring. Or if you prefer you can contact me or Abhilash directly. We can presumably add mentors up to July 23 (deadline for technical writer selection by orgs). For more information: https://wiki.list.org/DEV/SeasonOfDocs2019 https://developers.google.com/season-of-docs/ https://developers.google.com/season-of-docs/docs/participants/ https://developers.google.com/season-of-docs/docs/timeline Regards, Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

1 0

GDPR - save subscriptions confirmation emails
by contact＠maadix.net May 1, 2019

May 1, 2019

Hi, I am new in the list. I have been looking for this topic in the archives in order to avoid duplicate, but I could not find any thread. According to the new GDPR rules, lists owners need to have a confirmation from subscribers, and this is easy to do with Mailman 3. What I can't figure out is how to save all the confirmation emails received from users. I only see the confirmations commands emails in the logs, Is there another place/way to store them? For GDPR compliance it is important to be able to demonstrate that you received the confirmation, in case you may need it in the future. Bests Maddish -- *MaadiX* Tu nube en tus manos https://maadix.net https://twitter.com/MaadiXnet

3 4

HTML email sent to lists migrated from Mailman 2.1
by Nate Coraor April 16, 2019

April 16, 2019

Hello all, I have some lists migrated from 2.1 that are stripping the HTML parts (perhaps all attachments?) from messages despite the options to do so not being enabled and lynx not even being installed. I'm trying to get a new list to behave the same way so I can figure out what's going on without spamming a production list, but have been unsuccessful: despite setting nearly all the list options the same as the old lists, new lists pass HTML portions and attachments just fine. I've verified the settings using mailing list objects directly with `mailman withlist` on the command line and the only differences are things that I can't imagine would be related like admin_notify_mchanges, advertised, and archive_policy. Are there are really old options that can't be accessed via mailing list objects obtained with `withlist` on the command line? Thanks, --nate

3 3

Mailman in EC2 / Docker -- working but HTTPS not serving static content
by roger.hislop＠is.co.za April 15, 2019

April 15, 2019

Hi again ... I got everything working thanks to Danil, Abhilash, and finally found a simple NGINX conf that worked, using WSGI. Cool. Set up certificates using LetsEncrypt, used another conf to set up SSL, like the conf pasted below. I edited nginx.conf so that it only takes server config from the nginx/conf.d/blahblah.conf below. This works for HTTP, HTTPS works but it (apparently) is not serving static content. There are loads of how-tos to get this to work, but I've failed in all -- it seems to be the static path (I've not tried option using thttpd I've not tried as there is no easy install onto AQWS AMI and it seems like it's not specifically necessary. I'm so close... so close... ------------------------------- server { listen 80 default_server; # listen [::]:80 default_server ipv6only=on; root /usr/share/nginx/html; index index.html index.htm; server_name listman.iotcouncil.org.za; return 301 https://$server_name$request_uri; #<< AUTO_REDIRECT HTTP TO HTTPS # location / { # proxy_pass http://172.19.199.3:8000/; # proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; # proxy_set_header X-Forwarded-Host $host; # proxy_set_header X-Forwarded-Server $host; # proxy_set_header X-Forwarded-Proto $scheme; # proxy_redirect off; # } # # location /static/ { # alias /var/spool/mailman-web/static/; # } # # location /robots.txt { # alias /var/spool/mailman-web/static/hyperkitty/robots.txt; # } # # location /favicon.ico { # alias /var/www/listorg/images/favicon.ico; # } # } server { listen 443 default_server; # listen [::]:443 default_server ipv6only=on; #root /usr/share/nginx/html; #index index.html index.htm; server_name listman.iotcouncil.org.za; ssl on; ssl_certificate /etc/letsencrypt/live/listman.iotcouncil.org.za/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/listman.iotcouncil.org.za/privkey.pem; ssl_session_timeout 5m; ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers "HIGH:!aNULL:!MD5 or HIGH:!aNULL:!MD5:!3DES"; ssl_prefer_server_ciphers on; location / { proxy_pass http://172.19.199.3:8000/; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } location /static/ { alias /opt/mailman/web/static; } location /robots.txt { alias /var/spool/mailman-web/static/hyperkitty/robots.txt; } location /favicon.ico { alias /var/www/listorg/images/favicon.ico; } }

4 3

Mailman Core 3.2.2 is now out
by Abhilash Raj April 14, 2019

April 14, 2019

Hello Everyone, Mailman Core 3.2.2 is released and available on PyPI[1]. This is a regular bugfix release and I had to do that to fix a version constraint which pulled in a pre-release of a dependency (falcon) when installed via pip and caused the default install to break. There are few other changes included in this release, including a big refactor of error reporting in Core's REST API. All the error responses are now correctly formatted as JSON with more information about the error. For example, invalid inputs for Enum data types return the valid options. Other error message are now generated from the input validtor and will be more informative. REST API also accepts input as JSON formatted body, alongside the x-www-form-urlencoded. A full list of changes are available here: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 This release supports Python 3.5-3.7. Thanks very much to all the contributors involved in this release. [1]: https://pypi.org/project/mailman/ -- thanks, Abhilash Raj (maxking)

2 3