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

[PPPM-3456] Mailman 2.1.12 : pb with data headers exceeds..

Erwan

Regular Pleskian
Hello,

We have a data header with Mailman with Plesk 12.5 :

xxx : hostsmtppromx.orange.fr[193.252.23.116] said:
552 5.7.0 Number of 'Received:' DATA headers exceeds maximum permitted (in
reply to end of DATA command)

xxx: hostsmtp-in.orange.fr[193.252.22.65] said: 552 5.7.0
Number of 'Received:' DATA headers exceeds maximum permitted (in reply to
end of DATA command)

xxx: hostsmtp-in.orange.fr[193.252.22.65] said: 552
5.7.0 Number of 'Received:' DATA headers exceeds maximum permitted (in
reply to end of DATA command)


In the message entete received from Mailman message, we have a lot of:

Received-SPF: pass (xxx: localhost is always allowed.) client-ip=127.0.0.1; [email protected]; helo=server.domaine.net;
Received-SPF: pass (xxx: localhost is always allowed.) client-ip=127.0.0.1; [email protected]; helo=server.domaine.net;
Received-SPF: pass (xxx: localhost is always allowed.) client-ip=127.0.0.1; [email protected]; helo=server.domaine.net;
Received-SPF: pass (xxx: localhost is always allowed.) client-ip=127.0.0.1; [email protected]; helo=server.domaine.net;

How can we configure that in Mailman?
Note: we don't have the problem with other server emails.
 
As far as I know we have already submitted bugreport regarding this issue (PPPM-3456 for your reference).
The fix is considered to be included in one of the next Plesk updates.
Please use the id provided for your reference to trace the status of the issue.

http://kb.odin.com/subscriptions/index.html - knowledge base, each product update comes with corresponding KB article;

Additionally you can use RSS feeds at http://kb.odin.com/rss/index.html
 
Hello Igor,

The fix is considered to be included in one of the next Plesk updates.
Please use the id provided for your reference to trace the status of the issue.


Sorry, can you explain? I don't find the information....

Erwan
 
Bug is not fixed yet and will be fixed later. You can subscribe to notifications about new updates with links provided by me above. Each Release Notes of update contains IDs of fixed bugs. You know ID - PPPM-3456. Just monitor update release notes now.
 
How much longer is this bug going to take to fix?

We are having to run our server with SPF record checking off just to keep our Mailman lists working!

Forcing Plesk users to make a choice between Mailman & SPF is pathetic -- this should be patched before the next release.
 
Hi Martin,

for your information: The bug with the issue "PPPM-3456" has now being fixed with the latest Plesk Onyx 17.5.3 Update 23. ( You might know, that we fix bugs first within the latest, currently stable versions, while other versions might follow )
 
Back
Top