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

Which crontab?
by Pierre Abbat Nov. 15, 2017

Nov. 15, 2017

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

2 10

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

Nov. 14, 2017

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

3 6

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

Nov. 13, 2017

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

2 1

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

Nov. 13, 2017

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

4 15

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

Nov. 13, 2017

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

2 1

Bounces
by David Krantz Nov. 7, 2017

Nov. 7, 2017

Hi. How do I config mailman 3.1x to send any unrecognized bounces to e.g. the list owner? Now they just end up in the bounces table but I would like to see the entire message in this case. Cheers // David

2 3

LDAP/Krb5/SAML auth for Mailman
by Dmitry Makovey Nov. 7, 2017

Nov. 7, 2017

Can anyone share some information on LDAP/Krb5 or better yet SAML auth implementation for Mailman. Is it just adding appropriate auth module to DJango project or is there more involved things? -- Sr System and DevOps Engineer SoM IRT

2 1

configuring moderators per list
by Dmitry Makovey Nov. 7, 2017

Nov. 7, 2017

We're trying to configure moderator per list and so far we were only able to add "superuser" accounts that can handle "Held messages", "Members", "Banned addresses" etc. Is there a way to create special account per-list to manage some of the aspects of particular ML without giving them all the permissions that Superuser comes along with? In MM2 there was a ML password that moderator/list admin would use to login to perform operations. Current setup allows list admins to add/delete existing lists which is not desired. -- Sr System and DevOps Engineer SoM IRT

3 3

disabling social login
by Dmitry Makovey Nov. 6, 2017

Nov. 6, 2017

Hi, I'm trying to disable social login and running into troubles stepping on it's remnants all over the place. What's the proper sequence for disabling social login in MM3 install? -- Sr System and DevOps Engineer SoM IRT

3 4

Message shows up individually but not in the thread
by Marvin Gülker Nov. 4, 2017

Nov. 4, 2017

Hi, I've just observed something weird. While some users were testing the new mailman setup, the reply did not make it into the corresponding thread, but is still associated with it. That is, the message does not show up in the thread page at[1]. However, the reply is visible if requested individually[2]. Now what's weird is that in [2] there's a link at the top that says "< thread" that takes one to [1], so there is some kind of association appearently made but only in one direction (the reverse one). mailman.log has this to say: Nov 03 17:22:31 2017 (498) ACCEPT: <1fa6f9e1-254c-e999-42d0-9a6cc263020d(a)openmailbox.org> Nov 03 17:22:32 2017 (507) 127.0.0.1 - - "GET /3.0/users/sydneyjd(a)openmailbox.org HTTP/1.1" 200 305 Nov 03 17:22:32 2017 (495) HyperKitty archived message <1fa6f9e1-254c-e999-42d0-9a6cc263020d(a)openmailbox.org> to https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… The mailman-suite log contains: INFO 2017-11-03 17:22:32,910 14330 hyperkitty.views.mailman Archived message <1fa6f9e1-254c-e999-42d0-9a6cc263020d(a)openmailbox.org> to https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… This looks to me like a bug. The OP of that thread sent the same message to our other mailinglist[3] (where he did not get a reply), so Mailman may has been confused by that. Marvin [1]: https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… [2]: https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… [3]: https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

2 8