On Sat, Mar 16, 2024 at 6:00 PM Stuart Henderson <stu.li...@spacehopper.org> wrote:
> On 2024-03-16, Odhiambo Washington <odhia...@gmail.com> wrote: > > > > On Sat, Mar 16, 2024 at 3:57=E2=80=AFPM Mark <markbsdmail2...@gmail.com> > wr= > > ote: > > > >> On Wed, Mar 13, 2024 at 5:44=E2=80=AFPM Odhiambo Washington > <odhiambo@gma= > > il.com> > >> wrote: > >> > >>> > >>> This is why I suggested he should run Mailman3 from the word go. > >>> > >>> > >>> > >> It looks almost impossible to setup Mailman3 on OpenBSD. > >> > >> No, this is not working at all; > >> https://xn--gckvb8fzb.com/mailman3-on-openbsd-71/ > >> > >> Any other tutorial I could try? > >> > >> Thank you. > >> > > > > What exactly isn't working for you? > > Yes, this is a key thing when asking questions. Saying "No, this is not > working at all" followed by a URL is not much help. Copy text from > a terminal, showing _what commands you ran_ and _what you saw_. > > > The setup is actually pretty easy. > > mailman itself should be fairly easy to get installed in a venv, but > mailman-web pulls in cryptography and that can be problematic sometimes. > Trying to build that via pip isn't working at the moment in -current: > > error: failed to run custom build command for `openssl-sys v0.9.99` > ... > This crate is only compatible with OpenSSL (version 1.0.1 > through 1.1.1, or 3), or LibreSSL 2.5 through 3.8.1, but a > different version of OpenSSL was found. The build is now > aborting due to this version mismatch. > > - so you'll probably have better luck by installing py3-cryptography > from packages (when built in ports, openssl-sys is automatically > patched to fix this problem), and when you create the venv, use > --system-site-packages to allow the system package to be used. > > *However*, if you're doing this on a system which already has various > python packages installed, using this may result in some conflicts with > other software, so if you run into problems from that and can't > uninstall the relevant package, you may need to use a fairly clean > machine. > > (The ideal thing would be to get mailman updated to 3.x in ports, > but looking at 'pip list' after installing mailman and mailman-web > in a venv, there are 84 modules installed, getting on for 40 not > in ports yet, and some of the others probably need updating - > possibly with a ripple effect on other ports - so it's a lot of > work; running in a venv with most things installed via pip is > a saner option). > >From my own experience, running Mailman3 from OS packages/ports is fraught with pain. It's also not supported by the Mailman Developers. I have seen admins using Linux packages suffering from them. I am new to OpenBSD, but have used FreeBSD for decades and still saw lots of suffering getting Mailman3 installed from the ports. I had to settle for the virtualenv option and found it to be rock solid. The official documentation for Mailman3 is so Linux-centric and recommends virtualenv <https://docs.mailman3.org/en/latest/install/virtualenv.html> option. It's pretty easy to setup. For the *BSD the biggest challenge is how to launch the processes (mailman core and mailman-web) on system startup. However, there are ways: supervisord, cron, etc. I use a startup script on my FreeBSD server. I use Exim as MTA, Apache as the web server. I am positive that @Mark <markbsdmail2...@gmail.com> will manage fairly easily with the virtualenv method I shared previously. He can use the OpenBSD-centric applications as documented or opt for the *easier* ones like I do on FreeBSD :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
