From ralph at inputplus.co.uk Sat Mar 4 12:55:56 2017 From: ralph at inputplus.co.uk (Ralph Corderoy) Date: Sat, 04 Mar 2017 17:55:56 -0000 Subject: [Bug 266269] Re: Default list signature blocks do not follow good netiquette References: <20080905193021.27052.96508.launchpad@forster.canonical.com> Message-ID: <20170304175557.5834.88472.launchpad@wampee.canonical.com> ** Changed in: mailman Status: New => Confirmed -- 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 Sat Mar 4 13:05:37 2017 From: ralph at inputplus.co.uk (Ralph Corderoy) Date: Sat, 04 Mar 2017 18:05:37 -0000 Subject: [Bug 1670033] [NEW] Text blocks, e.g. msg_footer, might not end with linefeed Message-ID: <20170304180537.7760.14797.malonedeb@chaenomeles.canonical.com> Public bug reported: Mailman 2.1.18-2+deb8u1. msg_footer was edited in the web GUI so the text area limited the cursor to the last line of text; it couldn't move down to a blank line below. The emails comes from Mailman that have this text base64 encoded, and the last line doesn't end with a linefeed, e.g. LS0gCnNpZzAKc2lnMQ==. Mailman should ensure a linefeed is added if one isn't already present, but on using the text block, not editing it so the blank line appears in the GUI as then the user will wonder why they can't remove it. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1670033 Title: Text blocks, e.g. msg_footer, might not end with linefeed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1670033/+subscriptions From mark at msapiro.net Sat Mar 4 14:26:40 2017 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 04 Mar 2017 19:26: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: <20170304192640.7760.83708.malone@chaenomeles.canonical.com> Mailman list footers are not intended to be signatures. ** Changed in: mailman Status: Confirmed => Won't Fix -- 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 Sat Mar 4 14:42:39 2017 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 04 Mar 2017 19:42:39 -0000 Subject: [Bug 1670033] Re: Text blocks, e.g. msg_footer, might not end with linefeed References: <20170304180537.7760.14797.malonedeb@chaenomeles.canonical.com> Message-ID: <20170304194240.5740.97182.malone@wampee.canonical.com> If you position the cursor to the end of the last line, you should be able to press enter/return and add a new line. You should be able to ensure in the web GUI that msg_footer ends with a new-line. If this doesn't work, it would seem to be a browser issue. The base64 encoding is a Debian modification having to to with their changing Mailman's character set for English (and all other languages) to UTF-8. ** Changed in: mailman Status: New => Incomplete -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1670033 Title: Text blocks, e.g. msg_footer, might not end with linefeed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1670033/+subscriptions From ralph at inputplus.co.uk Sat Mar 4 15:36:12 2017 From: ralph at inputplus.co.uk (Ralph Corderoy) Date: Sat, 04 Mar 2017 20:36:12 -0000 Subject: [Bug 1670033] Re: Text blocks, e.g. msg_footer, might not end with linefeed References: <20170304180537.7760.14797.malonedeb@chaenomeles.canonical.com> Message-ID: <20170304203612.22443.28210.malone@gac.canonical.com> Hi Mark, Yes I can add a "blank" line to the end of the text area. My point is, it isn't obvious to the user that they should do this. By doing so they may think, like me, that they're adding an unwanted blank line to the msg_footer, for example. Just as Unix text editors shouldn't produce a text file without a trailing newline, since POSIX mandates a text file is zero or more LF-terminated lines, so I think Mailman has to work around the different UI presented by web-browser text areas and ensure the text it uses from them has a terminating LF. Thanks for the Debian pointer on the base64. I think other encodings would show the lack of final LF too though, e.g. Quoted-Printable of the above base64: --=20 sig0 sig1= -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1670033 Title: Text blocks, e.g. msg_footer, might not end with linefeed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1670033/+subscriptions From 1670033 at bugs.launchpad.net Sat Mar 4 16:24:39 2017 From: 1670033 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Sat, 04 Mar 2017 21:24:39 -0000 Subject: [Bug 1670033] Re: Text blocks, e.g. msg_footer, might not end with linefeed References: <20170304180537.7760.14797.malonedeb@chaenomeles.canonical.com> Message-ID: <20170304212442.7490.48906.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/1670033 Title: Text blocks, e.g. msg_footer, might not end with linefeed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1670033/+subscriptions From mark at msapiro.net Sat Mar 4 16:28:27 2017 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 04 Mar 2017 21:28:27 -0000 Subject: [Bug 1670033] Re: Text blocks, e.g. msg_footer, might not end with linefeed References: <20170304180537.7760.14797.malonedeb@chaenomeles.canonical.com> Message-ID: <20170304212827.6245.21893.malone@wampee.canonical.com> I'm not sure this won't have negative consequences on people/installations that do automated processing on list messages, but I'm willing to try it. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: Incomplete => 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/1670033 Title: Text blocks, e.g. msg_footer, might not end with linefeed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1670033/+subscriptions From ralph at inputplus.co.uk Wed Mar 8 05:36:32 2017 From: ralph at inputplus.co.uk (Ralph Corderoy) Date: Wed, 08 Mar 2017 10:36:32 -0000 Subject: [Bug 1671036] [NEW] Full-width "invisible" Logout button hit by accident Message-ID: <20170308103632.7954.70513.malonedeb@chaenomeles.canonical.com> Public bug reported: On a /mailman/admindb/foo page it might say "There are no pending requests. Click here to reload this page." Aiming at the "Click here" link and being a bit low logs me out. This is due to the right-aligned "Logout" text, far away, being a full-width
that fills under the "Click here" with an invisible button. Looking at the HTML, it's an wrapping a
. That's invalid,
being block level, and pasting the HTML into https://validator.w3.org/ agrees. The should be around just the Logout text to limit the click area. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1671036 Title: Full-width "invisible" Logout button hit by accident To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1671036/+subscriptions From mark at msapiro.net Wed Mar 8 09:41:15 2017 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 08 Mar 2017 14:41:15 -0000 Subject: [Bug 1671036] Re: Full-width "invisible" Logout button hit by accident References: <20170308103632.7954.70513.malonedeb@chaenomeles.canonical.com> Message-ID: <20170308144116.8083.37219.launchpad@chaenomeles.canonical.com> *** This bug is a duplicate of bug 1573623 *** https://bugs.launchpad.net/bugs/1573623 ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Fix Released ** Changed in: mailman Milestone: None => 2.1.23 ** This bug has been marked a duplicate of bug 1573623 admin screen logout link effects entire row -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1671036 Title: Full-width "invisible" Logout button hit by accident To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1671036/+subscriptions From mark at msapiro.net Wed Mar 15 21:57:35 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 16 Mar 2017 01:57:35 -0000 Subject: [Bug 266250] Re: header problems References: <20080905192957.27052.64287.launchpad@forster.canonical.com> Message-ID: <20170316015735.15017.66692.malone@soybean.canonical.com> The old FAQ Wizard link is no good. The current link if anyone is interested is https://wiki.list.org/x/4030707 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266250 Title: header problems To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266250/+subscriptions From mark at msapiro.net Wed Mar 15 22:22:22 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 16 Mar 2017 02:22:22 -0000 Subject: [Bug 1673307] [NEW] msg_header and/or msg_footer can be added as a separate MIME part even if only whitespace. Message-ID: <20170316022222.24941.2737.malonedeb@wampee.canonical.com> Public bug reported: If a content filtered message is other than single part text/plain, msg_header and msg_footer are added as separate MIME parts if they are non-empty even if they consist only of white space. msg_header and msg_footer consisting of only white space should be treated as empty and not added. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1673307 Title: msg_header and/or msg_footer can be added as a separate MIME part even if only whitespace. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1673307/+subscriptions From mark at msapiro.net Wed Mar 15 22:53:38 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 16 Mar 2017 02:53:38 -0000 Subject: [Bug 1673307] Re: msg_header and/or msg_footer can be added as a separate MIME part even if only whitespace. References: <20170316022222.24941.2737.malonedeb@wampee.canonical.com> Message-ID: <20170316025339.32115.41067.launchpad@chaenomeles.canonical.com> ** Description changed: If a content filtered message is other than single part text/plain, msg_header and msg_footer are added as separate MIME parts if they are non-empty even if they consist only of white space. msg_header and msg_footer consisting of only white space should be treated as empty and not added. + + Similar considerations apply to digest_header and digest_footer in both + MIME and, for footer at least, plain digests -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1673307 Title: msg_header and/or msg_footer can be added as a separate MIME part even if only whitespace. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1673307/+subscriptions From 1673307 at bugs.launchpad.net Wed Mar 15 23:40:49 2017 From: 1673307 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Thu, 16 Mar 2017 03:40:49 -0000 Subject: [Bug 1673307] Re: msg_header and/or msg_footer can be added as a separate MIME part even if only whitespace. References: <20170316022222.24941.2737.malonedeb@wampee.canonical.com> Message-ID: <20170316034050.20930.9579.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/1673307 Title: msg_header and/or msg_footer can be added as a separate MIME part even if only whitespace. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1673307/+subscriptions From mark at msapiro.net Wed Mar 15 23:40:52 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 16 Mar 2017 03:40:52 -0000 Subject: [Bug 1673307] Re: msg_header and/or msg_footer can be added as a separate MIME part even if only whitespace. References: <20170316022222.24941.2737.malonedeb@wampee.canonical.com> Message-ID: <20170316034052.24051.76292.launchpad@gac.canonical.com> ** Changed in: mailman Status: New => 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/1673307 Title: msg_header and/or msg_footer can be added as a separate MIME part even if only whitespace. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1673307/+subscriptions From mark at msapiro.net Tue Mar 21 15:18:31 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 21 Mar 2017 19:18:31 -0000 Subject: [Bug 1674802] [NEW] cPanel sites expose an email address for help that usually doesn't work. Message-ID: <20170321191831.19654.2967.malonedeb@soybean.canonical.com> Public bug reported: The listinfo page at http(s)://example.com/mailman/listinfo contains The line "If you are having trouble using the lists, please contact mailman at example.com." and the admin overview at http(s)://example.com/mailman/admin contains the line "(Send questions and comments to mailman at example.com.)". In most cases mailman at example.com is the list posting address for the site list and the site list can be configured to accept messages and deliver them appropriately, but in a multi-domain cPanel installation, there are multiple, disjoint and unrelated domains and only a single site list so most cPanel hosts have difficulty working around this issue in a way that accepts mail to a particular mailman at example.com address and delivers it to the appropriate example.com admin. To avoid this issue, I propose adding a CPANEL_WORKAROUND = No switch which if set to Yes in mm_cfg.py would just not display those lines on the listinfo and admin overview pages. Granted this is really cPanel's problem, but it causes grief for admins of cPanel hosted domains which expose addresses that don't accept mail. The hope is that by providing an easy way for cPanel or a cPanel host to "fix" this, that it will be done. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1674802 Title: cPanel sites expose an email address for help that usually doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1674802/+subscriptions From mark at msapiro.net Tue Mar 21 19:06:09 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 21 Mar 2017 23:06:09 -0000 Subject: [Bug 1674802] Re: cPanel sites expose an email address for help that usually doesn't work. References: <20170321191831.19654.2967.malonedeb@soybean.canonical.com> Message-ID: <20170321230609.25868.75919.malone@gac.canonical.com> It turns out an individual cPanel guest domain admin can create a mailman at example.com list in her domain and configure it to handle mail to that address. It also appears that domain admins have the ability to create forwarders for addresses like mailman at example.com, so the exposure of that address is no more of an issue for cPanel users than for others. ** Changed in: mailman Status: New => Invalid ** Changed in: mailman Milestone: 2.1.24 => 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/1674802 Title: cPanel sites expose an email address for help that usually doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1674802/+subscriptions From 1676905 at bugs.launchpad.net Tue Mar 28 10:49:44 2017 From: 1676905 at bugs.launchpad.net (Anne Summers) Date: Tue, 28 Mar 2017 14:49:44 -0000 Subject: [Bug 1676905] [NEW] mailman links resolve to "500: Internal Error" Message-ID: <20170328144945.1089.72432.malonedeb@gac.canonical.com> Public bug reported: Starting sometime in the last week all of my mailing list links (for moderation, subscriptions, etc.) resolve to "500: Internal Error". I assume this is because my web host (hostgator) upgraded something but I don't know how to fix it and they have been completely unhelpful and just told me to move away from mailman entirely. Here's an example of a link that was working until a week or two ago: http://blacksburgmomsclub.org/mailman/listinfo/bookclub_blacksburgmomsclub.org ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1676905 Title: mailman links resolve to "500: Internal Error" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1676905/+subscriptions From mark at msapiro.net Tue Mar 28 12:03:54 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 28 Mar 2017 16:03:54 -0000 Subject: [Bug 1676905] Re: mailman links resolve to "500: Internal Error" References: <20170328144945.1089.72432.malonedeb@gac.canonical.com> Message-ID: <20170328160355.17285.80388.malone@soybean.canonical.com> This is almost certainly not a Mailman bug per se. Hostgator (or you if you have access) needs to examine the web server logs to see what's logged for the 500 error. Since it affects every Mailman CGI, it is probably related to permissions or possibly a group mismatch error . It appears from your listinfo URL that this is cPanel. It may be a cPanel issue. This is clearly a case of Hostgator only offering Mailman because it comes with cPanel and being completely unwilling or unable to support it. If they can't be more helpful, find a new hosting service for your lists. . ** Changed in: mailman Status: New => Incomplete ** 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/1676905 Title: mailman links resolve to "500: Internal Error" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1676905/+subscriptions