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

Possible BUG: 11.0.9 #MU55 - Apache Webmail Wildcard missing by default

Antonio Sanchez

New Pleskian
I have detected a possible BUG in the default configuration of Plesk 11.0.9 at least in #MU55.

Working with the DNS Wildcard for Webmail I have found that the system does not create the ServerAlias Wildcard according to the DNS Zone in the Apache directives.

Recreate:
* Create a new domain with primary DNS zone
* Try to access to webmail.domain.tld. It must work correctly
* Try to access to whatever.webmail.domain.tld. It does not work and Plesk shows the default webpage.

Why?:
In Plesk 11 the Apache main directives are located under /etc/httpd/conf.d/. The main file that manage the vhost directives is zz010_psa_httpd.conf.

Into this file we can find that it points to another files, generated by Plesk, for example, when you reconfigure domains with /usr/local/psa/admin/bin/httpdmng --reconfigure-all

This is how zz010_psa_httpd.conf looks like:
Code:
#ATTENTION!
#
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.
Include '/usr/local/psa/admin/conf/generated/13735297540.77229700_server.include'
Include '/usr/local/psa/admin/conf/generated/13735297540.77229700_horde.include'
Include '/usr/local/psa/admin/conf/generated/13735297540.77229700_atmail.include'
Include '/usr/local/psa/admin/conf/vhosts_bootstrap.conf*'

As we can see the webmails config is located under the /usr/local/psa/admin/conf/generated/

Well, this is where the possible BUG exists becouse into these files a ServerAlias directive for the wildcard should be created but it is not.

As default it creates
Code:
ServerAlias webmail.domain.tld

And it should create:
Code:
ServerAlias webmail.domain.tld
ServerAlias *.webmail.domain.tld

Solution:
I think that in the /usr/local/psa/admin/conf/templates dir, where are located the files that has the configuration template info used to generate the correct configuration, are not defined the wildcard pointers in the ServerAlias, so creating this pointers will solve the problem

I hope this info could help anyone with this kind of problems.

Best Regards
Antonio Sanchez
 
It is simple.

Plesk creates by default the *.webmail.domain.tld in the DNS zone becoming from Plesk default DNS templates.

Therefore, it would be normal to maintain a consistent configuration, if the wildcard is generated automatically when you create the DNS zone for a new domain, it would make sense that the Apache has a configuration able to function properly with this configuration. If at DNS level, domain pointers are created and Apache do not work with it, in my opinion is a BUG since it is a configuration inconsistency.

Looking to the DNS configuration it is expected that *.webmail.domain.tld works in Apache such a way that whatever.webmail.domain.tld answers with the webmail frontend.

Best Regards
Antonio Sanchez
 
Back
Top