• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Question Rewrite Plesk Sender Adress

wilkis

New Pleskian
We will rewrite the Plesk Sender Adress.
Code:
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  [email protected]
    SMTP error from remote mail server after end of data:
    host another.mailserver.net [1.1.1.1]: 550-5.7.1 This email was rejected because it violates our security policy
    550 5.7.1   MAIL FROM domain (plesk.example.com) and Header-From domain (example.com) are not equal.

------ This is a copy of the message, including all the headers. ------

Return-path: <[email protected]>
...
Received: by plesk.example.com (Postfix, from userid 0)
    id 2851336D193; Wed, 21 Mar 2018 08:23:59 +XXXX (XXX)
To: res1 <[email protected]>
Subject: =?UTF-8?Q?=3Cpsk=2Ecust=2Eexample=2Ede=3E=20Notification=3A=20Resource=20usage=20by=20subscription=20has=20exceeded=20the=20allotments=2E?=
From: Administrator <[email protected]>
Reply-To: Administrator <[email protected]>
Date: Wed, 21 Mar 2018 08:23:59 +XXXX
X-Mailer: PHP/X.X.XX
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
MIME-Version: 1.0
Message-Id: <[email protected]>
X-MMR-Original-From:2.2.2.2

Message Text
 
It is perfectly legitimate that "mail from" and "header from" differ. This probably applies to a billion mails a day. It is rather a security overkill to evaluate a mismatch and block mail that has that mismatch.
 
Back
Top