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

Duplicate mail headers with multiple receipients

Flachzange

Basic Pleskian
A customer reported a bug where mails were rejected due to multiple x-headers:


For example:

host mx-rz6.energie-rath.de[88.198.232.66] said: 554 5.7.7 too many equal X-headers (X-No-Relay:) (in reply to end of DATA command)


The cause are indeed too many x-headers of type x-no-relay in the mail. I could reproduce it by simply adding more multiple recipients to the mail. For every recipient, a separate header tag is generated.

Thx for helping!


---------------------------------------------------------------
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

PLESK, 10.4.4#27, Ubuntu 8.04, x86

PROBLEM DESCRIPTION

Postfix generates a x-no-relay header for every recipient in the mail causing other mail servers rejecting this mail.

STEPS TO REPRODUCE

Write an email to two or more recipients.

ACTUAL RESULT
At least two x-no-relay entries.

EXPECTED RESULT
One x-no-relay entry

ANY ADDITIONAL INFORMATION
--------------------------------------------------------------
 
I have forwarded your report to developers. I will update thread with results when I receive them.
 
As workaround just remove non_auth.re and no_rely.re records in main.cf for Plesk >=10.4
or clean:
/var/spool/postfix/plesk/non_auth.re
/var/spool/postfix/plesk/no_relay.re
 
It will be completely fixed in upcoming Plesk 12.
 
Back
Top