BALUG-Test

balug-test@lists.balug.org

1 participants
175 discussions

test - ignore Check database timezone behavior
by Michael Paoli 20 Aug '24

20 Aug '24

Check database timezone behavior 2024-08-20T09:35:01+00:00 Tue, 20 Aug 2024 09:35:01 +0000 Tue Aug 20 09:35:01 2024 2024-08-20T02:35:01-07:00 Tue, 20 Aug 2024 02:35:01 -0700 Tue Aug 20 02:35:01 2024

1 0

gravatar.com leakage
by Michael Paoli 19 Aug '24

19 Aug '24

Yeah, I notice at least by default on at least the Mailman 3 hyperkitty archive, it "leaks" information to gravatar.com using per-member URLs for images from gravatar.com ... ugh. Yeah, looks like I'm not the first to notice this: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Anyway, one more item to add to migration checklist of things to do, and from the above, looks like it's probably not too difficult to manage to do. Michael Paoli wrote: > Mailman 2 --> Mailman 3 ... largely (but not entirely) done; holler if > one notes any issues. > > Summary on status/progres can be found here: > https://www.wiki.balug.org/wiki/doku.php?id=system:mailman3#mailman_2_--_... > > There were some glitches, notably with import21 ... > and did find a work-around(/fix?) for that, > and also had some issues with archive import+indexing, > but seem to have made it past all that now (though still have > some more validation checks to do, etc.). > > And note that thus far, the merging of archive from the > (temporary) balug-test3(a)lists.balug.org to > balug-test(a)lists.balug.org is still pending. > In the meantime, those archives are available here: > https://lists.balug.org/mailman3/hyperkitty/list/balug-test3@lists.balug.... > And the balug-test3(a)lists.balug.org is also mostly locked down > to prevent changes (no new postings or subscription/membership changes).

1 0

Mailman 2 --> Mailman 3 ... largely (but not entirely) done; holler if one notes any issues.
by Michael Paoli 19 Aug '24

19 Aug '24

Mailman 2 --> Mailman 3 ... largely (but not entirely) done; holler if one notes any issues. Summary on status/progres can be found here: https://www.wiki.balug.org/wiki/doku.php?id=system:mailman3#mailman_2_--_3_… There were some glitches, notably with import21 ... and did find a work-around(/fix?) for that, and also had some issues with archive import+indexing, but seem to have made it past all that now (though still have some more validation checks to do, etc.). And note that thus far, the merging of archive from the (temporary) balug-test3(a)lists.balug.org to balug-test(a)lists.balug.org is still pending. In the meantime, those archives are available here: https://lists.balug.org/mailman3/hyperkitty/list/balug-test3@lists.balug.or… And the balug-test3(a)lists.balug.org is also mostly locked down to prevent changes (no new postings or subscription/membership changes).

1 0

Re: Rats ... some hyperkitty_import issue(s) ...
by admin＠bclug.ca 19 Aug '24

19 Aug '24

Michael Paoli via BALUG-Test wrote on 2024-08-18 01:34: > So, seems it accepted and indexed them ... but for some reason isn't > yet showing them in hyperkitty - though it lets me download them > from the archive. You've probably tried this already, but: mailman-web update_index -h or mailman-web update_index_one_list -h rb

2 1

Re: And so it begins (well, only one teeny oops so far) Re: Welcome to the "BALUG-Test" mailing list
by admin＠bclug.ca 18 Aug '24

18 Aug '24

Michael Paoli via BALUG-Test wrote on 2024-08-18 01:30: > Just using the Debian packages. I think they include the venv setup, > but haven't poked into the details to see exactly how they function in > that regard. There should be approaching *zero* Debian packages installed! From my brain-addled notes: ## Use PG, not MySQL! Change next line per venv instructions online: apt install default-libmysqlclient-dev build-essential ## More Debian package(s): sudo apt install libpcre3 libpcre3-dev Various notes follow, the TL;DR is above regarding which repo packages to install. Everything gets installed inside a venv with pip! sudo useradd --create-home \ --home-dir /opt/mailman \ --shell /bin/bash \ mailman sudo chown -v mailman: /opt/mailman sudo chmod -v 755 /opt/mailman sudo -i -u mailman bash -c "python3 -m venv venv; echo 'source /opt/mailman/venv/bin/activate' >> /opt/mailman/.bashrc; exit" sudo -i -u mailman bash -c "pip install wheel mailman PyMySQL" ## Run as sudo: mkdir /etc/mailman3 touch /etc/mailman3/mailman3.service touch /etc/mailman3/mailman-hyperkitty.cfg ## This is about the only Debian / Ubuntu packages to install: ## And, screw messing with MySQL, PostgreSQL all the way: apt update ## Use PG, not MySQL, change next line per venv instructions online: apt install default-libmysqlclient-dev build-essential ## Is this run as mailman? I *think* so, inside the venv: pip install mailman-web mailman-hyperkitty ## As user mailman inside venv: MAILMAN_WEB_CONFIG=/etc/mailman3/mailman-web.py mailman-web migrate MAILMAN_WEB_CONFIG=/etc/mailman3/mailman-web.py mailman-web collectstatic MAILMAN_WEB_CONFIG=/etc/mailman3/mailman-web.py mailman-web compress MAILMAN_WEB_CONFIG=/etc/mailman3/mailman-web.py mailman-web compressmessages pip install uwsgi ## create & edit /etc/mailman3/uwsgi.ini: ## You can run test run uwsgi using the following command: ## ## (venv)$ uwsgi --ini /etc/mailman3/uwsgi.ini uwsgi --ini /etc/mailman3/uwsgi.ini ## NOTE: if /opt/mailman/web/logs/uwsgi-error.log (?) has this: ## !!! no internal routing support, rebuild with pcre support !!! ## then... ## pip uninstall uwsgi ## More Debian package(s): sudo apt install libpcre3 libpcre3-dev pip install --force-reinstall -U --no-deps --no-cache-dir uwsgi Next and last: Xapian full-text search. ## Xapian full-text search ################################### ## Xapian full-text search ################################### ## Xapian full-text search ################################### ## ## Latest version: 1.4.25 ## Inside (venv) as mailman: export XAPIAN_VERSION="1.4.25" mkdir /tmp/mailman/xapian -vp cd /tmp/mailman/xapian curl https://raw.githubusercontent.com/notanumber/xapian-haystack/master/xapian_w> bash xapian_wheel_builder.sh $XAPIAN_VERSION ls -l *.whl wheelFile=$(ls *.whl) pip install ${wheelFile} xapian-haystack unset wheelFile rm -fr /tmp/mailman/xapian > /dev/null echo "Edit /etc/mailman3/settings_local.py and add HAYSTACK_CONNECTIONS" ## DO NOT OVERLOOK XAPIAN-HAYSTACK IN LINES ABOVE!!! ## DO NOT OVERLOOK XAPIAN-HAYSTACK IN LINES ABOVE!!! ## DO NOT OVERLOOK XAPIAN-HAYSTACK IN LINES ABOVE!!!

1 0

Re: Rats ... some hyperkitty_import issue(s) ...
by admin＠bclug.ca 18 Aug '24

18 Aug '24

Michael Paoli via BALUG-Test wrote on 2024-08-18 00:04: > Rats ... some hyperkitty_import issue(s) ... imports some emails > perfectly fine, others it just quietly fails to import. Sounds like you're getting really close! I do see something running `mailman-web help hyperkitty_import` about another cleanup tool: > Before running this, the mbox(es) should be checked for messages that > could throw uncaught exceptions with the contrib/check_hk_archive > script and for unescaped 'From ' lines with Mailman 2.1's cleanarch > script. > Oh well, ye olde "divide and conquer" - shouldn't be too hard to > figure out what's tripping it up. I figure you'll have it figured out before this gets sent. Good luck, rb

2 1

Re: And so it begins (well, only one teeny oops so far) Re: Welcome to the "BALUG-Test" mailing list
by admin＠bclug.ca 18 Aug '24

18 Aug '24

Michael Paoli via BALUG-Test wrote on 2024-08-17 22:41: > For the curious, there's also: > https://www.wiki.balug.org/wiki/doku.php?id=system:mailman3#mailman_2_--_3_… Nice documentation. At a quick glance, did you forego the 'venv' method and go with packages from repo? Word of warning, it's not supported and anyone with issues is sent to Debian (etc.) for support on the MM3-users mailing list. The 'venv' method is *strongly* advised. rb

2 1

Rats ... some hyperkitty_import issue(s) ...
by Michael Paoli 18 Aug '24

18 Aug '24

Rats ... some hyperkitty_import issue(s) ... imports some emails perfectly fine, others it just quietly fails to import. Oh well, ye olde "divide and conquer" - shouldn't be too hard to figure out what's tripping it up.

1 0

And so it begins (well, only one teeny oops so far) Re: Welcome to the "BALUG-Test" mailing list
by Michael Paoli 18 Aug '24

18 Aug '24

Oops ... I should've turned off the notification before migration ... from Mailman 2 to Mailman 3. Yes, those migrated may have gotten a notification even if/when already subscribed. Did a "mass subscription" on Mailman 3, notably hazardously non-trivial to rename existing list on Mailman 3, so, on Mailman 3, created "new" (matching existing on Mailman 2) list balug-test(a)lists.balug.org But also merging (since hazardously non-trivial to rename) the (temporary) balug-test3(a)lists.balug.org into balug-test(a)lists.balug.org and for the existing members on balug-test3(a)lists.balug.org did a "mass subscribe", for those on balug-test(a)lists.balug.org that used Mailman's import21. Shouldn't have that issue with the other list migrations (there's no existing Mailman 3 target to rename or merge with the existing old Mailman 2 lists to be migrated). For the curious, there's also: https://www.wiki.balug.org/wiki/doku.php?id=system:mailman3#mailman_2_--_3_… See also: https://lists.balug.org/pipermail/balug-talk/2024-August/000251.html https://lists.balug.org/pipermail/balug-announce/2024-August/000346.html On Sat, Aug 17, 2024 at 9:57 PM <balug-test-request(a)lists.balug.org> wrote: > > Welcome to the "BALUG-Test" mailing list! > > To post to this list, send your email to: > > balug-test(a)lists.balug.org > > You can unsubscribe or make adjustments to your options via email by > sending a message to: > > balug-test-request(a)lists.balug.org > > with the word 'help' in the subject or body (don't include the > quotes), and you will get back a message with instructions. You will > need your password to change your options, but for security purposes, > this password is not included here. If you have forgotten your > password you will need to reset it via the web UI.

1 0

test post
by KLH IC 31 Jul '24

31 Jul '24

Thank you for the invite. Is this just an internally focused test of internal mail?

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
18
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

BALUG-Test