Search results

Thank you, Peter. I would also like to vote for it, but the topic has already been rejected by Plesk.In addition, my experience with feature requests is that it takes several years for Plesk to respond - if at all. I don't have several years to spare, so I'm looking for a solution that helps me...

No solution, yet? How about a file / directory protection for this specific mailaddress via ssh? Could this lead to any problems?

We need something like an email archive. Therefore, we plan to copy all emails from one mailbox to another. Is there a way to protect a specific mailbox from accidentally deleting any emails?

I have just found the automated script for the dist-upgrade from Ubuntu 18 to 20 as described here: https://support.plesk.com/hc/en-us/articles/12377714344983. Will there be similar scripts available for other Linux distributions like Debian as well?

Our customers need a way to secure emails in a separate mailbox that is read-only, so the mails can be viewed but not deleted. I came across the ACL Plugin from Dovecot, which is installed by default in Plesk but not activated. Using ACL seems to achieve this. Is it safe to use this plugin, or...

#!/bin/bash /usr/local/psa/bin/domain_pref --update ${NEW_DOMAIN_NAME} -sign_outgoing_mail false @Kaspar Yes, this event seems to work as a workaround. Thank you.

@Kaspar Thank you, but your solution would result in another problem. Since we are using an external DNS server, DKIM would be enabled by default for all newly created email accounts, even if it is not set up. This behavior was introduced in one of the recent Plesk patches.

Hello, this issue has been ongoing for a few days now. Is there any workaround available to us until the patch is released? How can I obtain the required DKIM record?

How about Plesk firewall rules for that? Disallow all mail access from ips other than server ip address and other servers addresses.

I can now download 18.0.56 Update 2 which seems to fix that problem. https://docs.plesk.com/release-notes/obsidian/change-log/?18056#plesk-18056-mu2 Thank you

That's just the default setting for new mail accounts. Check settings for individual mail accounts under the subscriptions.

Yes. Comment out all other lines with nameserver x.x.x.x 8.8.8.8 is Google DNS Server. It is intended for testing purpose if 127.0.0.1 still does not work. bind9 should work with nameserver 127.0.0.1 for resolv.conf

Please check the settings of /etc/resolv.conf Try adding nameserver 127.0.0.1 nameserver 8.8.8.8 and comment everything else like # nameserver 127.0.0.53

I have blocked ports 7080 and 7081 in the Plesk Firewall. To me, this seems to be a better solution and so far, I haven't encountered any problems with it. Have I overlooked something? Is there any reason not to block these ports in the firewall?

I'm sorry, I posted to the wrong location. This thread belongs to Plesk Obsidian for Linux, not Onyx. Yes, it is Ubuntu. Thank you, I will try it.

I tried the solution for but I get the error /etc/httpd/conf/httpd.conf dir or file not found If I understand correctly, if I could do that, I had to add: RemoteIPHeader CF-Connecting-IP RemoteIPTrustedProxy 127.0.0.1 into a new file like: /etc/httpd/conf.d/localhost.conf Is that correct?

Hello, we used the command plesk bin apache --listen-on-localhost true as described in https://support.plesk.com/hc/en-us/articles/17793065826839 After that we have problems, because some code needs to get the visitor's ip address with PHP $_SERVER[ 'REMOTE_ADDR' ] or with .htaccess Allow from...

Hello and thank you @Peter Debik . I will use a workaround until the final fix is released.

Okay, thank you. I will vote for this feature.

Just to complement: when I remove the password protection from domain, everything works as expected. When I switch it on again, I receive error 404 for all files in subdirectories, not 401 as mentioned above.