• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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