From mark at msapiro.net Wed May 3 01:22:11 2017 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 May 2017 05:22:11 -0000 Subject: [Bug 1602779] Re: Some German language templates are utf-8 encoded References: <20160713171043.14113.66799.malonedeb@soybean.canonical.com> Message-ID: <20170503052212.9983.74749.launchpad@gac.canonical.com> ** Description changed: The templates/de files - adminaddrchgack.txt - masthead.txt - nomoretoday.txt - probe.txt - refuse.txt - subauth.txt + ?adminaddrchgack.txt + ?masthead.txt + ?nomoretoday.txt + ?probe.txt + ?refuse.txt + ?subauth.txt - are incorrectly encoded as utf-8 instead of iso-8859.1. + are incorrectly encoded as utf-8 instead of iso-8859-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/1602779 Title: Some German language templates are utf-8 encoded To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1602779/+subscriptions From ralph at inputplus.co.uk Sun May 7 06:06:31 2017 From: ralph at inputplus.co.uk (Ralph Corderoy) Date: Sun, 07 May 2017 10:06:31 -0000 Subject: [Bug 266269] Re: Default list signature blocks do not follow good netiquette References: <20080905193021.27052.96508.launchpad@forster.canonical.com> Message-ID: <20170507100631.2534.30682.malone@wampee.canonical.com> Because they're not signatures they are included by MUAs in every reply. That reply typically goes back to the list and another list footer is added, that also then gets quoted. See http://lists.edlug.org.uk/pipermail/edlug/2017-February/000431.html The list footer should be intended to be a signature. If the user has a signature then that will precede it and just increase the one signature's size and it will all be stripped in the reply, which is desirable. Many newcomers to mailing lists aren't aware of the signature convention so Mailman should default to using one and explain what it is and why. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266269 Title: Default list signature blocks do not follow good netiquette To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266269/+subscriptions From mark at msapiro.net Sun May 7 10:46:22 2017 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 07 May 2017 14:46:22 -0000 Subject: [Bug 266269] Re: Default list signature blocks do not follow good netiquette References: <20080905193021.27052.96508.launchpad@forster.canonical.com> Message-ID: <20170507144622.2762.17917.malone@wampee.canonical.com> I understand the issue and I could easily implement this, but I won't. This is only one part of a larger problem which is that top posting with full quoting makes a mess on email discussion lists. The main reason I won't change this behavior is there are likely existing lists that don't want the information in the footer to be treated as a sig. With current behavior, the list owner has the ability to make the footer a sig if desired, and to not make it a sig if not desired. This would still be the case if I implemented this by just adding the "-- " line to DEFAULT_MSG_FOOTER in Defaults.py, but there are multiple reasons why I wouldn't do it that way. I would do it in the code that adds the footer and only when adding the footer to the message body and not as a separate MIME part and only when the body does not already contain a "-- " line, but this would preclude the list owner making the footer not a sig. ** Changed in: mailman Milestone: more-information-needed => None -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266269 Title: Default list signature blocks do not follow good netiquette To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266269/+subscriptions From ralph at inputplus.co.uk Sun May 7 11:43:40 2017 From: ralph at inputplus.co.uk (Ralph Corderoy) Date: Sun, 07 May 2017 15:43:40 -0000 Subject: [Bug 266269] Re: Default list signature blocks do not follow good netiquette References: <20080905193021.27052.96508.launchpad@forster.canonical.com> Message-ID: <20170507154340.13732.14446.malone@chaenomeles.canonical.com> I realise I might not have been clear what with joining onto someone else's bug report. I agree it should be the list owner's choice and that they already have this choice just by starting the footer with "--?\n", as I do. Given that, my suggestion is DEFAULT_MSG_FOOTER in Defaults.py gains that prefix so new lists start with a sig and the owner can change it to non-sig rather than the other way around. Existing lists certainly shouldn't be switched. Many list owners don't know about sigs so it's not as if they've made a conscious decision to stick with Mailman's non-sig choice. Making sig the default for new lists would help these owners get it "right". I take your point about not if in a separate MIME part, etc., but my manual sig setting makes it through to a separate MIME part today so altering DEFAULT_MSG_FOOTER would be no worse off. Implementing a new "make footer a sig" Boolean, with all the considerations you mention taken into account, sounds more 3.0-ish. (I've no idea what 3.0 has done in this area.) So prefixing DEFAULT_MSG_FOOTER so an owner can delete the sig prefix seems an easy change and gives a result no worse than my persuading each owner individually that they should switch, once they learn the sig technology exists. A weaker alternative would be to alter DEFAULT_MSG_FOOTER's help text to explain how to make it a sig, and why it's beneficial, referencing https://en.wikipedia.org/wiki/Signature_block#Signatures_in_Usenet_postings -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266269 Title: Default list signature blocks do not follow good netiquette To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266269/+subscriptions From 1525954 at bugs.launchpad.net Mon May 8 12:39:21 2017 From: 1525954 at bugs.launchpad.net (sphakka) Date: Mon, 08 May 2017 16:39:21 -0000 Subject: [Bug 1525954] Re: mailman-2.1.20: option "subject_prefix": prefix trailing blanks are removed when subject lines have non-ASCII characters References: <20151214152550.25123.231.malonedeb@soybean.canonical.com> Message-ID: <149426156109.2425.5101116129433809152.malone@gac.canonical.com> I just gave it a try after reviewing my configuration. Since the patch applies only to subjects with "Re:", it doesn't work on the very first message. Wouldn't it be feasible in all circumstances? -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1525954 Title: mailman-2.1.20: option "subject_prefix": prefix trailing blanks are removed when subject lines have non-ASCII characters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1525954/+subscriptions From mark at msapiro.net Tue May 9 22:02:01 2017 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 10 May 2017 02:02:01 -0000 Subject: [Bug 1525954] Re: mailman-2.1.20: option "subject_prefix": prefix trailing blanks are removed when subject lines have non-ASCII characters References: <20151214152550.25123.231.malonedeb@soybean.canonical.com> Message-ID: <149438172142.2256.2033452169068186116.malone@chaenomeles.canonical.com> It's fairly complicated. I have a possible fix, but it will take me a while to test all combinations of ascii/non-ascii prefixes and subjects and old vs new style prefixes and subjects with and without Re: and prefix. ** Changed in: mailman Status: Fix Released => In Progress ** Changed in: mailman Milestone: 2.1.21rc1 => 2.1.24 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1525954 Title: mailman-2.1.20: option "subject_prefix": prefix trailing blanks are removed when subject lines have non-ASCII characters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1525954/+subscriptions From mark at msapiro.net Fri May 12 15:20:11 2017 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 12 May 2017 19:20:11 -0000 Subject: [Bug 1525954] Re: mailman-2.1.20: option "subject_prefix": prefix trailing blanks are removed when subject lines have non-ASCII characters References: <20151214152550.25123.231.malonedeb@soybean.canonical.com> Message-ID: <149461681196.9287.17886443051142268136.malone@gac.canonical.com> Subject prefixing has been improved to always have a space between the prefix and the subject even with non-ascii in the prefix. This will sometimes result in two spaces when the prefix is non-ascii but the subject is ascii, but this is the lesser evil. (LP: #1525954) ** 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/1525954 Title: mailman-2.1.20: option "subject_prefix": prefix trailing blanks are removed when subject lines have non-ASCII characters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1525954/+subscriptions From mark at msapiro.net Fri May 12 15:40:25 2017 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 12 May 2017 19:40:25 -0000 Subject: [Bug 266269] Re: Default list signature blocks do not follow good netiquette References: <20080905193021.27052.96508.launchpad@forster.canonical.com> Message-ID: <149461802598.9249.16451432428242589735.malone@gac.canonical.com> The values for DEFAULT_DIGEST_FOOTER and DEFAULT_MSG_FOOTER have been changed to use a standard signature separator for DEFAULT_MSG_FOOTER and to remove the unneded line of underscores from DEFAULT_DIGEST_FOOTER. ** Changed in: mailman Status: Won't Fix => Fix Committed ** 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/266269 Title: Default list signature blocks do not follow good netiquette To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266269/+subscriptions From 266269 at bugs.launchpad.net Fri May 12 18:02:48 2017 From: 266269 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 12 May 2017 22:02:48 -0000 Subject: [Bug 266269] Re: Default list signature blocks do not follow good netiquette References: <20080905193021.27052.96508.launchpad@forster.canonical.com> Message-ID: <20170512220252.23273.93008.launchpad@ackee.canonical.com> ** 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/266269 Title: Default list signature blocks do not follow good netiquette To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266269/+subscriptions From mark at msapiro.net Wed May 24 18:10:39 2017 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 24 May 2017 22:10:39 -0000 Subject: [Bug 1693366] [NEW] Setting member_verbosity_threshold to 1 results in moderating first post. Message-ID: <149566383921.22905.10723862354292881550.malonedeb@wampee.canonical.com> Public bug reported: This feature is an anti-spam measure to automatically moderate a user who posts more than a threshold number of times in a defined interval. The test for threshold includes the current message so if the threshold is 1, all users are moderated whenever they post. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1693366 Title: Setting member_verbosity_threshold to 1 results in moderating first post. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1693366/+subscriptions From 1693366 at bugs.launchpad.net Wed May 24 19:05:18 2017 From: 1693366 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Wed, 24 May 2017 23:05:18 -0000 Subject: [Bug 1693366] Re: Setting member_verbosity_threshold to 1 results in moderating first post. References: <149566383921.22905.10723862354292881550.malonedeb@wampee.canonical.com> Message-ID: <20170524230522.8577.73658.launchpad@ackee.canonical.com> ** 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/1693366 Title: Setting member_verbosity_threshold to 1 results in moderating first post. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1693366/+subscriptions From mark at msapiro.net Wed May 24 19:05:26 2017 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 24 May 2017 23:05:26 -0000 Subject: [Bug 1693366] Re: Setting member_verbosity_threshold to 1 results in moderating first post. References: <149566383921.22905.10723862354292881550.malonedeb@wampee.canonical.com> Message-ID: <149566712695.3223.16890471504786326607.launchpad@gac.canonical.com> ** 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/1693366 Title: Setting member_verbosity_threshold to 1 results in moderating first post. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1693366/+subscriptions From mark at msapiro.net Wed May 24 19:01:13 2017 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 24 May 2017 23:01:13 -0000 Subject: [Bug 1664729] Re: Processing a probe bounce from a deleted member throws NotAMemberError References: <20170214214456.29967.71622.malonedeb@gac.canonical.com> Message-ID: <149566687478.3477.6087375308355111251.launchpad@gac.canonical.com> ** 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/1664729 Title: Processing a probe bounce from a deleted member throws NotAMemberError To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1664729/+subscriptions From mark at msapiro.net Wed May 24 19:00:10 2017 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 24 May 2017 23:00:10 -0000 Subject: [Bug 1661810] Re: Certain Malformed list names throw TypeError: in roster CGI References: <20170204060726.14491.70065.malonedeb@soybean.canonical.com> Message-ID: <149566681121.2771.16345302899927050798.launchpad@gac.canonical.com> ** 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/1661810 Title: Certain Malformed list names throw TypeError: in roster CGI To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1661810/+subscriptions From 1694384 at bugs.launchpad.net Tue May 30 03:06:53 2017 From: 1694384 at bugs.launchpad.net (Laurent Declercq) Date: Tue, 30 May 2017 07:06:53 -0000 Subject: [Bug 1694384] [NEW] Missing list owner email alias in data/virtual-mailman Message-ID: <149612801384.18003.8212779029827075590.malonedeb@chaenomeles.canonical.com> 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 at 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 at 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 (-owner at 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 at 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 at 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 at 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 at 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 - (-owner at VIRTUAL_DOMAIN. + (-owner at 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 at 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 at 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 (-owner at 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 at 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 at 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 (-owner at 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 From 1694384 at bugs.launchpad.net Tue May 30 03:29:39 2017 From: 1694384 at bugs.launchpad.net (Laurent Declercq) Date: Tue, 30 May 2017 07:29:39 -0000 Subject: [Bug 1694384] Re: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman References: <149612801384.18003.8212779029827075590.malonedeb@chaenomeles.canonical.com> Message-ID: <149612937942.17705.1023836898315719178.launchpad@chaenomeles.canonical.com> ** Summary changed: - Missing list owner email alias in data/virtual-mailman + Missing mailman-owner at 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 at VIRTUAL_DOMAIN entry in data/virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions From mark at msapiro.net Tue May 30 12:55:54 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 30 May 2017 16:55:54 -0000 Subject: [Bug 1694384] Re: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman References: <149612801384.18003.8212779029827075590.malonedeb@chaenomeles.canonical.com> Message-ID: <149616335463.3514.1389220943062656701.malone@gac.canonical.com> Thanks for your report. I will fix the mailman-owner at VIRTUAL_DOMAIN issue. I will also address exposing the (mildly obfuscated) list owner addresses in the web page footer ( see the thread at ). 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 at VIRTUAL_DOMAIN entry in data/virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions From 1694384 at bugs.launchpad.net Tue May 30 18:08:29 2017 From: 1694384 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Tue, 30 May 2017 22:08:29 -0000 Subject: [Bug 1694384] Re: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman References: <149612801384.18003.8212779029827075590.malonedeb@chaenomeles.canonical.com> Message-ID: <20170530220830.8609.17918.launchpad@ackee.canonical.com> ** 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 at VIRTUAL_DOMAIN entry in data/virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions From mark at msapiro.net Tue May 30 18:20:02 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 30 May 2017 22:20:02 -0000 Subject: [Bug 1694384] Re: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman References: <149612801384.18003.8212779029827075590.malonedeb@chaenomeles.canonical.com> Message-ID: <149618280384.3043.1230826530871038321.launchpad@gac.canonical.com> ** 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 at VIRTUAL_DOMAIN entry in data/virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions From 1694384 at bugs.launchpad.net Tue May 30 19:12:57 2017 From: 1694384 at bugs.launchpad.net (Laurent Declercq) Date: Tue, 30 May 2017 23:12:57 -0000 Subject: [Bug 1694384] Re: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman References: <149612801384.18003.8212779029827075590.malonedeb@chaenomeles.canonical.com> Message-ID: <149618597724.25391.7456939890756864658.malone@soybean.canonical.com> @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 at VIRTUAL_DOMAIN entry in data/virtual-mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1694384/+subscriptions