- Mailman-users - lists.mailman3.org

UI changes in Hyperkitty
by Abhilash Raj 02 Apr '19

02 Apr '19

Hi All, I have been working this past weekend trying to change some UI elements of Hyperkitty to make it a bit more cleaner, easier to read quoted emails and make unread posts more visible than they were before. As a test bed, I have deployed my changes to lists.mailman3.org[1]. A complete summary of changes is available in my MR[2] on Gitlab. I would appreciate some feedback from users to make sure that is is a step in the right direction. Since it has been a long long time since I ever designed a UI, I would also really appreciate if there people who want to work with me on fixing some of the UX issues in Hyperkitty. Summary of Changes: --------------------------------- - The grey background for the email headers are removed. - Gravatars are now round in shape instead of square. - Links to permalink of the message and fixed-font button has been moved to the bottom to remove clutter from the top of the message. - The date format is changed to remove the Day of the week and uses 3 letter month names for minimalism. - Right sidebar is now fixed and doesn't scroll with the page. - All buttons on the bottom of the email now have a hover property that changes their background on mouse hover. - Quoted part of the email now has a different background. Each level of quoting gets a different background till 3-levels of indentation. After, which we don't process more quoted text. - Unread threads show a blue bar on the left side as a more prominent indication as compared to current envelope icon. [1]: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ [2]: https://gitlab.com/mailman/hyperkitty/merge_requests/132 Feel free to reply here or just comment on MR in Gitlab. -- thanks, Abhilash Raj (maxking)

3 2

mail stuck in "out" queue
by Dmitry Makovey 30 Mar '19

30 Mar '19

I've had encountered this situation now twice: mail is being stuck in "out" queue and nothing in the logs indicates the issue. Is there a way to ask mailman-core politely to attempt delivery (perhaps with increased debugging in the logs) *without* restarting the core (which does solve *this* problem but creates other problems, like availability of the mailman as a whole) -- Sr System and DevOps Engineer SoM IRT

2 1

Delete archive of mailing list
by Torge Riedel 28 Mar '19

28 Mar '19

Hi list, I've successfully set up mailman3 in a test environment and deleted a test list which I only used for some basic tests. Looking at the archiver, the archive is still there and I haven't found a way to delete it. Although I am logged in as admin. Is there a (non-) official way to delete the archive? I want a clean environment for the later user to test mailman3. Thanks and regards Torge

2 2

Introducing Mailman Web project
by Abhilash Raj 26 Mar '19

26 Mar '19

I have been working on a new sub-project Mailman Web[1][2]. This project basically combines Postorius and Hyperkitty together in a single package which you can easily use to serve Mailman's web interface. The basic motivation behind this was to make it simpler for people to install the web interface *and* make it easier for people to configure Mailman's web ui. Both Postorius and Hyperkitty are based on Django Web Framework, which uses settings.py as its default configuration language. While it is quite convenient for Python developers to be able to put Python statements in configuration to join/edit/configure settings. However, I think a traditional INI, or TOML style configuration is easier for non-developers without having to worry about PYTHONPATH, valid Python sytax etc, etc. For this reason, I decided to combine all the projects together into a Django project which can be easily installed and run: $ pip install mailman-web # Export Settings for commands to just work. $ export DJANGO_SETTINGS=mailman_web.settings $ django-admin migrate $ django-admin runserver This should get you default settings for running. If you want to customize your installation, which you almost always would need to in a prod environment, you can create a config file at one of these locations (which are searched in following order): - /etc/mailman-web.toml - /etc/mailman3/mailman-web.toml - ./mailman-web.toml Note that we support only TOML as the configuration language[3][4] because of its simplicity. I would have loved to use INI, like Mailman Core, but it turns out to be way too simple to represent more complex data structures like maps and tables, that is commonly used in Django's Settings. This project is currently in alpha stage (I created it today!), but can be installed with pip[5] and in my basic tests works. There isn't much in the project itself beyond some configurations. I also took this opportunity to document all the settings that are used in Mailman Web (both Postorius and Hyperkitty) together[6]. This is documented in code and so I really hope that it won't go out of date like many other places ;-) Improvements to docs is very welcome, just a modification of a comment and is quite easy to propose right in your web browser using Gitlab! Any questions, comments or suggestions are welcome. You can open issues for feature requests on gitlab[1] too. [1]: https://gitlab.com/mailman/mailman-web [2]: https://mailman-web.readthedocs.io/en/latest/ [3]: https://github.com/maxking/django-settings-toml [4]: https://github.com/toml-lang/toml [5]: https://pypi.org/project/mailman-web/ [6]: https://mailman-web.readthedocs.io/en/latest/settings.html -- thanks, Abhilash Raj (maxking)

2 6

Configuring the List-Archive and Archived-At headers
by Ralph Seichter 25 Mar '19

25 Mar '19

With archiving enabled, mail is sent with headers like the following: Archived-At: <https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/> List-Archive: <https://example.com/hyperkitty/list/foo-users@lists.example.com/> List-Post: <mailto:foo-users@lists.example.com> List-Subscribe: <mailto:foo-users-join@lists.example.com> The 'mailto:' entries are fine, but I need all 'https:' links to be prefixed with https://lists.example.com instead of https://example.com . Does Mailman extract CN parts from the SSL certificate to populate the header values (that would explain 'example.com' in my tests), or is this something I can influence using configuration parameters? I searched the docs for Mailman Suite and HyperKitty, but did not find an answer. -Ralph

5 9

Non resolved placeholders in action message
by Torge Riedel 23 Mar '19

23 Mar '19

Hi, after adding a new moderator to a list I get the following message in a green box: %(email)s has been added with the role %(role)s Looks like the placeholders are not resolved (correctly). Should I report this somewhere as a bug? Mailman Core Version GNU Mailman 3.2.0 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.6.7 (default, Oct 22 2018, 11:32:17) [GCC 8.2.0] Best regards Torge

2 1

State of STARTTLS/SMTPS support?
by Ralph Seichter 21 Mar '19

21 Mar '19

Hello list. I just found https://gitlab.com/mailman/mailman/issues/252 and was surprised to see that a) the issue is two years old and b) a related merge request has been submitted a year ago and is also still open. The possibility to send mail unencrypted via localhost is something I have in a test environment, but not in production. I need to be able to specify settings that look like these: [mta] smtp_host: outbound-mta.mydomain.tld smtp_port: 587 smtp_security: STARTTLS When is STARTTLS/SMTPS likely to become available in Mailman? -Ralph

2 2

How to best disable message decoration for all lists defined for a domain
by Ralph Seichter 19 Mar '19

19 Mar '19

Hello list. I have read [1] and [2], but I am not quite sure what the recommended method is to completely disable message headers/footers and subject modifications for *all* lists tied to a specific domain. Being new to Mailman 3, I was actually surprised that there are no configuration switches in the Web UI's settings for mailing lists that allow me to get rid of unwanted message decorations. [1] https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/decorate… [2] https://mailman.readthedocs.io/en/latest/build/lib/mailman/rest/docs/templa… Thanks for your input. -Ralph

3 4

REST Runner (and other runners) taking long time to boot up
by Dmitry Makovey 18 Mar '19

18 Mar '19

splitting this discussion into it's own thread from "MM3 occasionally chokes (?)". Re-iterating background info for posterity: we have been experiencing increasingly long boot ups from mailman-core over the past year to the point where it's at about 45min for the sequence to complete. We run couple of mailing lists (20+) that are anywhere between 100 and 10K+ members and most of them are low traffic. From what I can tell all that time is spent doing some sort of indexing operations, I'm writing from memory since I can't restart the system to confirm that. sizes of directories that containers use: 3.6G core 352M database 285M web state of my queues (as far as I understand how to evaluate them: $ for q in core/var/queue/*; do echo ${q}; ls ${q}/ | wc -l ; done core/var/queue/archive 1 core/var/queue/bad 3845 core/var/queue/bounces 0 core/var/queue/command 0 core/var/queue/digest 0 core/var/queue/in 0 core/var/queue/nntp 0 core/var/queue/out 7 core/var/queue/pipeline 0 core/var/queue/retry 1 core/var/queue/shunt 958 core/var/queue/virgin 0 what kind of tuning should we be looking into to speed up our boot-ups? -- Sr System and DevOps Engineer SoM IRT

2 1

Maximum number of recipients error
by brian＠emwd.com 18 Mar '19

18 Mar '19

I am unable to modify the "Maximum number of recipients" setting. It generates the following error when I click the "save changes" button: "An error occured: Unknown attribute: max_num_recipients" I am using the docker version of MM3 and its happening on "Postorius Version 1.2.3". Is this a known bug? Brian

3 2