-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/13/2013 01:29 PM, Ian Eiloart wrote:
Repeating what I already wrote for completeness here: Migrating and then going back all at once is not necessary. You can migrate bit by bit, although it may require a little bit of manual fiddling if you get to the point of installing both on a production server.
The tricky bit here is the continuity of the web interfaces. If a list manager is used to going to lists.example.com/Mailman/listname, and they have that bookmarked, then they’ll want to keep going to that same place.
Likewise, with the list archives, and all the list users. We have 1312 lists, perhaps two or three thousand list admins, and tens of thousands of users.
Postorius' URL config does allow for some customization, but I doubt it will be easily possible to style list summary URLs to match the MM2-style "mailman/listinfo/{list name}" URLs. The reason is that Postorius uses the "list-id" property as unique identifier in URLs which is generally different to the list names used in MM2-URLs.
What we could do though (possibly as part of the migration routine) is to auto-generate rewrite rules for major web servers like Apache/nginx/... redirecting MM2-style URL requests to the new ones (using HTTP status code 301, which would also tell search engines that the change is permanent).
Florian