system:mailman3
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| system:mailman3 [2024-08-31T13:01:07+0000] – Have to fix HyperKitty after upgrade michael_paoli_admin | system:mailman3 [2025-07-02T03:38:52+0000] (current) – Some more to complete on recording/reporting, and more notes about mailman members behavior when there are no matches michael_paoli | ||
|---|---|---|---|
| Line 150: | Line 150: | ||
| Y how do we export roster of members? | Y how do we export roster of members? | ||
| E.g.: # (for list in $(Mailman lists -a -q); do echo " | E.g.: # (for list in $(Mailman lists -a -q); do echo " | ||
| + | Note, however, if there are no matches for the specified role (or default of --role member), it will output | ||
| + | name of list with @ replaced by ., followed by text " has no members" | ||
| + | $ mailman members --role moderator balug-admin@lists.balug.org | ||
| + | balug-admin.lists.balug.org has no members | ||
| + | $ | ||
| + | And note also that's written to stdout and the exit/return value is 0. | ||
| + | So, one will probably want to filter such out from actual data results. | ||
| or via URLs, e.g. https:// | or via URLs, e.g. https:// | ||
| Y don't reject empty body (e.g. mailman commands don't require body to be present) | Y don't reject empty body (e.g. mailman commands don't require body to be present) | ||
| Line 219: | Line 226: | ||
| |Mailman 2 --> Mailman 3 http[s] redirects | |Mailman 2 --> Mailman 3 http[s] redirects | ||
| |update Mailman 2 archive locations to not link to obsolete information|n | |update Mailman 2 archive locations to not link to obsolete information|n | ||
| + | |customize templates | ||
| |update monthly stats reporting | |update monthly stats reporting | ||
| + | |fix Mailman 3 monthly data recording / stats reporting | ||
| notes/keys: | notes/keys: | ||
| Line 230: | Line 239: | ||
| * pending: handle pending as warranted (e.g. held pending moderator approval) | * pending: handle pending as warranted (e.g. held pending moderator approval) | ||
| - | |Mailman 3: fix gravatar.com information leakage | + | |Mailman 3: fix gravatar.com information leakage |
| - | |fix what I broke in attempting to fix the immediately above | + | |fix what I broke in attempting to fix the immediately above |y| |
| - | |Mailman 3: check for any additional information leaks | + | |Mailman 3: check for any additional information leaks |y| |
| - | |stop Mailman 2 services | + | |stop Mailman 2 services |
| - | |disable Mailman 2 services # systemctl disable mailman.service | + | |disable Mailman 2 services # systemctl disable mailman.service |
| - | |disable the remaining Mailman 2 aliases (mailman & mailman-*) / | + | |disable the remaining Mailman 2 aliases (mailman & mailman-*) / |
| - | |Apache 2 configuration - remove no longer relevant Mailman 2 portions | + | |Apache 2 configuration - remove no longer relevant Mailman 2 portions |
| - | |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 |
| - | |disable nntp runner | + | |disable nntp runner |
| - | |remove but **do not purge** mailman2 and no longer needed reverse dependencies packages | + | |remove but **do not purge** mailman2 and no longer needed reverse dependencies packages |
| - | |fix minor HyperKitty archive bugs present on Debian | + | |fix minor HyperKitty archive bugs present on Debian |
| - | |fix HyperKitty failure (configuration) from Debian 11 Bullseye --> Debian 12 Bookworm upgrade | + | |fix HyperKitty failure (configuration?) from Debian 11 Bullseye --> Debian 12 Bookworm upgrade |
| + | |balug-announc@lists.balug.org set users with explicit moderation of hold (imported from Mailman 2) to List default (discard) | ||
| + | |'' | ||
| + | |'' | ||
| + | |'' | ||
| + | |'' | ||
| notes/keys: | notes/keys: | ||
| Line 381: | Line 395: | ||
| Looks like that went in with HyperKitty 1.3.4: https:// | Looks like that went in with HyperKitty 1.3.4: https:// | ||
| Debian 10.13 --> 11.10 gave us upgrade python3-django-hyperkitty: | Debian 10.13 --> 11.10 gave us upgrade python3-django-hyperkitty: | ||
| - | So, should now be able to fix the gravatar issue. | + | 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' | ||
| Minor HyperKitty archive bugs on Debian 11 Bullseye | Minor HyperKitty archive bugs on Debian 11 Bullseye | ||
| From archive page, e.g.: https:// | From archive page, e.g.: https:// | ||
| Line 388: | Line 404: | ||
| once there, clicking on a year shows the months under year, but those immediately collapse before one can click on any of those months, | 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. | this seems to be the case regardless of browswer. | ||
| - | These issues weren' | + | These issues weren' |
| + | 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 / | ||
| + | templates: | ||
| + | from mailman3 package: / | ||
| + | formatting of templates is not consistent, see also: | ||
| + | https:// | ||
| + | for some templates (e.g. list: | ||
| + | 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: | ||
| + | / | ||
| + | / | ||
| + | it shows folding at 70 | ||
| + | looks like wrap is applied to (at least): | ||
| + | list: | ||
| + | list: | ||
| + | list: | ||
| + | list: | ||
| + | And does //not// fold: | ||
| + | list: | ||
| + | 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: | ||
| + | appears templates may be preserved much closer to unchanged, e.g. lines not joined nor folded, just variable substitutions applied | ||
| + | 'da Internet sayeth: | ||
| + | https:// | ||
| + | Some but not all templates are wrapped at column 70 by the function at | ||
| + | https:// | ||
| + | Those that are wrapped are: | ||
| + | list: | ||
| + | list: | ||
| + | list: | ||
| + | list: | ||
| + | list: | ||
| + | list: | ||
| + | list: | ||
| + | list: | ||
| + | list: | ||
| + | list: | ||
| + | Others are not. For those that are wrapped, there are techniques to | ||
| + | avoid wrapping. In particular, lines beginning with whitespace aren' | ||
| + | wrapped | ||
| VM: debian10mailman23 | VM: debian10mailman23 | ||
| select documentation: | select documentation: | ||
system/mailman3.1725109267.txt.bz2 · Last modified: 2024-08-31T13:01:07+0000 by michael_paoli_admin