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

Mailman: Envelope-From set wrong for messages to list-owner

mejo

New Pleskian
Hello,

apparently Envelope-From, Sender and Errors-To headers are set to a wrong address for messages from mailman to the list-owner. This is particularly true for mails like 'message requires approval'.

It seems like the plesk<->mailman magic results in all list-domains being written to the end of /var/lib/mailman/Mailman/mm_cfg.py in the following format:
add_virtualhost('list.DOMAIN')

This in return results in mail headers Envelope-From, Sender and Errors-To of mailman system mails like described above being set to mailman-bounces@DOMAIN, where DOMAIN is the one from the last add_virtualhost entry.

In my opinion, this obviously is a bug. Maintainance mails from mailinglists have wrong headers set, often with a domain that belongs to a completely different customer than the mailinglist.

I found the following discussion on mailman-users mailinglist from 2008 which discusses the same issue - also a plesk setup: https://mail.python.org/pipermail/mailman-users/2008-July/062413.html

Cheers,
jonas
 
Parallels acknowledged the problem as a bug in plesk in the meantime. Bug id #PPM-2449 has been assigned to it. Let's hope that they fix it in the next update of plesk 12.
 
Hi,

Has #PPPM-2449 been fixed? We're running a server with Plesk v12.0.18 and a customer reported the same issue on June 9th.

Thanks,
 
Back
Top