Search results for "Postorius" - Mailman-users

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, 4 months

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.

8 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

11 months, 3 weeks

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

9 months, 3 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, 8 months

Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 11:56 AM, David Newman wrote: > > I created a pending subscription request on a test list. Here is the > text I'm using in a file called 'list:admin:action:subscribe.txt' (minus > the rows of hypens): > > ---------- > > > As list administrator, your authorization is required for a mailing list > subscription request approval: > > For: $member > List: $listname > > At your convenience, visit: > > https://${domain}/mailman/admindb/lists/${short_listname}.${domain}/ This looks like a Mailman 2.1 URL. Are you sure you don't want something like https://${domain}/mailman3/lists/${short_listname}.${domain}/ > > to approve or deny the request. > > ---------- > > Instead the message that goes out at midnight daily reads like this: That's a different message. It is sent from the `mailman notify` command run by cron. It's built from the list:admin:notice:pending template. > > On successive nights I have placed copies of the > 'list:admin:action:subscribe.txt' file above in these locations: > > mm/var/templates/lists/test.lists.domain.tld/en I hope you mean /opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en > /opt/mailman/mm/var/templates/site/en Either of those should work. The lists one will take priority over the site one for that list. > and then in Postorius, with the same contents as above. If you set a template in Postorius, it takes priority. If you later decide you want to use one in /opt/mailman/mm/var/templates/ you have to delete the postorius one. > The file > versions are owned by the mailman user, and have 0644 permissions. Not > sure this is necessary but I've restarted the mailman3 and mailmanweb > services each time after a change. > > There is no sign of trouble in the MM3 or web logs. The only thing I see > is in the Postfix log, where the shorter and less helpful message goes > out each night. I don't see anything in the template docs about this. > > Questions: > > 1. What to do to get the custom message working? It should work. I suspect you need to go to the list's Settings -> Automatic Responses and set `Admin immed notify` to Yes. > 2. Is there a way to trigger a subscribe reminder for one list only? If by subscribe reminder you mean the `list:admin:action:subscribe.txt` message, yes that's the above list setting. If you mean the one sent from the `mailman notify` command, see `mailman notify --help` for the options. You can specify one or more lists (default is all lists) via options and put them in your cron. > Asking because there are other lists on this server with other requests > pending, and I don't want to bother other moderators with multiple > reminders per day. Not a big deal, but it would be nice to test this > with one list rather than waiting up to 24 hours after each change. You can test `mailman notify` at any time by running it by hand. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

Re: What's the difference between (purpose of) reject and ignore

by denis.bitouze＠univ-littoral.fr

Yes, that's what I meant, thanks. AFAICS, it is not documented since, at Postorius → Settings → Message Acceptance → Default action to take when a (non-)member posts to the list, I only read: “Discard: this simply discards the message, with no notice sent to the post's author”. So no mention that this would set it to (silently) discard all future mails from them. Just to be sure: for this feature, is it necessary to click on the subject and to choose in the drop-down list “Discard (no notification)”, or is it enough, on the .../held_messages page, to select the messages and click on “Discard”?

3 years, 11 months

Re: FW: You have been invited to join the ssan@lists.ccalternatives.org mailing list.

by Mark Sapiro

On 6/9/25 07:07, Odhiambo Washington via Mailman-users wrote: > The template is named list:user:action:invite. You can create it either > from Postorius or on the filesystem at > /opt/mailman/mm/var/templates/lists/LISTNAME/en/list:user:action:invite.txt Given the age of the OP's system (see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…) I suspect it's a Debian/Ubuntu package or perhaps another package and it's unlikely that Mailman's var/ directory is /opt/mailman/mm/var/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

Re: List Migration from MM2.1 -> MM3

by Odhiambo Washington

On Mon, Aug 15, 2022 at 4:59 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/15/22 06:53, Odhiambo Washington wrote: > > > > That is exactly what I have in my mailman.cfg > > > > Installing Postfix suppresses that message though. I installed Postfix > and > > then disabled it. > > > > > Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman > core than the one reading that mailman.cfg and the one Postorius is > talking to. > How can I track the one it's talking to? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 10 months

Re: list of subscribers

by Peter Münster

On Sun, Feb 04 2018, Simon Hanna wrote: > You should be able to use mailmanclient to get a list of subscribers with > names. It seems, that mailmanclient does not know about the real name (the first name and the last name in Django). But this seems to work: from django.contrib.auth.models import User user = User.objects.get(email='address(a)of.user') print(user.first_name) print(user.last_name) So, I'll try to make some loop over a list with email addresses, that I can get on the web interface. > Names are optional though, if people signup without them you won't be able to > get them. My usage of mailman is perhaps a bit special: users can't sign up, only the site owner signs up manually with create_user(email=, first_name=...) Then the site owner creates the mailing lists and uses mass subscription (for example all members of a basketball team). At one moment, the list of subscribers should be verified by all members, just to be sure, that nobody got forgotten. > Currently there is no option to require names. I'll open an issue in > postorius about showing the name in the member list if there is one > associated. Thanks. It would be nice, to see the first_name and the last_name of the django-auth user object. > IIRC one person(postorius account) can also signup at different lists using > different names (regardless of address). You mean the "display_name" of mailmanclient here? I won't use it. For my usage, I prefer a clear association of email, first name and last name in one account, no need for "display_name" here. > There was some discussion about names and potentially using the from header to > populate the database but I don't remember the result... Nice idea, especially for the normal use case, the public mailing list (but not for mine). Off topic: I have "Receive own postings = Yes", but I don't receive copies of my postings to this list... Kind regards, -- Peter

8 years, 4 months

Mailman-users search results for query "Postorius"