Search results

You can start by first checking the headers of the spoofed email to see if the original sending IP is actually your server. If you confirm that it's not, then consider using SPF to help combat message spoofing.

Great to hear - Plesk is finicky about permissions so customizing ownership can give it a bad cold.

The best problems are the ones that solve themselves! Care to elaborate on your solution?

As you seem to be handy with SSH, have you run the command? plesk repair fs Without any additional flags that should recurse through both your vhosts and system files. Link to all options for Plesk Repair Utility: File System

Why yes sir! There's a handy dandy article on this very topic complete with well-snipped screenshots here.

This came up not too long ago - Have you checked out this thread to see if there is a nugget that might help?

Correct, as @Peter Debik pointed out the first part is strictly for the initial issuance of the SSL certificate. Ideally it really should be in two different messages or the empty part should be suppressed but that might be splitting hairs at the moment.

Additionally, DigitalOcean may require a request or change on their to open 25 at a level higher than your installation. Other cloud providers have been known to imposed that limitation out of the box to help combat spam originating from their IPs.

A little "unresolve" status magic would be nice on this post - Has anyone running 18.0.28 reported this as a bug?

No doubt making some t-shirts or bumper stickers with that very quote can be tempting as is the case with any complex ecosystem. As previously suggested, have you started by making this change? content_filter = amavis:[127.0.0.1]:10024 to content_filter = smtp-amavis:[127.0.0.1]:10024

For any interested (or just plain bored readers) of this post, the issue, albeit a bit difficult to tell from the lack of a more meaningful error, stemmed from the same circumstances detailed here so by disabling priority protections, running the update, and then re-enabling it as documented in...

If you're using the WordPress tool for each location, try scanning for them again. You should likely see a "broken" instance for the source one that you can remove if you're not using it or its files/database and the new one should pick up its new "home" regardless of directory change.

Because instead of having two email templates, the little person who lives in your Linux box just types out one! But yes, in an ideal world, the first portion would be suppressed if there are no new ones and same for renewals if there are no new referrals.

Assuming that's it not all email originated from your server(s), the message content and structure may also play a part in that determination.

Another "here as well" to add to this thread - So apparently even "large" number updates are indeed automatic but with somewhat erratic dates/times that they apply (an update from 18.0.28 #3 to 18.0.29 #2 that kicked off during business hours on its own). All I can say is...... IT'S...

I would recommend avoiding the upgrade/restore circle as that isn't likely going to address the issues that you're using. The first action item might be to engage either Plesk support or your Plesk reseller to get this addressed and if it's especially critical, Plesk support might be the way to go.

If that's the case, there are a couple of things that you can do depending on your level of technical aptitude. More often than not this isn't a Plesk issue and if turns out to be, your provider can address it for you or let you know what's needed to send mail in their environment (in some cases...

In some ways it wouldn't be terribly challenging since they already do it for the database service that ships with Plesk so they could offer a "Use vendor database" option just like we see with PHP handlers as a default alongside a "Use MariaDB shipped with Plesk" option. Now THAT would be...

Are you a hosting provider or are you an end user working on a site that happens to be using the Plesk control panel? Depending on your answer, that will determine the next step to check!

If you haven't already restored your server from a backup and you engage Plesk Support, please post back with your results!