• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Plesk Premium Mail Autodiscover

drdna

New Pleskian
Server operating system version
Ubuntu 18.04.6 LTS
Plesk version and microupdate number
Plesk Obsidian Version 18.0.46
Hello Pleskians,
my autodiscover / autoconfig with Plesk Premium Mail is not working correctly.

When I test the output of :
curl https://www.mydomain.de/autodiscover/autodiscover.xml
or
curl https://www.mydomain.de/mail/[email protected]

gives me output of the /usr/share/kolab-autoconf/public_html/index.php file instead of an xml file...:
Code:
<?php

/**
 +--------------------------------------------------------------------------+
 | Kolab Autodiscover Service                                               |
 |                                                                          |
 | Copyright (C) 2011-2014, Kolab Systems AG <[email protected]>         |
 |                                                                          |
 | This program is free software: you can redistribute it and/or modify     |
 | it under the terms of the GNU General Public License as published by     |
 | the Free Software Foundation, either version 3 of the License, or        |
 | (at your option) any later version.                                      |
 |                                                                          |
 | This program is distributed in the hope that it will be useful,          |
 | but WITHOUT ANY WARRANTY; without even the implied warranty of           |
 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the             |
 | GNU General Public License for more details.                             |
 |                                                                          |
 | You should have received a copy of the GNU General Public License        |
 | along with this program. If not, see http://www.gnu.org/licenses/.       |
 +--------------------------------------------------------------------------+
 | Author: Aleksander Machniak <[email protected]>                      |
 +--------------------------------------------------------------------------+
*/

// environment initialization
define('INSTALL_PATH', realpath(dirname(__FILE__) . '/../') . '/');

ini_set('error_reporting', E_ALL &~ E_NOTICE &~ E_STRICT);
ini_set('error_log', INSTALL_PATH . '/logs/errors');

$include_path = INSTALL_PATH . '/lib' . PATH_SEPARATOR;
$include_path .= ini_get('include_path');
if (set_include_path($include_path) === false) {
    die("Fatal error: ini_set/set_include_path does not work.");
}

require_once INSTALL_PATH . '/lib/Autodiscover.php';

// Set internal charset
mb_internal_encoding(Autodiscover::CHARSET);
@mb_regex_encoding(Autodiscover::CHARSET);

Already reinstalled Plesk Premium Mail Extension,

Ubuntu 18.04.6 LTS
Plesk Obsidian Version 18.0.46 Update #1
Plesk Premium Mail 16.14.0-4

Can someone help me please to fix the error?
Thanks
 
It is said that autodiscover is a separate option in Plesk Premium E-Mail. Is it enabled?

Other users report that to return to Plesk autodiscover, they added
[mail]
autoconfig.enabled = 1
to the panel.ini file.-
 
@Peter Debik Thanks, yes Premium Mail is enabled for one Test Subscription. I want to Test it if it make sense to build bigger environments.

The Web Access via webmail.comain.tld and the Smartphone Active Sync connection with the same servername works fine.
Outlook doesn't work, because they call the autodiscover.xml

And then the Plesk Server not deliver the expected xml output, instead plesk deliver the same PHP Output like in @drdna original post.

I have also created a case for that - #95201266.
But it sound a little bit creepy that i found only a few information in the web for this plesk feature.
Do you know if its its very rare used feature?
Do you think that i can create very big Setups (> 1.000 users) with your Plugin and it scale as expected? :)
 
Other users report that to return to Plesk autodiscover, they added
[mail]
autoconfig.enabled = 1
to the panel.ini file.-
But in the Knowledge base for the Premium is written, that is expected that the default autodiscover will be deactivated and replaced by an own autodiscover from the premium mail? Is this not right?
 
Yes, Premium EMail replaces the default. That is why I asked whether autodiscover is enabled. The other setting is just an option.

Outlook has issues with autodiscover files that other software understands. I am not sure to which extent this applies in this case. Have you contacted Plesk support already? They will be able to find out more.
 
Thanks, yes i have already an open case for that issue. I will wait for a solution in the suport case.
 
Thanks, yes i have already an open case for that issue. I will wait for a solution in the suport case.
You have already seen my other post so you know the problems.

Regarding this exact problem, you better of telling your customers to always use the manual setup.
Autodiscover tries to use ActiveSync for domains where it is not enabled or uses IMAP for ActiveSync enabled domains.

If it works at all, it will setup the domain of the subscription instead of the Plesk server domain as the mailserver, which would be fine if Plesk would secure the mail domain with an SSL certificate. Currently that will just prompt a certificate issue on Outlook and most other clients.
 
This topic is a horrible story..
The plesk support not really understand the issue, and the kolab plugin breaks existing non-premium mailboxes by behavior and file system changes inside the imap boxes :/

  • I have closed the support case (hopefull a new case will be helpful)
  • I have deinstalled the Plugin, and plan to try it on a separate play machine
At the moment i think it is not possible to provide premium-mail and non-premium-mail on the same server because the collab setting interference with non-premium mail users and breaks the default imap behavior.
 
Back
Top