• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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