Differences

This shows you the differences between two versions of the page.

--- system:mailman3 [2024-08-25T04:57:24+0000] – removed (not purged) Mailman 2 package (mailman) michael_paoli_admin
+++ system:mailman3 [2024-09-19T04:03:13+0000] (current) – +Debian bug # michael_paoli_admin
@@ Line 219: / Line 219: @@
 |Mailman 2 --> Mailman 3 http[s] redirects                             |ir  |ir   |ir  |ir      |
 |update Mailman 2 archive locations to not link to obsolete information|n   |n    |n   |n       |
+|customize templates                                                   |i   |i    |i   |i       |
 |update monthly stats reporting                                        |-   |  y              |||
@@ Line 230: / Line 231: @@
   * pending: handle pending as warranted (e.g. held pending moderator approval)
-|Mailman 3: fix gravatar.com information leakage                                                       |n|
+|Mailman 3: fix gravatar.com information leakage                                                                                        |y|
-|fix what I broke in attempting to fix the immediately above                                           |y|
+|fix what I broke in attempting to fix the immediately above                                                                            |y|
-|Mailman 3: check for any additional information leaks                                                 |n|
+|Mailman 3: check for any additional information leaks                                                                                  |y|
-|stop Mailman 2 services    # systemctl stop mailman.service                                           |y|
+|stop Mailman 2 services    # systemctl stop mailman.service                                                                            |y|
-|disable Mailman 2 services # systemctl disable mailman.service                                        |y|
+|disable Mailman 2 services # systemctl disable mailman.service                                                                         |y|
-|disable the remaining Mailman 2 aliases (mailman & mailman-*) /etc/aliases                            |y|
+|disable the remaining Mailman 2 aliases (mailman & mailman-*) /etc/aliases                                                             |y|
-|Apache 2 configuration - remove no longer relevant Mailman 2 portions                                 |y|
+|Apache 2 configuration - remove no longer relevant Mailman 2 portions                                                                  |y|
-|fix what I broke in the immediately above, notably links so static web archive content will still work|y|
+|fix what I broke in the immediately above, notably links so static web archive content will still work                                 |y|
-|disable nntp runner                                                                                   |y|
+|disable nntp runner                                                                                                                    |y|
-|remove but **do not purge** mailman2 and no longer needed reverse dependencies packages               |y|
+|remove but **do not purge** mailman2 and no longer needed reverse dependencies packages                                                |y|
+|fix minor HyperKitty archive bugs present on Debian 12 Bullseye                                                                        |n|
+|fix HyperKitty failure (configuration?) from Debian 11 Bullseye --> Debian 12 Bookworm upgrade                                         |y|
+|balug-announc@lists.balug.org set users with explicit moderation of hold (imported from Mailman 2) to List default (discard)           |y|
+|''mailman3 start --force'' bug: identify manual work-around (remove lock links in /var/lib/mailman3/locks/)                            |y|
+|''mailman3 start --force'' bug: report/analysis/test: [[https://gitlab.com/mailman/mailman/-/issues/1174|GNU Mailman Core Issue #1174]]|y|
+|''mailman3 start --force'' bug: test and apply local fix                                                                               |y|
+|''mailman3 start --force'' bug: report bug to Debian: [[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082167|#1082167]]           |y|
 notes/keys:
@@ Line 371: / Line 379: @@
           provides users (members), their passwords, and options.
     Before migrating list archive, check, clean, etc., see: https://docs.mailman3.org/en/latest/migration.html#id2
+    Mailman 3 gravatar information leakage
+      HyperKitty archive pages are (at least by default) served up with links to gravatar.com
+      (looks like) they leak information to gravatar.com - looks like each link is (probably) a hash of the user/member's email address
+      Earlier versions of Mailman 3 don't have a "fix" for that.
+      Later versions allow it to be disabled in configuration:
+        https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mailman_web.settings.mailman.HYPERKITTY_ENABLE_GRAVATAR
+        Looks like that went in with HyperKitty 1.3.4: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-4
+        Debian 10.13 --> 11.10 gave us upgrade python3-django-hyperkitty:all 1.2.2-1+deb10u1 --> 1.3.4-4
+        So, should now be able to fix the gravatar issue (and was earlier fixed and confirmed fixed).
+    Mailman 3 information leakage?
+      After fixing the gravatar issue and reasonably checking again, seems there's no longer information leakage present (yay!)
+    Minor HyperKitty archive bugs on Debian 11 Bullseye
+      From archive page, e.g.: https://lists.balug.org/mailman3/hyperkitty/list/balug-test@lists.balug.org/
+      clicking the Threads by month dropdown doesn't do anything.
+      After clicking All Threads which goes to, e.g. https://lists.balug.org/mailman3/hyperkitty/list/balug-test@lists.balug.org/latest
+        once there, clicking on a year shows the months under year, but those immediately collapse before one can click on any of those months,
+        this seems to be the case regardless of browswer.
+      These issues weren't present on Debian Buster 10, and hopefully are fixed by Debian 12 Bookworm
+    balug-announc@lists.balug.org set users with explicit moderation of hold (imported from Mailman 2) to List default (discard)
+      as user list:
+      (umask 022 && unset LC_ALL && LANG=en_US.UTF-8 export LANG && sqlite3 /var/lib/mailman3/data/mailman.db "UPDATE member SET moderation_action = NULL WHERE list_id = 'balug-announce.lists.balug.org' and moderation_action = 0;")
+    templates:
+      from mailman3 package: /usr/lib/python3/dist-packages/mailman/templates/en/*.txt
+      formatting of templates is not consistent, see also:
+        https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/templates.html
+      for some templates (e.g. list:user:notice:welcome)
+        empty line starts a new paragraph
+        Adjacent non-empty lines that don't start with space may be joined
+          partial workaround - appears if the line starts with a space it won't be joined to the preceding, however that leading space isn't stripped
+        long lines may be folded - mailman documentation says at 72 characters but appears this happens at 70
+      Debian:
+        see also:
+          /usr/lib/python3/dist-packages/mailman/utilities/string.py
+          /usr/lib/python3/dist-packages/mailman/app/notifications.py
+        it shows folding at 70
+        looks like wrap is applied to (at least):
+          list:user:notice:welcome (confirmed)
+          list:user:notice:goodbye
+          list:user:notice:warning
+          list:member:digest:masthead (confirmed)
+        And does //not// fold:
+          list:member:regular:footer (confirmed)
+        looks like also for those templates where wrapping is applied,
+        source comments imply if the paragraph starts with whitespace, wrapping won't be applied to the paragraph - but seems the comments lie,
+        need each line to start with whitespace (which is preserved) to not have the line folded, also prevents it from being joined to preceding line.
+      for other templates (e.g. list:member:regular:footer)
+        appears templates may be preserved much closer to unchanged, e.g. lines not joined nor folded, just variable substitutions applied
+      'da Internet sayeth:
+        https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/RWHXDB7D562YSWP67Y5CVQYDOFCLW6TM/
+        Some but not all templates are wrapped at column 70 by the function at
+        https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/string.py#L102
+        Those that are wrapped are:
+        list:admin:action:subscribe
+        list:admin:action:unsubscribe
+        list:admin:notice:pending
+        list:user:notice:goodbye
+        list:user:notice:hold
+        list:user:notice:no-more-today
+        list:user:notice:probe
+        list:user:notice:refuse
+        list:user:notice:warning
+        list:user:notice:welcome
+        Others are not. For those that are wrapped, there are techniques to
+        avoid wrapping. In particular, lines beginning with whitespace aren't
+        wrapped
   VM: debian10mailman23
 select documentation: