• 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!
  • 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 Mailman + nginx proxy mode off

Matt M

New Pleskian
Hi,

I've disabled nginx proxy mode on one of my domains. In other words, nginx serves all requests directly, without going through Apache. This has broken mailman. Now when I try to access https://lists.domain.com/mailman/admin/listname, the server returns the home page of domain.com. If I re-enable proxy mode, the issue is fixed. I've tried googling this issue but haven't found anything. Does anyone know of a fix or workaround?
 
Last edited:
Nginx does not support Apache .htaccess rewrites. You need to convert all rewrite rules and settings and enter them as additional Nginx rules into the Nginx configuration. Else some paths or file cannot be accessed as the path is not rewritten.
 
I understand this. I just figured that since I was using two standard Plesk features -- nginx and Mailman -- someone might already have come up against this issue.
 
Back
Top