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