Question Whitelists (IPv4 & IPv6) For Plesk 360 - Modified and/or Where Have They Gone?

[learning_curve]

We set up Plesk 360 when it first was offered. So far, it's all been good.
Today, we've had lost of warnings (via Plesk's Spam Assassin) due to the sender's IP Addresse(s) that has been used, already being on certain blocklists
These came from Plesk 360, but... the original e-mails (with the blocked IP addresses) came from... Plesk 360! So this is Plesk, reporting Plesk, to Plesk

We had all of the orginal whitelisted IP Adresses (both IPv4 and IPv6) i.e. all of those that were provided by Plesk 360, correctly configured, but...
Today's "offending IP addresses" were not in those whitelists and the Plesk 360 whitelist link: Plesk 360 is currently, just a 404 page

Plesk! Can you please advise / update / correct ASAP?

 

[learning_curve]

FWIW Here's one quick example:

The Original e-mail IP Address, which is not in the original Plesk 360 whitelist and, the reason is was blocked, hence the followup warnings etc

~ 360 Monitoring <noreply@monitoring360.io> ~ spf=pass (sender IP is 54.240.7.29) smtp.mailfrom=0102017e9b1e7666-dc058627-0178-40a9-97be-0369d277f60d-000000@aws.monitoring360.io smtp.helo=a7-29.smtp-out.eu-west-1.amazonses.com ~
~
0.0 RCVD_IN_DNSWL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to
DNSWL was blocked. See
DnsBlocklists - SPAMASSASSIN - Apache Software Foundation
for more information.
[54.240.7.29 listed in list.dnswl.org] ~

 

[Kaspar]

@vincent360 any suggestions?

 

[learning_curve]

More info after digging deeper into this...

These errors won't stop (automatically anyway - see below) so the warnings will keep arriving by default, because they are being generated, originally, from one of the default warnings that are provided by Plesk 360, the one which specifically relates to disk usuage. This one:

if disk (any) used percentage is higher than 90% for 15 minutes alert Default Contact[Email]

However, erronously, this is reporting all of the Ubuntu Snap Disk areas (/dev/loop*) which are, by default and by design, always at 100% so its #FalsePositives
This errroneous reporting is then exacerbated by the set of IP Address issues shown in the first two posts above, but see further notes below.

Plesk 360 genertates false positive errors in relation to the set of Ubuntu /dev/loop* on the server
These errors are NOT reported via GUI anywhere else e.g. /modules/diskspace-usage-viewer/ or /plesk/server/statistics/ or the Plesk Monitoring extension
These are then reported by e-mail (see quoted text ^^) but the IP addresses being used by both Plesk 360 (and the IONOS Name Servers) have already exceeded the DNSWL limits. A simple explanation of those limits etc is here: “Am I Blocked?” – dnswl.org
This results in the Plesk 360 e-mails being picked up by Spam Assassin and then a revised system email (from Plesk 360) c/w the original e-mail & an SA Report
These errors have started since the last server re-boot, when using Plesk Obsisidan 18.0.41

The real Plesk related questions therefore @vincent360 are:
Plesk 360 should not, by default, report disk usage errors for Ubuntu Snap Disk areas (/dev/loop*) - Will this be fixed?
The whitelist of Plesk 360 IP IPv4 and IPv6 addresses has been changed without customer notification / is currently a 404 page - Will this be fixed?

NB We (the users) can edit the associated Plesk 360 warning criteria and the Spam Assassin settings, as workarounds in the interim, so we have done.

 

[learning_curve]

Did we miss the Plesk response @vincent360 .......?

 

[learning_curve]

Bump
The Plesk 360 whitelist page is still just a 404 (at the time of writing this post) and there's still no response from Plesk / @vincent360
Therefore, to make some progress, does this need a bug report posting @IgorG do you think?

 

[IgorG]

Therefore, to make some progress, does this need a bug report posting @IgorG do you think?

Yes, please fill report and I will forward it to developers immediately.