BALUG-Test

balug-test@lists.balug.org

1 participants
171 discussions

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

Re: test - ignore (post, archive, delete, reimport)
by admin＠bclug.ca 26 Jul '24

26 Jul '24

Michael Paoli via BALUG-Test3 wrote on 2024-07-19 01:51: > hyperkitty_import -lbalug-test3(a)lists.balug.org import.single.mbox) That... should've been obvious as it's how one imports lists after all. > $ (unset LC_ALL && LANG=en_US.UTF-8 export LANG && /usr/share/mailman3-web/manage.py I set up user mailman's .bashrc file so I can just `sudo -u mailman bash` and have everything set up so I can run mailman and mailman-web commands. Anyway, have you fully migrated the lists? I'm still in a "I've migrated everything but not made MM3 live yet" some number of months after starting. Dunno why. rb

2 1

Re: test - ignore (post, archive, delete, reimport)
by admin＠bclug.ca 19 Jul '24

19 Jul '24

Michael Paoli via BALUG-Test3 wrote on 2024-07-18 01:02: > Then reimported the message (and reindexed) and it's back again fine. How, pray tell, did you re-import the message? I didn't know this could be done and have no idea how to go about it. rb

2 1

test - ignore (post, archive, delete, reimport)
by test-trnzipzntiaotvhgjmee＠balug.org 18 Jul '24

18 Jul '24

1721289353

2 1

Initial BALUG-Test3 posting
by aaronco thirtysix 18 Jul '24

18 Jul '24

A bit interesting b/c even before further adjusting BALUG-Test3 mailing-list subscriber settings, could already view prior archived postings directly via https://lists.balug.org/mailman3/hyperkitty/list/balug-test3@lists.balug.or… by way of the [possibly] more private Tor browser. Already able to view by Tor all of BALUG's mailing lists at https://lists.balug.org/ including the "older" specific Mailman 2 BALUG-Test list https://lists.balug.org/cgi-bin/mailman/listinfo/balug-test While can similarly access via the Tor browser the Bay Area's technically-related Noisebridge Hackerspace ( https://www.noisebridge.net/wiki/Noisebridge ), and even that as a non-subscriber, cannot similarly access Oakland's NB-variant and no doubt fluorishing SudoRoom ( https://sudoroom.org/ ) Its Tor browser 403 error msg consistently displayed as: ~~~~~~~~~~~~~~~~~~~~ quoting ~~~~~~~~~~~~~~~~~~~~ "403 - Forbidden. Note: Tor has been blocked from accessing this website due to spammer abuse. Please connect without a proxy for access. Contact sudo-discuss-owner AT sudoroom DOT org if you believe this is a mistake." ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ One idea for Michael Or Other Possible BALUG.org Admins(*) pending any possible BALUG-lists-targeting spammers, is similarly as sudoroom.org to consider blocking Tor if that should prove necessary(?) * the MOOPBA's is of course _not_ the pithy name of a leadoff band preluding the Rolling Stones's big Wednesday concert at Levi's Stadium! ;-D

2 1

← 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