• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Mailman configuration missing

P_heck

Basic Pleskian
Hello,

one problem:

I have setup a mailing list some months ago in one domain. Now I want to change the settings, as I got sometimes the following error:

Message body is too big: 41629 bytes with a limit of 40 KB

I looked for the place to set this in the panel and found in the help section the following instruction:

To set up the mailing list administrator's account from your control panel:
Go to Tools & Settings > Set Up Mailing Lists Server (in the Resources group).
Specify the username and password that you will use for administration of mailing lists and their settings.
Click OK.

Unfortunately, this menu item is missing! Mailman is installed, I can see it at the server components:

mailman 1:2.1.13-5

Also the domain http://lists.domain.tld/cgi-bin/mailman/admindb/mailing is not available (domain.tld is for sure substituded by my domain name).

Looks for me, that Mailman is not completely integrated within the Plesk panel, nevertheless - it is working for the configured mailing list.

Does anyone know, how I can fix this?

Ciao
Peter
 
Looks for me, that the fact, that the menu item for setting up mailman is only displayed for the initial configuration of mailman and afterwards disabled ==> found this today on 2 posts in other forums.
The unavailability of the subdomain was caused by a missing DNS entry.
I hopefully fixed the memory limit by adding the DEFAULT_MAX_MESSAGE_SIZE parameter in the file /etc/mailman/mm_cfg.py
 
Back
Top