• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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