• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

MailEnable headers

G

getUP

Guest
A customer running a server with Plesk 8.2, MailEnable generates the following header:

Code:
Received: from ([127.0.0.1]) with MailEnable ESMTP; Thu, 25 Oct 2007 23:33:48 +0200

SpamAssassin on other servers have issues with this:

Code:
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE,
	UNPARSEABLE_RELAY

The unparseable relay error is caused by that header for what I know.

Another server generates the following header, which is how it should look like:

Code:
Received: from localhost ([127.0.0.1]) by hostname.com with MailEnable ESMTP; Sat, 20 Oct 2007 18:51:15 +0200

Who has any idea what's causing this and how we can solve it? Our hosts file just has "127.0.0.1 localhost" in it. Is this correct?
 
Back
Top