• 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!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Issue mailman3: host and web-host not aligned with custom domain name

Jan

Basic Pleskian
Server operating system version
Debian 12.6
Plesk version and microupdate number
18.0.63 Update #4, last updated on Sept 4, 2024 06:27 AM
Is:

In the mailman3-configuration example.com / localhost is encoded at various places:
  1. /etc/mailman3/mailman.cfg: site_owner:
  2. /etc/mailman3/mailman-web.py: EMAILNAME
  3. postorious / django3 Web-Host List (https://<domain>/mailman3/admin/sites/site/): example.com
Should:

1. and 2. should be valid email-addresses to contact the site-owner. These are default addressed for moderation-requests
3. Is more tricky. This can either be the name of the vhost oder the host. That depends on how django is integrated into plesk. IMHO, the best-case scenario would be to have a dedicated web-host per enabled domain including a valid let's-encrypt certificate ... But this is seemingly not the case. However, example.com does not fit, here
 
Back
Top