Search results

The microupdate 18.0.23 update # 1 is also buggy :oops: - there is no longer a possibility to enter a blacklist. the previously entered blacklists (spamcop etc.) disappear from main.cf as soon as saved the settingspage. - Outgoing mail mode has no IP defined - The anti-virus filter used is not...

that was already reported here https://talk.plesk.com/threads/ppp-47160-plesk-18-0-23-on-centos-7-internal-error-on-server-wide-mail-settings-page.354979/ and in addition there is another BugID here...

this could be as follows. - set up a new centos 7 server with plesk an install pleskmigrator extension - migrate all accounts from the centos 6 server with the "pleskmigrator" to centos 7 server - either remove the ip from the source server and put it on the target server and change the ip...

is probably also under another BugID PPPM-11478. Should be related to the fact that bind is not installed. https://support.plesk.com/hc/en-us/articles/360011393240-Mail-Server-Settings-tab-shows-Internal-Server-Error

I also confirm this Bug on CentOS 6.10, CentOS 7.7 after reactivation, all settings are default and must be reset. If you then call up the page again, the first error appears again. The option "Spam protection based on the DNS blackhole lists" is gone Oh my God :cool: it may be better to run...

Hi, see: Plesk email account via Outlook IMAP/POP3 returns the following after syncing: Message appears to be a Unicode message and your E-mail reader did not enable Unicode support. I assume that nobody can say exactly when the fix is coming

only if you DO NOT use courier-imap. otherwise you will have some dissatisfied customers. ;)

Is it possible to replace MariaDB 5.5, 10.X with MySQL 5.6, 5.7 on a Plesk server

if you have mariadb installed, you can stay with mariadb and update it. How to upgrade MySQL 5.5 to 5.6/5.7 or MariaDB 5.5 to 10.0/10.1/10.2 on Linux? always make a backup :)

have you already updated to 18.0.21 Update 3?

Does anyone know what the "SelectBestBuild function" is about? if the two servers in my example would be different but that's not the case. both servers are exactly the same. same os had same extensions same configuration.

yes, the update settings are the same everywhere what I have found so far: on a machine that has automatically updated (autoinstallerlog) on a machine that has not updated automatically (autoinstallerlog) what is "The SelectBestBuild function" ?

some of the servers have automatically updated within the first two days after the appearance of 18.0.21 and the other part not, but after the login only shows an "An upgrade to Plesk Obsidian 18.0.21 is available." if every month new upgrades appear, they always have to be triggered manually...

where at Plesk Obsidian should this attitude be? Under Tools - Update Settings is nothing.

I have noticed that on some systems the update from 18.0.20 to 18.0.21 was automatically installed and on some system this is not automatically installed. the update settings are the same everywhere. Where can I look for what the problem could be?

could someone please check if this manual for centos 6/7 is correct? yum install perl-Razor-Agent pyzor pyzor --homedir /etc/mail/spamassassin discover mkdir /etc/mail/spamassassin/.razor sudo razor-admin -home=/etc/mail/spamassassin/.razor -register sudo razor-admin...

maybe you have upgraded mariadb 10.1 to 10.2 ? Troubleshooting Row Size Too Large Errors with InnoDB ALTER TABLE clients ROW_FORMAT=DYNAMIC; should eliminate the warning. always make a backup before

thanks ales for the info this is of course great if the developer of a server software implements a rule without first checking exactly whether the clients fully implement this rule. then we'll wait and see whether either the clients make corrections or courier changes.

Hi Igor, thank you for your message. but that is not a pure outlook problem. there are customers who use thunderbird or macmail and also have this message. This only happens with isolated emails. For example, a customer receives an email a day from an email distributor and suddenly after the...

I can report that we have updated more than 100 servers so far and there is no problem.