• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Blacklist Behaviour

Namesonic

New Pleskian
Plesk 11.5

We are utilizing the Plesk Blacklist email feature but find that the blacklist applies to only the Return-Path: header if specified and not the From: or Sender: fields.

Most customers do not inspect headers and enter only the From: address as the blacklist value. As a result, the customer continues to receive spam from the same address but coming from different Return-Paths.

Can you verify that the blacklist is ONLY supposed to check the Return-Path field when rejecting email? Or should it also be checking the other available fields?

Thanks in advance.
 
Back
Top