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