Edward Hasbrouck
My feedback
3 results found
-
29 votesEdward Hasbrouck
supported this idea
·
An error occurred while saving the comment -
27 votes
An error occurred while saving the comment Edward Hasbrouck
commented
Yes. This should be part of automated migration. Until this is implemented, users should be warned that these settings will not be migrated, and weill need to be recreated manaually.
-
293 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.— rk
An error occurred while saving the comment Edward Hasbrouck
commented
Yes. This is essential for any Web service.
Mailman is, for me, an essential component of my Plesk server. The difficulty of manually migrating mailman settings for all lists (I had to do it once before, and it was poorly documented and difficult to do without spamming list subscribers unintentionally due to reset to default settings and change of announcement lists to discussion lists) is a major obstacle to migrating from CentOS 6 to a newer underlying OS for my Plesk server. For me, migrating mailing list *settings* is more important than migrating archives. But all should be included in a Plesk migration. And, as others have noted, in the meantime, there should be a clear warning that these won't be migrated.