[Bug 1694384] [NEW] Missing list owner email alias in data/virtual-mailman

Public bug reported: Dear project leader, In the Mailman version 2.1.21, you released a fix regarding Mailman- Postfix: - Mailman-Postfix integration will now add mailman@domain entries in data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS which is a host_name of a list. This is so the addresses which are exposed on admin and listinfo overview pages of virtual domains will be deliverable. (LP: #1459236) That fix was a good thing. However there is an identical problem for the site list owner email that is exposed in email notification when you create a new list. Indeed, when you create a new list, there is a notification that is sent to the list owner and which state that it must address all questions to mailman-owner@VIRTUAL_DOMAIN. Therefore, you should considere adding that alias too in the data/virtual-mailman map. Right now, sending mail to such address result to non-delivery. That being said, I would want give you my personal point of view regarding the email addresses that are exposed. Regarding the site list address that is exposed in the listinfo overview page: I tend to think that exposing the site list email address in the listinfo overview page is a mistake. End-users that visit or subscribe to the lists shouldn't have to ask any question to the mailman site list administrator. Think of a shared hosting environment where there is the sysadmin and the end-users which are administrators of their own lists. Here, my thinking is that subscribers (or visitors) of the listinfo interface should ask their questions, not to the mailman site list administrator, but to the list administrator which is not always the same person. From my point of view, only the list administrators should have to ask something to the mailman site list administrator (sysadmin). Another thing: In the listinfo oveview page, you're also exposing the list administrator personal email in the footer (email used while creating the list). From my point of view, that email should be hidden from the visitors and subscribers. That email, always from my point of view, should be replaced by the list owner email address (<listname>-owner@VIRTUAL_DOMAIN). Thank you. ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman (Ubuntu) Importance: Undecided Status: New ** Affects: mailman (Debian) Importance: Undecided Status: New ** Description changed: Dear project leader, In the Mailman version 2.1.21, you released a fix regarding Mailman- Postfix: - - Mailman-Postfix integration will now add mailman@domain entries in - data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS - which is a host_name of a list. This is so the addresses which are - exposed on admin and listinfo overview pages of virtual domains will - be deliverable. (LP: #1459236) + - Mailman-Postfix integration will now add mailman@domain entries in + data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS + which is a host_name of a list. This is so the addresses which are + exposed on admin and listinfo overview pages of virtual domains will + be deliverable. (LP: #1459236) - That fix was a good thing. However there is an identical problem for the site list owner email that is exposed in email notification when you create a new list. Indeed, - when you create a new list, there is a notification that is sent to the list owner and which state that it must address all questions to mailman-owner@VIRTUAL_DOMAIN. Therefore, you should considere adding that alias too in the virtual-mailman map. Right now, sending mail to such address result to non-delivery notification. + That fix was a good thing. However there is an identical problem for the + site list owner email that is exposed in email notification when you + create a new list. Indeed, when you create a new list, there is a + notification that is sent to the list owner and which state that it must + address all questions to mailman-owner@VIRTUAL_DOMAIN. Therefore, you + should considere adding that alias too in the virtual-mailman map. Right + now, sending mail to such address result to non-delivery notification. That being said, I would want give you my personal point of view regarding the email addresses that are exposed. Regarding the site list address that is exposed in the listinfo overview page: I tend to think that exposing the site list email address in the listinfo overview page is a mistake. End-users that visit or subscribe to the lists shouldn't have to ask any question to the mailman site list administrator. Think of a shared hosting environment where there is the sysadmin and end-users which are administrators of their own lists. Here, my thinking is that subscribers (or visitors) of the listinfo interface should ask their questions, not to the mailman site list administrator, but to the list administrator which is not always the same person. From my point of view, only the list administrators should have to ask something to the mailman site list administrator (sysadmin). Another thing: In the listinfo oveview page, you're also exposing the list administrator personal email in the footer (email used while creating the list). From my point of view, that email should be hidden from the visitors and subscribers. That email, always from my point of view should be replaced by the list owner email address - (<listname>-owner@VIRTUAL_DOMAIN. + (<listname>-owner@VIRTUAL_DOMAIN). + + Thank you. ** Description changed: Dear project leader, In the Mailman version 2.1.21, you released a fix regarding Mailman- Postfix: - Mailman-Postfix integration will now add mailman@domain entries in data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS which is a host_name of a list. This is so the addresses which are exposed on admin and listinfo overview pages of virtual domains will be deliverable. (LP: #1459236) That fix was a good thing. However there is an identical problem for the site list owner email that is exposed in email notification when you create a new list. Indeed, when you create a new list, there is a notification that is sent to the list owner and which state that it must address all questions to mailman-owner@VIRTUAL_DOMAIN. Therefore, you - should considere adding that alias too in the virtual-mailman map. Right - now, sending mail to such address result to non-delivery notification. + should considere adding that alias too in the data/virtual-mailman map. + Right now, sending mail to such address result to non-delivery + notification. That being said, I would want give you my personal point of view regarding the email addresses that are exposed. Regarding the site list address that is exposed in the listinfo overview page: I tend to think that exposing the site list email address in the listinfo overview page is a mistake. End-users that visit or subscribe to the lists shouldn't have to ask any question to the mailman site list administrator. Think of a shared hosting environment where there is the sysadmin and end-users which are administrators of their own lists. Here, my thinking is that subscribers (or visitors) of the listinfo interface should ask their questions, not to the mailman site list administrator, but to the list administrator which is not always the same person. From my point of view, only the list administrators should have to ask something to the mailman site list administrator (sysadmin). Another thing: In the listinfo oveview page, you're also exposing the list administrator personal email in the footer (email used while creating the list). From my point of view, that email should be hidden from the visitors and subscribers. That email, always from my point of view should be replaced by the list owner email address (<listname>-owner@VIRTUAL_DOMAIN). Thank you. ** Also affects: mailman (Debian) Importance: Undecided Status: New ** Also affects: mailman (Ubuntu) Importance: Undecided Status: New ** Description changed: Dear project leader, In the Mailman version 2.1.21, you released a fix regarding Mailman- Postfix: - Mailman-Postfix integration will now add mailman@domain entries in data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS which is a host_name of a list. This is so the addresses which are exposed on admin and listinfo overview pages of virtual domains will be deliverable. (LP: #1459236) That fix was a good thing. However there is an identical problem for the site list owner email that is exposed in email notification when you create a new list. Indeed, when you create a new list, there is a notification that is sent to the list owner and which state that it must address all questions to mailman-owner@VIRTUAL_DOMAIN. Therefore, you should considere adding that alias too in the data/virtual-mailman map. - Right now, sending mail to such address result to non-delivery - notification. + Right now, sending mail to such address result to non-delivery. That being said, I would want give you my personal point of view regarding the email addresses that are exposed. Regarding the site list address that is exposed in the listinfo overview page: I tend to think that exposing the site list email address in the listinfo overview page is a mistake. End-users that visit or subscribe to the lists shouldn't have to ask any question to the mailman site list administrator. Think of a shared hosting environment where there is the - sysadmin and end-users which are administrators of their own lists. + sysadmin and the end-users which are administrators of their own lists. Here, my thinking is that subscribers (or visitors) of the listinfo interface should ask their questions, not to the mailman site list administrator, but to the list administrator which is not always the same person. From my point of view, only the list administrators should have to ask something to the mailman site list administrator (sysadmin). Another thing: In the listinfo oveview page, you're also exposing the list administrator personal email in the footer (email used while creating the list). From my point of view, that email should be hidden from the visitors and subscribers. That email, always from my point of - view should be replaced by the list owner email address + view, should be replaced by the list owner email address (<listname>-owner@VIRTUAL_DOMAIN). Thank you. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1694384 Title: Missing list owner email alias in data/virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions

** Summary changed: - Missing list owner email alias in data/virtual-mailman + Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1694384 Title: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions

Thanks for your report. I will fix the mailman-owner@VIRTUAL_DOMAIN issue. I will also address exposing the (mildly obfuscated) list owner addresses in the web page footer ( see the thread at <https://mail.python.org/pipermail/mailman- developers/2017-May/026047.html>). Regarding exposing the site list address on the admin and listinfo overview pages, we can't expose a list owner address here because we don't have a list context so the alternative is to expose nothing. I do not plan to change this at this point. ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: None => 2.1.24 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1694384 Title: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions

** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1694384 Title: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions

** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1694384 Title: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions

@Mark Sapiro Thank for your answer and the fix ;) That is much appreciated. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1694384 Title: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions

** Changed in: mailman Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1694384 Title: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions
participants (3)
-
Launchpad Bug Tracker
-
Laurent Declercq
-
Mark Sapiro