Dear list,
When migrating the lists and archives from Mailman 2.1 to Mailman 3, the e-mail templates were obviously not migrated. Is there a way to make up for this?
Kind regards, Markus Grandpré
-- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342
Markus Grandpré writes:
When migrating the lists and archives from Mailman 2.1 to Mailman 3, the e-mail templates were obviously not migrated.
Which templates? Headers and footers are in the database, and they should be migrated. The standard templates for autoreplies, moderator notifications, and so on will have versions appropriate for Mailman 3, and as far as I know all of the languages standard in Mailman 2 have been translated to Mailman 3, or the Mailman 2 version crudely adapted to Mailman 3.
Do you mean custom templates (such as moderator noifications) that overwrote stock templates in the Mailman 2 installation? I would think you would have to copy those by hand, because the upgrade process would not know that they're customized, and would just assume the new installed versions are good for you. I'm pretty sure you can copy them to a different place that has higher precedence in the search path so you don't have to worry about them being overwritten by upgrades.
Unfortunately Mark is on vacation.
Steve
Dear Stephen,
Thank you for your prompt reply. Based on a customer request, it seems that custom templates need to be copied manually. Could you kindly indicate which files and locations should be considered when transferring them from the source to the target system?
Best regards, Markus
Am 3/5/25 um 15:01 schrieb Stephen J. Turnbull:
Markus Grandpré writes:
When migrating the lists and archives from Mailman 2.1 to Mailman 3, the e-mail templates were obviously not migrated.
Which templates? Headers and footers are in the database, and they should be migrated. The standard templates for autoreplies, moderator notifications, and so on will have versions appropriate for Mailman 3, and as far as I know all of the languages standard in Mailman 2 have been translated to Mailman 3, or the Mailman 2 version crudely adapted to Mailman 3.
Do you mean custom templates (such as moderator noifications) that overwrote stock templates in the Mailman 2 installation? I would think you would have to copy those by hand, because the upgrade process would not know that they're customized, and would just assume the new installed versions are good for you. I'm pretty sure you can copy them to a different place that has higher precedence in the search path so you don't have to worry about them being overwritten by upgrades.
Unfortunately Mark is on vacation.
Steve
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to markus.grandpre@uni-konstanz.de
-- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342
On 3/6/25 2:24 PM, Markus Grandpré wrote:
Thank you for your prompt reply. Based on a customer request, it seems that custom templates need to be copied manually. Could you kindly indicate which files and locations should be considered when transferring them from the source to the target system?
In MM 2.1, you could have list specific templates in directories like lists/<listname>/<language>/, domain specific templates in directories like templates/<list.host_name>/<language> and sitewide templates in directories like templates/site/<language>.
In MM 3 You can create list and domain specific templates in Postorius or you can create them in sub-directories of Mailman's var/templates/ directory. List specific templates in lists/<list-id>/<language>/, domain specific templates in directories like domains/<mail-host>/<language>/ and sitewide templates in directories like site/<language>/.
However, you can't just copy MM 2.1 templates because the variable replacement syntax is different and the template file names are different. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/t... for documentation of the MM 3 templating system.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Mark Sapiro -
Markus Grandpré -
Stephen J. Turnbull