• 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.

Mail header parsing bug / NDR reflection spam

JasonE

New Pleskian
Mail sent to Plesk servers running Postfix with a "Delivered-To:" header will bounce to sender with a "mail forwarding loop" message.

For example, if a message with the following headers is sent to Plesk:

Code:
Delivered-To: test@recipient.com
Return-Path: <test@sender.com>
From: <test@sender.com>
Subject: test
To: <test@recipient.com>

It will bounce with the following:

Code:
Reporting-MTA: dns; host.domain.com
X-Postfix-Queue-ID: EABA02A10C9
X-Postfix-Sender: rfc822; test@sender.com
Arrival-Date: Wed,  5 Dec 2012 17:09:46 -0500 (EST)

Final-Recipient: rfc822; test@recipient.com
Original-Recipient: rfc822;test@recipient.com
Action: failed
Status: 5.4.6
Diagnostic-Code: X-Postfix; mail forwarding loop for test@recipient.com

This assumes "test@recipient.com" is a valid user on the server. I imagine a malicious third-party could manipulate the Return-Path/From headers in order to send NDR reflection spam.
 
Have you checked that recipient.com hostname is resolvable from Plesk server?
 
recipient.com resolves to the Plesk server, and is resolvable from the Plesk server. This is not relevant to the problem.

I became aware of this when I noticed unusual bounces queued up in one of our servers. I used a packet analyzer to capture and dissect new messages as they came in, which allowed me to isolate the problem to the errant header.
 
Back
Top