• 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.

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