MegaBrutal via Mailman-users writes:
> Stephen J. Turnbull <[email protected]> ezt írta (időpont: 2026. márc. 26.,
> Cs, 8:37):
> Hmm, probably I set "Hírlevél" for the list's title or something
> (it means "newsletter").
Dman, you caught me, off-by-one error there. :-) (That's just a joke,
I thought "position 21" refers to the *first* character in the
substituted string.)
> > You can try to use UTF-8 instead by adding
> >
> > [language.en]
> > charset: utf-8
> >
>
> Where do I set this? Just append to settings.py?
No, that's in mailman.cfg. I need to get with Mark and Abhilash and
find out what the "practical problems" are with universal UTF-8. (I
think there are probably still Linux systems out there that support
only ASCII in server configurations.)
> I don't have this variable defined, so it's probably using the
> default. I shall add it with 128.8.0.1:8000 then... But it didn't
> help! Restarted the mailman service, but it still wants to fetch
> the template from localhost. May it be hardcoded?
Mailman depends on at least *four* services if the full suite is
active:
mailman: configured in mailman.cfg, handles mail and list database
mailmanweb: configured in settings.py, handles web UI and auth stuff
qcluster: configured somewhere (sorry! defaults are always good enough
as far as I know), handles HyperKitty periodic jobs like
re-indexing the archives
cron: configured in /etc/cron.d/mailman*, handles other periodic jobs
(obviously cron is a generic service)
It's probably a good idea to restart mailman and mailmanweb (might be
spelled differently such as mailman-web) at the same time. Changes to
mailman.cfg *require* a restart of mailman, changes to settings.py
*require* a restart of mailmanweb.
> To be fair, in the past I was trying to set my mailing lists to my
> native language, but then I found that many templates have no
> translation. In cases like this, most software just falls back to
> English, which would be fine for my use case. However, Mailman
> doesn't: I just noticed that empty automatic notifications are
> being sent out.
Mark explains this, it's basically a problem with how we ingest the
output of the translation processing software our volunteers use. We
should find a way to fix that.
> Yeah, it might not be a big deal, but 8000+ ports are often used
> for various local HTTP services, I may have another one running on
> 127.0.0.1:8000. Then true there are many ports being available, so
> I could just pick a different one, but using a dedicated localhost
> IP like 127.8.0.1 looked just nicer. I can immediately identify the
> listen ports belonging to Mailman;
Whatever works for you is good. I stick with default hosts and
configure ports and lsof(1) is my friend
root@somehost:~# lsof -i tcp@localhost:8000-8999
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
opendkim 544 opendkim 3u IPv4 17238 0t0 TCP localhost:8891 (LISTEN)
> Is this the official bug tracker on Launchpad?
> https://bugs.launchpad.net/mailman
No, I'm not sure why we left Launchpad (probably because it didn't do
git and for quite a while arch/baz/bzr/brz was quite a mess -- and
still is in Mac/Homebrew, btw), but the Mailman 3 repos are on GitLab:
https://gitlab.com/mailman/ and we use the issue tracker there, such
as https://gitlab.com/mailman/mailman/-/issues/.
Steve
--
GNU Mailman consultant (installation, migration, customization)
Sirius Open Source https://www.siriusopensource.com/
Software systems consulting in Europe, North America, and Japan
_______________________________________________
Mailman-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/[email protected]/message/4OGTYOPUYHXPTGQXEABWMNVMJ5VH3AQP/
This message sent to [email protected]
