Facebook
Twitter
Mailman is available for WebAdmin as well as for WebPro and for WebHost. If you use WebAdmin, just skip this step because WebAdmin does not have ability to apply custom service plans, Plesk use default service plan without mentioned restrictions.
-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies! -
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
Question The future of mailing list management?
- Thread starter Jan
- Start date
Good news,
With Plesk Obsidian 18.0.59 release,
Feel free to leave feedback in this thread as before.
With Plesk Obsidian 18.0.59 release,
Feel free to leave feedback in this thread as before.
Hi @AYamshanov
Great news! However, I am wondering how you manage the certificate issue here and if it is vhost compatible?
Additionally, do people like me who tested the unofficial support habe to tested something?
Thanks,
Matthias
Great news! However, I am wondering how you manage the certificate issue here and if it is vhost compatible?
Additionally, do people like me who tested the unofficial support habe to tested something?
Thanks,
Matthias
Lack of built-in support HTTPS certificates and ARC headers for mailman2/3 in Plesk are known limitations of implementation for now (as well as supporting mailman3 only on two OSes).
We decided to start from this level of function because there is no degradation of functionality compared to mailman2; it allows customers to start switching to new OSes and mailman if they need to do that because of some reasons. Since 18.0.59 release, mailman3 on Debian11/12 OSes is officially supported by Plesk, it means if you have some issues with feature, you can contact with the Plesk Support team to get support.
Anyway, we have tasks to improve these aspect in the future, but currently, I can't say any ETA for that.
We decided to start from this level of function because there is no degradation of functionality compared to mailman2; it allows customers to start switching to new OSes and mailman if they need to do that because of some reasons. Since 18.0.59 release, mailman3 on Debian11/12 OSes is officially supported by Plesk, it means if you have some issues with feature, you can contact with the Plesk Support team to get support.
Anyway, we have tasks to improve these aspect in the future, but currently, I can't say any ETA for that.
(c) (Plesk for Linux) Mailman Version
We are blocked by "Bug #1999197 “mailman3 package missing in jammy, however mailman...” : Bugs : mailman3 package : Ubuntu" and because of this we can't promise anything.
Thanks a lot! Mailman3 works here now on Debian 11.9 and I can create new mailinglists on domains, that I did not use before with mailman2.
On domains, I used before with mailman2, I get this error message, when clicking on mailinglists.
Trying to deactivate mailinglists on a domain (in order to reacitvate it) is not possible and results in this error:
Error: Unable to update MailList object:Unable to turnOnOff list: listmng failed: Error: the list '[name@domain]' does not exist
Any suggestions?
On domains, I used before with mailman2, I get this error message, when clicking on mailinglists.
500 TypeError
count(): Argument #1 ($value) must be of type Countable|array, bool given| Type | TypeError |
| Message | count(): Argument #1 ($value) must be of type Countable|array, bool given |
| File | MailLists.php |
| Line | 116 |
Trying to deactivate mailinglists on a domain (in order to reacitvate it) is not possible and results in this error:
Error: Unable to update MailList object:Unable to turnOnOff list: listmng failed: Error: the list '[name@domain]' does not exist
Any suggestions?
Regarding "500 TypeError", I can say that this is already known bug (internal ID is PPPM-14338).
Dist-upgrade in Plesk does not supporting updating/migration from mailman2 to mailman3. For now I do not have any additional information, will try to find what could be done to solve it.
BTW, mailman3 has a document about migration from mailman2 (Migrating from Mailman 2.1 to Mailman 3 — Mailman Suite 3.3 documentation). From my personal point of view, and if this option is available for you, I would recommend to deploy a new server with new Debian and migrate mailman to instead of dist-upgrade of existing server. And, of, course, makes sense to make a backup before any huge task like OS upgrading!
Dist-upgrade in Plesk does not supporting updating/migration from mailman2 to mailman3. For now I do not have any additional information, will try to find what could be done to solve it.
BTW, mailman3 has a document about migration from mailman2 (Migrating from Mailman 2.1 to Mailman 3 — Mailman Suite 3.3 documentation). From my personal point of view, and if this option is available for you, I would recommend to deploy a new server with new Debian and migrate mailman to instead of dist-upgrade of existing server. And, of, course, makes sense to make a backup before any huge task like OS upgrading!
Hi @AYamshanov ,
thanks for that info but am I wrong or is mailman then not really usable?
Mailman Web will create always HTTPS / SSL errors in browsers and the default hiperkitty archive will create only errors as it cannot ignore the SSL errors as well :-(
Hello,
many thanks for including mailman3 in Plesk! I haven't had the time to check the support, yet, but I'm thinking about doing so in the next weeks. Some questions remain neverletheless.
Thanks in advance,
Jan
many thanks for including mailman3 in Plesk! I haven't had the time to check the support, yet, but I'm thinking about doing so in the next weeks. Some questions remain neverletheless.
- What is a good strategy to migrate a Debian 10 server (including mailman2) to Debian 12 with mailman 3? I have read that dist-upgrade is not a good idea, whereas mailman has a 2 -> 3 migration guide. The latter confuses me, because it is plesk and not mailman that provides the source-of-truth for the documentation. Is there, for example, a way to export / backup the current installation, set up the server from scratch and import this again? Will mailman subscription-lists, mailinglists archive, etc. be imported and exported that way? Is there a better alternative?
- I wonder why mailman's webinterface is not secured using a valid certificate. This is almost a show-stopper for me. I'm tempted to install a let's-encrypt / nginx-proxying system but I wonder why this is necessary in the first place. Do you know what is the underlaying problem?
- Is missing ARC support a sever limitation? As of today, I'm using DKIM on fields that are not changed by mailman. Is it possible to keep using DKIM?
Thanks in advance,
Jan
We are moving gradually, step by step. For now, it was necessary to provide an alternative for mailman2 because of Ubuntu18 and CentOS7 (EOL). The current set of limitations for mailman3 is the same as it was in the past for mailman2. If we were to work on fixing all known limitations, it could seriously delay the mailman3 support, but we felt that earlier access to mailman3 was a higher priority.
We know about existing limitations (Mailing Lists), some of the should be addressed in the future (SSL, ARC). Currently, there are no ETAs.
At the moment, we note that there is insufficient demand for the automated migration tool. If you think the tool is necessary, you can support the request on UserVoice, Migration/conversion tool from Mailman 2 to 3.
If you find errors that do not allow you to manually migrate data according to the guide (Migrating from Mailman 2.1 to Mailman 3 — Mailman Suite 3.3 documentation), let us know, maybe we can resolve the problem with help of the Plesk community.
We know about existing limitations (Mailing Lists), some of the should be addressed in the future (SSL, ARC). Currently, there are no ETAs.
At the moment, we note that there is insufficient demand for the automated migration tool. If you think the tool is necessary, you can support the request on UserVoice, Migration/conversion tool from Mailman 2 to 3.
If you find errors that do not allow you to manually migrate data according to the guide (Migrating from Mailman 2.1 to Mailman 3 — Mailman Suite 3.3 documentation), let us know, maybe we can resolve the problem with help of the Plesk community.
Hi,
many thanks for integrating mailman3 into plesk. I migrated the old data via plesk / backup-restore
All lists and subscribe were apparently migrated by doing so. Only a few problems remain.
I think it is better to address any backup/restore problems in a dedicated thread.
Regards, Jan
many thanks for integrating mailman3 into plesk. I migrated the old data via plesk / backup-restore
All lists and subscribe were apparently migrated by doing so. Only a few problems remain.
I think it is better to address any backup/restore problems in a dedicated thread.
Regards, Jan
sergiomb
Basic Pleskian
On RHEL 9 and RHEL 9-based , mailman3 is already available on EPEL 9 we have mailman3-3.3.8-3.el9, python-mailman-hyperkitty-1.2.1-2.el9, python-mailman-web-0.0.6-1.el9, python-django-mailman3-1.3.9-1.el9 and mailman3-fedmsg-plugin-schemas-1.0.0-2.el9 , what do I need to enable mailing lists on Plesk with AlmaLinux 9.5 ?
Thank you
Thank you
Hi sergiomb, some development on the Plesk side is required to support mailman3 on RHEL 9 and its derivatives. I will ask the team do we still have any blockers for that or not. Thank you for your question!
