• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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