• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Serious Aliasing Bug

K

kwillmon

Guest
I have the latest update to 8.1.1 and found out through search engines that content in my server's main domain can be accessed through the mail sub-domain for ALL other domains on my server. For example:

http://www.MainDomain.Com/ThisFile.Ext
can also be accessed by going to
http://mail.AnyOtherDomain.Com/ThisFile.Ext

or
http://www.MainDomain.Com/SomeDirectory/ThisFile.Ext
can also be accessed by going to
http://mail.AnyOtherDomain.Com/SomeDirectory/ThisFile.Ext

Is anyone else having this problem too?
 
been that way for me since 7.x (my first soirée into plesk).

I'm no expert here, but I believe it's that way so all the POP, SMTP, IMAP, etc, mail traffic gets forwarded to the right place on the server. The same is true of webmail (which you probably wouldn't notice because of the horde interface) and FTP.

The "culprit" is the DNS settings under the server control panel. If your DNS skills are better than mine, then you might be able to figure out how to fix it.

You might also be able to fix it by creating a "mail" subdomain on your default domain. Then adding in an index.php file that checks the $_SERVER['SERVER_NAME'] and does a header redirect to the www address of the same.
 
The reason is because the HTTP and SMTP services are accessible over the same IP address. If you set a default web site then any requests that don't match a valid web site (including the IP address itself, or in your case mail.domainname.com) will be answered by the default site.

You could unconfigure the default site so that any invalid requests will be answered by the "Default Plesk Page", or you could manually set up a virtual host to respond to mail.* and fix it that way (but you'd have to do that manually and not through Plesk).

It's not really a bug as such but it's more due to the nature of running virtual hosting.
 
Back
Top