Search results for "Postorius" - Mailman-users

Re: Upgrading other python packages than the mailman ones in a venv results in dependency conflicts

by Mark Sapiro

On 12/16/24 03:03, Andreas Vetter wrote: > > OK. So what about --upgrade-strategy eager: > > pip install -U --upgrade-strategy eager mailman postorius django-mailman3 > hyperkitty mailman-web > > Is that allowed/supported? Yes it is recommended if you want to upgrade dependencies and if you have a recent version of pip. Older versions of pip don't support that option but their default behavior is the same as newer versions with --upgrade-strategy eager. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Hyperkitty - not sending from GUI & reply-thread

by sunil soprey

With latest release (HK 1.3.1), does anyone have an issue with no emails from reply-thread? I able to send/receive emails to/from mailman. I see MTA delivered emails, just no emails from HK GUI. No errors logs (py exception) nor mailman. ideaS? Versions: mailman-hyperkitty (1.1.0) - Mailman archiver plugin for HyperKitty INSTALLED: 1.1.0 (latest) HyperKitty (1.3.1) - A web interface to access GNU Mailman v3 archives INSTALLED: 1.3.1 (latest) mailman (3.3.0) - Mailman -- the GNU mailing list manager INSTALLED: 3.3.0 (latest) postorius (1.3.1) - A web user interface for GNU Mailman INSTALLED: 1.3.1 (latest) django-mailman3 (1.3.1) - Django library to help interaction with Mailman INSTALLED: 1.3.1 (latest) mailmanclient (3.3.0) - mailmanclient -- Python bindings for Mailman REST API INSTALLED: 3.3.0 (latest) f

6 years, 7 months

Re: Mailing list name with capital letters?

by Mark Sapiro

On 9/26/23 12:00, Mark London wrote: > I guess this is not possible? If you mean create a list with upper case in it's list_id or list posting address, you are correct, but since in your OP you said "Right now, only the first letter can be capitalized." you must be talking about the list's display name. That can be set in Postorius at Settings -> List Identity per my reply at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. It can also be set via REST or mailman shell. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

Re: General question mailman3: message sender acceptance "always"

by Wikinaut

Mark Sapiro wrote: > On 10/23/23 05:41, Wikinaut wrote: > > I could not find such an option (in the moderation dialog) in Mailman3 (only "accept" or "reject" and "discard", but "accept and add to white-list = accept always"). > > In the Postorius held messages view, click on the message's subject to > open a dialog showing the messages content Dear Mark, sorry: How should I know this? I'd rather prefer to have these both changes: i) relabel the existing one od three buttons from "accept" to "accept once" ; and ii) add a fourth button "accept all messages from this sender (i.e. add to white list)"

2 years, 9 months

Re: Adding a domsin

by Mark Sapiro

On 1/13/20 1:33 PM, Allan Hansen wrote: > > It’s mostly working but the Postorius page and the ‘noreply’ emails still sport the old domain name. I hav looked at all the py and cfg files where the old name appeared, and they no longer hold the old name. My coadmin now tells me that the database has a table with the old name. Any suggestion as to whether that can cause the issue and if it’s safe to change the table. Look in Mailman's var/templates/directory. I suspect you have a site/en/ subdirectory with templates containing the old name. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

Re: Language Support In Templates

by Mark Sapiro

Mark Sapiro wrote: > > This is a bug in Postorius. I just reported it at > https://gitlab.com/mailman/postorius/-/issues/465. I have deleted that bug report as it appears the language attribute in the postorius_emailtemplate table is unused anyway. Notices built from templates are sent by core in the appropriate charset, that of the list's preferred language for admin notices and the either the user's or the list's preferred language for user notices. (Un)sibscribe confirmations are sent in the list's preferred language. In Brian's case the (default) charset for Greek is UTF-8, so if the template was encoded as UTF-8 and the list's preferred language was Greek, it should not have been garbled.

5 years, 6 months

Re: Caching problem with templates

by Mark Sapiro

On 6/28/25 22:05, Mark wrote: > > Setting the cache_life to a zero value only writes the expiry date as > "now". The cached file is still there. And it doesn't appear to be > getting overwritten (as expected) when the template is edited. The template caching occurs on retrieval. Editing the template in Postorius does not change the URI in the template table, so a subsequent retrieval still gets the old cached value. The task runner will delete the expired template the next time it runs but with default settings that's up to an hour later. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

Re: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Mark Sapiro

On 8/25/25 15:07, Flo via Mailman-users wrote: > > In /usr/share/mailman3-web/settings.py there is: > > INSTALLED_APPS = ( > ... > 'django.contrib.humanize', > ... > ) Then I don't understand why you are getting the error. django.contrib.humanize is required because it is referenced by django-allauth in templates here https://codeberg.org/allauth/django-allauth/src/commit/5baeee79b2915dbb881d… and here https://codeberg.org/allauth/django-allauth/src/commit/5baeee79b2915dbb881d… If django.contrib.humanize is loaded, those references should be satisfied. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

Re: Migrating to Mailman3

by Dennis Putnam

On 10/17/2025 3:09 AM, Stephen J. Turnbull wrote: > dap1--- via Mailman-users writes: > > > I am about to migrate from mailma2 on CentOS to mailman3 on > > Ubuntu. Are there any special gotchas of which I need to be aware? > > TIA. > > * The Ubuntu packages are old, and not well-supported by Ubuntu or the > Mailman project. Mailman 3 is not a hyperactive project, but we are > making steady progress and many new Mailman 3 users have issues or > requests for enhancement for 2-, 3-year-old packages that have been > fixed or implemented in the most recent releases. For these reasons, > we strongly recommend installing from source or from PyPI in a virtual > environment: > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > (Installing from source is not hard, but it's more work than using > pre-built packages. Source is required for beta testers and > developers, but not recommended for most production environments.) > > * If your preferred RDBMS is in the MySQL family: > 1. Make sure the Mailman database(s) have the utf8mb4 charset option > set. Otherwise all emoji and some Asian characters will cause > your database to throw errors (I think this is mostly an issue for > HyperKitty and maybe a few users who put them in their display > names in Postorius and Mailman core). This is not needed for > PostgreSQL or SQLite3. > 2. You may want to increase the timeout for startup (I think this is > in the systemd units for mailman and mailmanweb). The issue is > that the mysqld doesn't exit until the journal has been flushed to > the main database (or something like that), and this may take many > seconds. This is not an issue for SQLite3 (it's a library) or > PostgreSQL (it uses dbus to notify systemd that it's ready). > > * The migration scripts for list database and web databases are quite > good, but not 100%. > > * The user model is completely different. Ordinary subscribers will > probably be happy or won't notice, but there are some traps for > administration roles. The most important is that some list owners > will give the owner password to moderators so they can do work like > use mass subscribe, but put them on the moderator list attribute so > they get the moderation notices. These moderators will lose the > "owner" capabilities like mass subscribe. > > * If you're looking at a multinode installation with Mailman core, > Postorius and HyperKitty distributed across several hosts or > containers, configuration can be finicky. I don't recommend it unless > you're familiar with such distributed operations. > > Steve > Hi Steve, Thanks for the info. I thought I had followed everything but I an unable to start mailman3 because all the expected directories in /var are missing. What steps did I miss? The instructions are a bit confusing because I had to keep switching between mailman and admin for setting up various files such as /etc/mailman3. There was no step to make mailman a sudoers. I hope I didn't mess up the installation by switching back and forth.

9 months, 2 weeks

Re: Ann: Mailman Core 3.3.5 is out

by Brett Delmage

On Wed, 29 Sep 2021, Eggert Ehmke via Mailman-users wrote: > Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I would have > to bypass the Debian installer. Or will there be Debian packages available? > Same question for Postorius 1.3.6 I am excited to see 3.3.5 with its many updates available. Thanks to all the contributors. I would like to know this too, as I was just about to install parallel to the Debian package(s). I expect there are many of us. Going forward, what is the best way to maintain a stable version of 3.3.5 with security and defect fixes only, exluding new features? Is picking and applying individual checkins on gitlab the only way? Brett

4 years, 10 months

Mailman-users search results for query "Postorius"