On 5/28/25 01:14, Mark wrote:
Then I created a template using Postorius and updated the uri in mailman.templates to:
file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt - and that works.
Which says get the template from the file system at that location and don't ask for it from Postorius at all. This would be the default action if there were no entry for this template in the mailman.template table at all. I.e. you now have a template in Postorius, but it is not used.
It's looking promising. Now I just need to modify my script that periodically copies the data from the "mailmanweb.postorius_emailtemplate" table to a file and updates the uri.
Why it won't handle the templates in the database I don't know. But at least I can get a work-around solution in place now.
If you want to continue to use the template at /opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt just delete the template from Postorius and update that file directly.
If Postorius template updates don't work because of web server caching or whatever, just don't use them and use templates in the /opt/mailman/mm/var/templates/ hierarchy instead. You can create sitewide templates at /opt/mailman/mm/var/templates/site/en/*, domain specific templates in /opt/mailman/mm/var/templates/domains/en/* and list specific templates in /opt/mailman/mm/var/templates/lists/<list-id>/en/ without any entries in the mailman.template table.
Note that sitewide templates can be the most useful and can't be created in Postorius anyway.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan