From xeno at thehappy.de Tue Mar 2 13:47:36 2010 From: xeno at thehappy.de (Stefan Ritter) Date: Tue, 02 Mar 2010 12:47:36 -0000 Subject: [Bug 530654] [NEW] Active button on /cgi-bin/mailman/confirm is 'cancel' References: <20100302124736.20181.11966.malonedeb@wampee.canonical.com> Message-ID: <20100302124736.20181.11966.malonedeb@wampee.canonical.com> Public bug reported: Hi, when someone come to the confirm page and enter his/her email-address, the active button should be 'submit', not 'cancel'. Several people want to press the enter-key to send the data, and in this case, he/she cancel the progress. Regards, Stefan ** Affects: mailman Importance: Undecided Status: New -- Active button on /cgi-bin/mailman/confirm is 'cancel' https://bugs.launchpad.net/bugs/530654 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From rkw at dataplex.net Tue Mar 2 21:44:26 2010 From: rkw at dataplex.net (Richard Wackerbarth) Date: Tue, 02 Mar 2010 20:44:26 -0000 Subject: [Bug 530952] [NEW] mailman-3.0.0a5 fails bin/test on MacOSX References: <20100302204426.17012.8396.malonedeb@potassium.ubuntu.com> Message-ID: <20100302204426.17012.8396.malonedeb@potassium.ubuntu.com> Public bug reported: The name of a tempfile is not unique on MacOSX. /tmp//a_file is actually stored in /private/tmp//a_file because MacOSX has a symbolic link for /tmp This causes test_configfile to fail because the faked root is presented as different values by os.path.abspath A patch which creates to same canonical name within the test is provided. ** Affects: mailman Importance: Undecided Status: New -- mailman-3.0.0a5 fails bin/test on MacOSX https://bugs.launchpad.net/bugs/530952 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From rkw at dataplex.net Tue Mar 2 21:44:26 2010 From: rkw at dataplex.net (Richard Wackerbarth) Date: Tue, 02 Mar 2010 20:44:26 -0000 Subject: [Bug 530952] Re: mailman-3.0.0a5 fails bin/test on MacOSX References: <20100302204426.17012.8396.malonedeb@potassium.ubuntu.com> Message-ID: <20100302204426.17012.53432.malone@potassium.ubuntu.com> ** Patch added: "Patch to fix fake_root path in test_configfile" http://launchpadlibrarian.net/40000077/Patch%20to%20Mailman%203.0.txt -- mailman-3.0.0a5 fails bin/test on MacOSX https://bugs.launchpad.net/bugs/530952 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Tue Mar 2 22:24:48 2010 From: barry at canonical.com (Barry Warsaw) Date: Tue, 02 Mar 2010 21:24:48 -0000 Subject: [Bug 530952] Re: mailman-3.0.0a5 fails bin/test on MacOSX References: <20100302204426.17012.8396.malonedeb@potassium.ubuntu.com> Message-ID: <20100302212448.12522.99548.malone@palladium.canonical.com> Thanks! This is already fixed in the lp:mailman branch :) ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 3.0.0a6 -- mailman-3.0.0a5 fails bin/test on MacOSX https://bugs.launchpad.net/bugs/530952 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Wed Mar 3 02:10:33 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Mar 2010 01:10:33 -0000 Subject: [Bug 531081] [NEW] Multiple copies of a single attachment accumulate in a lists archive. References: <20100303011033.25590.51619.malonedeb@soybean.canonical.com> Message-ID: <20100303011033.25590.51619.malonedeb@soybean.canonical.com> Public bug reported: This is not Bug #266749. It is a different issue. After multiple fixes, we have arrived at the current situation wherein if there is a message in a list's digest.mbox which throws an exception in digest processing, the exception is logged and processing aborted. This normally results in the missing digests being noticed and investigated, the log messages being found, the problem message in the digest.mbox fixed or removed, and normal digest processing being resumed. If however, the list allows attachments which are scrubbed from the plain digest, the processing of the digest will store all attachments from messages prior to the one causing the exception. On a busy list, there can be many digests triggered by size before the problem is discovered and each attempt at producing a digest results in the same set of attachments being scrubbed and stored again in the archive potentially wasting much space. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: New -- Multiple copies of a single attachment accumulate in a lists archive. https://bugs.launchpad.net/bugs/531081 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at summersault.com Wed Mar 3 16:04:09 2010 From: mark at summersault.com (Mark Stosberg) Date: Wed, 03 Mar 2010 15:04:09 -0000 Subject: [Bug 266275] Re: can't subscribe - does not like recipient References: <20080905193026.27052.89490.launchpad@forster.canonical.com> Message-ID: <20100303150410.25590.960.malone@soybean.canonical.com> I think this a mail system configuration issue not a mailman bug. Besides, this is a Ubuntu bug tracker, and I don't think SourceForge runs their mailman install on Ubuntu. ** Changed in: mailman Status: New => Invalid -- can't subscribe - does not like recipient https://bugs.launchpad.net/bugs/266275 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Wed Mar 3 17:02:11 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Mar 2010 16:02:11 -0000 Subject: [Bug 266275] Re: can't subscribe - does not like recipient References: <20080905193026.27052.89490.launchpad@forster.canonical.com> Message-ID: <20100303160211.20262.65374.malone@wampee.canonical.com> This is not an Ubuntu bug tracker. It is a Launchpad bug tracker which supports many projects including GNU Mailman. This bug is in the right place for a GNU Mailman bug report. However, I agree that this is not a Mailman bug. The issue appears to be between the originator's qmail and the MTA at Sourceforge. Mailman is not even directly involved. -- can't subscribe - does not like recipient https://bugs.launchpad.net/bugs/266275 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From contact at internux.ch Thu Mar 4 15:55:04 2010 From: contact at internux.ch (=?utf-8?q?C=C3=A9dric_Jeanneret?=) Date: Thu, 04 Mar 2010 14:55:04 -0000 Subject: [Bug 531942] Re: xapian indexer References: <20100304145309.21041.68937.malonedeb@soybean.canonical.com> Message-ID: <20100304145504.21142.35640.malone@soybean.canonical.com> And here's pippermail part. It's a copy of "arch" script, without the lock stuff. Maybe we should modify "arch" so that we can pass a "-no-lock" option... ? ** Attachment added: "pippermail archiver for the previous script" http://launchpadlibrarian.net/40168163/pipermail-archive.py -- xapian indexer https://bugs.launchpad.net/bugs/531942 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From contact at internux.ch Thu Mar 4 15:53:09 2010 From: contact at internux.ch (=?utf-8?q?C=C3=A9dric_Jeanneret?=) Date: Thu, 04 Mar 2010 14:53:09 -0000 Subject: [Bug 531942] [NEW] xapian indexer References: <20100304145309.21041.68937.malonedeb@soybean.canonical.com> Message-ID: <20100304145309.21041.68937.malonedeb@soybean.canonical.com> Public bug reported: Hello, As it was discussed on mailman-users ML[1], here is my xapian indexer code. You'll find two scripts : - the one which will replace the "normal" archiver - the one called to update pippermail archives Depends: - xappy [2] How it works : just set the variable PUBLIC_EXTERNAL_ARCHIVER and/or PRIVATE_EXTERNAL_ARCHIVER so that it points on archive-and-index.py script Ex: PUBLIC_EXTERNAL_ARCHIVER = '/var/local/bin/archive-and-index.py %(hostname) %(listname)' Change if necessary the path for pipermail-archive.py if necessary. Reload mailman.... and that's all ;) I'd like to really thank Mark Sapiro for his help :) Feel free to use it, and to comment it out. I tested it some times on our server, it works just fine. Best regards, C. [1] http://mail.python.org/pipermail/mailman-users/2010-February/068899.html and following mails [2] http://code.google.com/p/xappy/ ** Affects: mailman Importance: Undecided Status: New -- xapian indexer https://bugs.launchpad.net/bugs/531942 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From contact at internux.ch Thu Mar 4 15:53:09 2010 From: contact at internux.ch (=?utf-8?q?C=C3=A9dric_Jeanneret?=) Date: Thu, 04 Mar 2010 14:53:09 -0000 Subject: [Bug 531942] Re: xapian indexer References: <20100304145309.21041.68937.malonedeb@soybean.canonical.com> Message-ID: <20100304145310.21041.85436.malone@soybean.canonical.com> ** Attachment added: "archive an index incomming mails" http://launchpadlibrarian.net/40168072/archive-and-index.py -- xapian indexer https://bugs.launchpad.net/bugs/531942 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Sat Mar 6 21:38:32 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 06 Mar 2010 20:38:32 -0000 Subject: [Bug 533468] [NEW] admindb interface applies action to not yet seen messages from user. References: <20100306203832.2495.93188.malonedeb@palladium.canonical.com> Message-ID: <20100306203832.2495.93188.malonedeb@palladium.canonical.com> Public bug reported: If the moderator has retrieved the admindb overview page and another message arrives and is held from a user who already has one or more held messages displayed on the page, and the moderator applies an action or the default "discard all messages marked Defer" to that user's messages, the same action will be applied to the newly arrived message even though it wasn't displayed. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: New -- admindb interface applies action to not yet seen messages from user. https://bugs.launchpad.net/bugs/533468 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Sat Mar 6 23:04:03 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 06 Mar 2010 22:04:03 -0000 Subject: [Bug 530654] Re: Active button on /cgi-bin/mailman/confirm is 'cancel' References: <20100302124736.20181.11966.malonedeb@wampee.canonical.com> Message-ID: <20100306220403.24575.95808.malone@wampee.canonical.com> Actually, the page as sent has no active button. If one presses enter with MSIE without first selecting a button (e.g. by tabbing), neither button's data will be sent, and Mailman will resend the confirmation page. The other browsers I tried (Firefox, Opera, Safari and Google Chrome) all send the data for the first submit button on the page. I reordered the buttons so this is the 'subscribe' rather than the 'cancel' button. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.14 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) ** Branch linked: lp:mailman/2.1 -- Active button on /cgi-bin/mailman/confirm is 'cancel' https://bugs.launchpad.net/bugs/530654 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Sat Mar 6 23:05:21 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 06 Mar 2010 22:05:21 -0000 Subject: [Bug 533468] Re: admindb interface applies action to not yet seen messages from user. References: <20100306203832.2495.93188.malonedeb@palladium.canonical.com> Message-ID: <20100306220522.31337.30143.launchpad@soybean.canonical.com> ** Changed in: mailman Status: New => Fix Committed ** Branch linked: lp:mailman/2.1 -- admindb interface applies action to not yet seen messages from user. https://bugs.launchpad.net/bugs/533468 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From keturn at keturn.net Fri Mar 12 08:36:28 2010 From: keturn at keturn.net (Kevin Turner) Date: Fri, 12 Mar 2010 07:36:28 -0000 Subject: [Bug 266862] Re: Feature Request -- OpenID support References: <20080905194310.1806.42729.launchpad@forster.canonical.com> Message-ID: <20100312073629.13954.98304.launchpad@potassium.ubuntu.com> *** This bug is a duplicate of bug 266836 *** https://bugs.launchpad.net/bugs/266836 ** This bug has been marked a duplicate of bug 266836 support openid / yadis -- Feature Request -- OpenID support https://bugs.launchpad.net/bugs/266862 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From contact at internux.ch Tue Mar 16 09:03:16 2010 From: contact at internux.ch (=?utf-8?q?C=C3=A9dric_Jeanneret?=) Date: Tue, 16 Mar 2010 08:03:16 -0000 Subject: [Bug 531942] Re: xapian indexer References: <20100304145309.21041.68937.malonedeb@soybean.canonical.com> Message-ID: <20100316080316.4275.86185.malone@wampee.canonical.com> Please discard all previous attachments (seems I cannot remove them, Mark). According to http://wiki.list.org/x/RAKJ I rewrite my indexer; you'll find it attached with this comment. Thank you Mark for the time you took on my case! ** Attachment added: "archive and index mailman incoming mail - the good way" http://launchpadlibrarian.net/40995991/archive-and-index.py -- xapian indexer https://bugs.launchpad.net/bugs/531942 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From p at state-of-mind.de Sun Mar 21 19:18:21 2010 From: p at state-of-mind.de (Patrick Ben Koetter) Date: Sun, 21 Mar 2010 18:18:21 -0000 Subject: [Bug 543618] [NEW] test breaks if existing mailman.cfg is found References: <20100321181821.13322.75963.malonedeb@potassium.ubuntu.com> Message-ID: <20100321181821.13322.75963.malonedeb@potassium.ubuntu.com> Public bug reported: The test program reports an error if it detects an existing mailman.cfg: Failure in test test_current_working_directory (mailman.tests.test_configfile.TestConfigFileSearch) Traceback (most recent call last): File "/usr/lib/python2.6/unittest.py", line 279, in run testMethod() File "/root/mailman/src/mailman/tests/test_configfile.py", line 107, in test_current_working_directory self.assertEqual(found, config_file) File "/usr/lib/python2.6/unittest.py", line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: '/etc/mailman.cfg' != u'/tmp/tmpVfAIyB/home/alex/mailman/hacking/mailman.cfg' I believe it should not do this. It should either silently ignore the difference or use the test mailman.cfg or ... but not break. ** Affects: mailman Importance: Undecided Status: New ** Tags: 3.0 mailman -- test breaks if existing mailman.cfg is found https://bugs.launchpad.net/bugs/543618 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From p at state-of-mind.de Sun Mar 21 19:22:56 2010 From: p at state-of-mind.de (Patrick Ben Koetter) Date: Sun, 21 Mar 2010 18:22:56 -0000 Subject: [Bug 543620] [NEW] command mailman info fails when Database url does not exist References: <20100321182256.2177.85290.malonedeb@soybean.canonical.com> Message-ID: <20100321182256.2177.85290.malonedeb@soybean.canonical.com> Public bug reported: The command "mailman info" crashes if the database path "url" points to a location that does not exist yet: root at mailman:~/mailman/bin# ./mailman info Traceback (most recent call last): File "./mailman", line 32, in mailman.bin.mailman.main() File "/root/mailman/src/mailman/bin/mailman.py", line 98, in main initialize(config_file) File "/root/mailman/src/mailman/core/initialize.py", line 175, in initialize initialize_2(propagate_logs=propagate_logs) File "/root/mailman/src/mailman/core/initialize.py", line 146, in initialize_2 database.initialize(debug) File "/root/mailman/src/mailman/database/stock.py", line 64, in initialize self._create(debug) File "/root/mailman/src/mailman/database/stock.py", line 98, in _create touch(url) File "/root/mailman/src/mailman/database/stock.py", line 141, in touch fd = os.open(path, os.O_WRONLY | os.O_NONBLOCK | os.O_CREAT, 0666) OSError: [Errno 2] No such file or directory: '/opt/mailman/data/mailman.db' ** Affects: mailman Importance: Undecided Status: New ** Tags: 3.0 mailman -- command mailman info fails when Database url does not exist https://bugs.launchpad.net/bugs/543620 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From p at state-of-mind.de Sun Mar 21 19:31:08 2010 From: p at state-of-mind.de (Patrick Ben Koetter) Date: Sun, 21 Mar 2010 18:31:08 -0000 Subject: [Bug 543627] [NEW] mailman command does not initialize directory structure on first run References: <20100321183108.4275.88077.malonedeb@wampee.canonical.com> Message-ID: <20100321183108.4275.88077.malonedeb@wampee.canonical.com> Public bug reported: Contrary to "src/mailman/docs/START.txt" which says Run the ``bin/mailman info`` command to see which configuration file Mailman will use, and where it will put its database file. The first time you run this, Mailman will also create any necessary run-time directories and log files. neither the mailman command alone nor running it with option "info" creates the initial directory structure. If you go with the default settings in mailman.cfg you probably won't notice because you are within the correct directory structure. But if you set "var_dir: /opt/mailman" in e.g. /etc/mailman.cfg things break. I believe fixing this would also fix ticket #543620. ** Affects: mailman Importance: Undecided Status: New -- mailman command does not initialize directory structure on first run https://bugs.launchpad.net/bugs/543627 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 21 22:39:33 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 21 Mar 2010 21:39:33 -0000 Subject: [Bug 543627] Re: mailman command does not initialize directory structure on first run References: <20100321183108.4275.88077.malonedeb@wampee.canonical.com> Message-ID: <20100321213933.11592.82004.malone@gandwana.canonical.com> Make that bug 543620 ** Changed in: mailman Milestone: None => 3.0.0a6 -- mailman command does not initialize directory structure on first run https://bugs.launchpad.net/bugs/543627 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 21 22:38:56 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 21 Mar 2010 21:38:56 -0000 Subject: [Bug 543620] Re: command mailman info fails when Database url does not exist References: <20100321182256.2177.85290.malonedeb@soybean.canonical.com> Message-ID: <20100321213858.19123.52265.launchpad@soybean.canonical.com> ** Changed in: mailman Milestone: None => 3.0.0a6 -- command mailman info fails when Database url does not exist https://bugs.launchpad.net/bugs/543620 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 21 22:38:14 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 21 Mar 2010 21:38:14 -0000 Subject: [Bug 543618] Re: test breaks if existing mailman.cfg is found References: <20100321181821.13322.75963.malonedeb@potassium.ubuntu.com> Message-ID: <20100321213815.19123.45673.launchpad@soybean.canonical.com> ** Changed in: mailman Milestone: None => 3.0.0a6 -- test breaks if existing mailman.cfg is found https://bugs.launchpad.net/bugs/543618 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From p at state-of-mind.de Mon Mar 22 21:31:24 2010 From: p at state-of-mind.de (Patrick Ben Koetter) Date: Mon, 22 Mar 2010 20:31:24 -0000 Subject: [Bug 544477] [NEW] setting localhost in postfix_lmtp breaks delivery References: <20100322203125.20764.52512.malonedeb@potassium.ubuntu.com> Message-ID: <20100322203125.20764.52512.malonedeb@potassium.ubuntu.com> Public bug reported: Setting localhost in postfix_lmtp works against Postfix defaults and breaks delivery. Reason: The Postfix lmtp client only uses dns queries by default to search for hostnames. If the DNS server does not provide an answer for "localhost" delivery from the lmtp client to mailman fails. Solution: Provide "127.0.0.1" instead of "localhost". This does not require DNS and is even faster because it saves DNS lookups. Example: hey2 at mailman.state-of-mind.de lmtp:[localhost.localdomain]:8024 ** Affects: mailman Importance: Undecided Status: New ** Tags: 3.0 mailman -- setting localhost in postfix_lmtp breaks delivery https://bugs.launchpad.net/bugs/544477 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From p at state-of-mind.de Mon Mar 22 21:36:24 2010 From: p at state-of-mind.de (Patrick Ben Koetter) Date: Mon, 22 Mar 2010 20:36:24 -0000 Subject: [Bug 544477] Re: setting localhost in postfix_lmtp breaks delivery References: <20100322203125.20764.52512.malonedeb@potassium.ubuntu.com> Message-ID: <20100322203624.11240.40359.malone@wampee.canonical.com> Silly me Provided a bad example. Here's the good one: hey2 at mailman.state-of-mind.de lmtp:[127.0.0.1]:8024 -- setting localhost in postfix_lmtp breaks delivery https://bugs.launchpad.net/bugs/544477 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From cheeseli at hotmail.com Wed Mar 24 07:41:56 2010 From: cheeseli at hotmail.com (LI Rui Bin) Date: Wed, 24 Mar 2010 06:41:56 -0000 Subject: [Bug 545772] [NEW] An error in Simplified Chinese translation References: <20100324064157.25773.44815.malonedeb@soybean.canonical.com> Message-ID: <20100324064157.25773.44815.malonedeb@soybean.canonical.com> Public bug reported: See the patches. ** Affects: mailman Importance: Undecided Status: New -- An error in Simplified Chinese translation https://bugs.launchpad.net/bugs/545772 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From cheeseli at hotmail.com Wed Mar 24 07:41:56 2010 From: cheeseli at hotmail.com (LI Rui Bin) Date: Wed, 24 Mar 2010 06:41:56 -0000 Subject: [Bug 545772] Re: An error in Simplified Chinese translation References: <20100324064157.25773.44815.malonedeb@soybean.canonical.com> Message-ID: <20100324064157.25773.40597.malone@soybean.canonical.com> ** Patch added: "Patch for 2.1 branch" http://launchpadlibrarian.net/41809744/zh_CN-mailman.po-2.1.patch -- An error in Simplified Chinese translation https://bugs.launchpad.net/bugs/545772 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From cheeseli at hotmail.com Wed Mar 24 07:42:54 2010 From: cheeseli at hotmail.com (LI Rui Bin) Date: Wed, 24 Mar 2010 06:42:54 -0000 Subject: [Bug 545772] Re: An error in Simplified Chinese translation References: <20100324064157.25773.44815.malonedeb@soybean.canonical.com> Message-ID: <20100324064255.19500.69421.malone@wampee.canonical.com> Patch for 3.0 branch ** Patch added: "Patch for 3.0 branch" http://launchpadlibrarian.net/41809798/zh_CN-mailman.po-3.0.patch -- An error in Simplified Chinese translation https://bugs.launchpad.net/bugs/545772 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Fri Mar 26 02:23:29 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 26 Mar 2010 01:23:29 -0000 Subject: [Bug 545772] Re: An error in Simplified Chinese translation References: <20100324064157.25773.44815.malonedeb@soybean.canonical.com> Message-ID: <20100326012330.20764.58671.launchpad@potassium.ubuntu.com> ** Branch linked: lp:mailman/2.1 -- An error in Simplified Chinese translation https://bugs.launchpad.net/bugs/545772 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Fri Mar 26 02:32:07 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 26 Mar 2010 01:32:07 -0000 Subject: [Bug 545772] Re: An error in Simplified Chinese translation References: <20100324064157.25773.44815.malonedeb@soybean.canonical.com> Message-ID: <20100326013207.19409.99392.malone@wampee.canonical.com> I have to take your word that this patch is an improvement. Google translate says: msgid "View this page in" -msgstr "In this view the page" +msgstr "Select the language used by this page:" and neither the old nor the new is very satisfying, but I will assume this is just Google not doing a perfect job. I have committed the 2.1 patch. The web interface is being completely redone for Mailman 3.0, and the patch won't be applicable, but you are invited to join in the 3.0 translation effort when it gets underway. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.14 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- An error in Simplified Chinese translation https://bugs.launchpad.net/bugs/545772 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 00:40:41 2010 From: barry at canonical.com (Barry Warsaw) Date: Sat, 27 Mar 2010 23:40:41 -0000 Subject: [Bug 544477] Re: setting localhost in postfix_lmtp breaks delivery References: <20100322203125.20764.52512.malonedeb@potassium.ubuntu.com> Message-ID: <20100327234041.16706.88707.malone@gandwana.canonical.com> Is the suggestion then to change lmtp_host in schema.cfg to 127.0.0.1 instead of localhost? Is there anything else that needs to be done? -- setting localhost in postfix_lmtp breaks delivery https://bugs.launchpad.net/bugs/544477 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 00:49:11 2010 From: barry at canonical.com (Barry Warsaw) Date: Sat, 27 Mar 2010 23:49:11 -0000 Subject: [Bug 543620] Re: command mailman info fails when Database url does not exist References: <20100321182256.2177.85290.malonedeb@soybean.canonical.com> Message-ID: <20100327234911.6651.56760.malone@palladium.canonical.com> Can you post your mailman.cfg file? 'bin/mailman info' will try to create the mailman.db file if it doesn't exist, but of course that could fail if say the process doesn't have permission to create the paths, e.g. -----mailman.cfg----- [mailman] layout: foo [paths.foo] var_dir: /foo/mailman ---------- % bin/mailman info Traceback (most recent call last): File "bin/mailman", line 31, in mailman.bin.mailman.main() File "/home/barry/projects/mailman/3.0/src/mailman/bin/mailman.py", line 98, in main initialize(config_file) File "/home/barry/projects/mailman/3.0/src/mailman/core/initialize.py", line 174, in initialize initialize_1(config_path) File "/home/barry/projects/mailman/3.0/src/mailman/core/initialize.py", line 117, in initialize_1 mailman.config.config.load(config_path) File "/home/barry/projects/mailman/3.0/src/mailman/config/config.py", line 106, in load self._post_process() File "/home/barry/projects/mailman/3.0/src/mailman/config/config.py", line 126, in _post_process Switchboard.initialize() File "/home/barry/projects/mailman/3.0/src/mailman/queue/__init__.py", line 94, in initialize config.switchboards[name] = Switchboard(name, path) File "/home/barry/projects/mailman/3.0/src/mailman/queue/__init__.py", line 119, in __init__ makedirs(self.queue_directory, 0770) File "/home/barry/projects/mailman/3.0/src/mailman/utilities/filesystem.py", line 66, in makedirs os.makedirs(path, mode) File "/usr/lib/python2.6/os.py", line 150, in makedirs makedirs(head, mode) File "/usr/lib/python2.6/os.py", line 150, in makedirs makedirs(head, mode) File "/usr/lib/python2.6/os.py", line 150, in makedirs makedirs(head, mode) File "/usr/lib/python2.6/os.py", line 157, in makedirs mkdir(name, mode) OSError: [Errno 13] Permission denied: '/foo' -- command mailman info fails when Database url does not exist https://bugs.launchpad.net/bugs/543620 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 01:08:18 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 00:08:18 -0000 Subject: [Bug 544477] Re: setting localhost in postfix_lmtp breaks delivery References: <20100322203125.20764.52512.malonedeb@potassium.ubuntu.com> Message-ID: <20100328000819.9985.35299.launchpad@potassium.ubuntu.com> ** Changed in: mailman Status: New => Confirmed -- setting localhost in postfix_lmtp breaks delivery https://bugs.launchpad.net/bugs/544477 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From 544477 at bugs.launchpad.net Sun Mar 28 01:08:18 2010 From: 544477 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Sun, 28 Mar 2010 00:08:18 -0000 Subject: [Bug 544477] Re: setting localhost in postfix_lmtp breaks delivery References: <20100322203125.20764.52512.malonedeb@potassium.ubuntu.com> Message-ID: <20100328000823.26496.32561.launchpad@loganberry.canonical.com> ** Branch linked: lp:mailman -- setting localhost in postfix_lmtp breaks delivery https://bugs.launchpad.net/bugs/544477 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 01:08:45 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 00:08:45 -0000 Subject: [Bug 544477] Re: setting localhost in postfix_lmtp breaks delivery References: <20100322203125.20764.52512.malonedeb@potassium.ubuntu.com> Message-ID: <20100328000845.6651.39796.malone@palladium.canonical.com> r6897 ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a6 ** Changed in: mailman Status: Confirmed => Fix Committed -- setting localhost in postfix_lmtp breaks delivery https://bugs.launchpad.net/bugs/544477 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 01:07:22 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 00:07:22 -0000 Subject: [Bug 543618] Re: test breaks if existing mailman.cfg is found References: <20100321181821.13322.75963.malonedeb@potassium.ubuntu.com> Message-ID: <20100328000722.16706.77438.malone@gandwana.canonical.com> Do you by any chance have $MAILMAN_CONFIG_FILE environment variable set? That's the only way I can see triggering this failure. Still that should not cause test failures because tests should not be dependent on the environment. I'll fix that. -- test breaks if existing mailman.cfg is found https://bugs.launchpad.net/bugs/543618 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 01:07:36 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 00:07:36 -0000 Subject: [Bug 543618] Re: test breaks if existing mailman.cfg is found References: <20100321181821.13322.75963.malonedeb@potassium.ubuntu.com> Message-ID: <20100328000736.16706.10582.malone@gandwana.canonical.com> r6897 ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Status: Fix Committed => Confirmed ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: Confirmed => Fix Committed -- test breaks if existing mailman.cfg is found https://bugs.launchpad.net/bugs/543618 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From 543618 at bugs.launchpad.net Sun Mar 28 01:08:18 2010 From: 543618 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Sun, 28 Mar 2010 00:08:18 -0000 Subject: [Bug 543618] Re: test breaks if existing mailman.cfg is found References: <20100321181821.13322.75963.malonedeb@potassium.ubuntu.com> Message-ID: <20100328000822.26496.53927.launchpad@loganberry.canonical.com> ** Branch linked: lp:mailman -- test breaks if existing mailman.cfg is found https://bugs.launchpad.net/bugs/543618 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 01:09:12 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 00:09:12 -0000 Subject: [Bug 543620] Re: command mailman info fails when Database url does not exist References: <20100321182256.2177.85290.malonedeb@soybean.canonical.com> Message-ID: <20100328000912.5798.96102.launchpad@soybean.canonical.com> ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Status: New => Incomplete ** Also affects: mailman/3.0 Importance: Undecided Assignee: Barry Warsaw (barry) Status: Incomplete ** Tags added: mailman3 ** Tags removed: 3.0 mailman -- command mailman info fails when Database url does not exist https://bugs.launchpad.net/bugs/543620 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 01:11:45 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 00:11:45 -0000 Subject: [Bug 490114] Re: Mailman should be compliant with the Filesystem Hierarchy Standard References: <20091129221530.31720.38380.malonedeb@potassium.ubuntu.com> Message-ID: <20100328001145.6651.30961.launchpad@palladium.canonical.com> ** Tags added: mailman3 -- Mailman should be compliant with the Filesystem Hierarchy Standard https://bugs.launchpad.net/bugs/490114 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From p at state-of-mind.de Sun Mar 28 09:02:51 2010 From: p at state-of-mind.de (Patrick Ben Koetter) Date: Sun, 28 Mar 2010 07:02:51 -0000 Subject: [Bug 544477] Re: setting localhost in postfix_lmtp breaks delivery References: <20100322203125.20764.52512.malonedeb@potassium.ubuntu.com> Message-ID: <20100328070251.20764.7255.malone@potassium.ubuntu.com> Yes, the suggestion is to change lmtp_host in schema.cfg to 127.0.0.1 instead of localhost? At the moment I don't see anything else that needs to be done? -- setting localhost in postfix_lmtp breaks delivery https://bugs.launchpad.net/bugs/544477 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From p at state-of-mind.de Sun Mar 28 09:05:06 2010 From: p at state-of-mind.de (Patrick Ben Koetter) Date: Sun, 28 Mar 2010 07:05:06 -0000 Subject: [Bug 543618] Re: test breaks if existing mailman.cfg is found References: <20100321181821.13322.75963.malonedeb@potassium.ubuntu.com> Message-ID: <20100328070506.8120.60122.malone@wampee.canonical.com> Well spotted. I have it set on the machine: p at mailman:~$ set | grep MAILMAN_CONFIG_FILE MAILMAN_CONFIG_FILE=/etc/mailman.cfg -- test breaks if existing mailman.cfg is found https://bugs.launchpad.net/bugs/543618 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From p at state-of-mind.de Sun Mar 28 09:09:17 2010 From: p at state-of-mind.de (Patrick Ben Koetter) Date: Sun, 28 Mar 2010 07:09:17 -0000 Subject: [Bug 543620] Re: command mailman info fails when Database url does not exist References: <20100321182256.2177.85290.malonedeb@soybean.canonical.com> Message-ID: <20100328070917.25773.65631.malone@soybean.canonical.com> When the error occured /opt/mailman existed AND /etc/mailman.cfg used to be like this: p at mailman:~$ cat /etc/mailman.cfg [mailman] site_owner: postmaster at state-of-mind.de # Which paths.* file system layout to use. layout: dev [paths.master] var_dir: /opt/mailman # [database] # The class implementing the IDatabase. # class: mailman.database.stock.StockDatabase # Use this to set the Storm database engine URL. You generally have one # primary database connection for all of Mailman. List data and most rosters # will store their data in this database, although external rosters may access # other databases in their own way. This string supports standard # 'configuration' substitutions. # url: sqlite:///opt/mailman/data/mailman.db # debug: no -- command mailman info fails when Database url does not exist https://bugs.launchpad.net/bugs/543620 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 23:09:43 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 21:09:43 -0000 Subject: [Bug 497968] Re: Need a 'no-daemonize' option for '/bin/mailman start' References: <20091217213007.23975.78442.malonedeb@wampee.canonical.com> Message-ID: <20100328210943.16706.19020.launchpad@gandwana.canonical.com> ** Tags added: mailman3 -- Need a 'no-daemonize' option for '/bin/mailman start' https://bugs.launchpad.net/bugs/497968 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 23:11:48 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 21:11:48 -0000 Subject: [Bug 526143] Re: List-Post header should be retained in MIME digest messages References: <20100223005814.14825.18826.malonedeb@soybean.canonical.com> Message-ID: <20100328211149.9985.21312.launchpad@potassium.ubuntu.com> ** Tags added: mailman3 -- List-Post header should be retained in MIME digest messages https://bugs.launchpad.net/bugs/526143 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 23:11:30 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 21:11:30 -0000 Subject: [Bug 518517] Re: Add the equivalent of postconf(1) References: <20100207193615.31330.60613.malonedeb@soybean.canonical.com> Message-ID: <20100328211130.6651.32246.launchpad@palladium.canonical.com> ** Tags added: mailman3 -- Add the equivalent of postconf(1) https://bugs.launchpad.net/bugs/518517 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 23:11:10 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 21:11:10 -0000 Subject: [Bug 514625] Re: Mailman 3 member functions should "guess" address membership References: <20100130060432.12561.63827.malonedeb@gandwana.canonical.com> Message-ID: <20100328211110.16706.49066.launchpad@gandwana.canonical.com> ** Tags added: mailman3 -- Mailman 3 member functions should "guess" address membership https://bugs.launchpad.net/bugs/514625 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 23:23:26 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 21:23:26 -0000 Subject: [Bug 543620] Re: command mailman info fails when Database url does not exist References: <20100321182256.2177.85290.malonedeb@soybean.canonical.com> Message-ID: <20100328212326.16706.46081.malone@gandwana.canonical.com> I just noticed a problem with the mailman.cfg file you posted. You've set the layout to be 'dev' but you're overriding var_dir in the [paths.master] section. That doesn't match, so it's not picking that up. You can verify by running bin/mailman info -p See if s/paths.master/paths.dev/ fixes your problem. -- command mailman info fails when Database url does not exist https://bugs.launchpad.net/bugs/543620 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 23:24:03 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 21:24:03 -0000 Subject: [Bug 543620] Re: command mailman info fails when Database url does not exist References: <20100321182256.2177.85290.malonedeb@soybean.canonical.com> Message-ID: <20100328212403.6651.87351.malone@palladium.canonical.com> BTW I am going to change 'bin/mailman info --paths/-p' to '--verbose/-v' in the trunk ;) -- command mailman info fails when Database url does not exist https://bugs.launchpad.net/bugs/543620 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From p at state-of-mind.de Sun Mar 28 23:43:22 2010 From: p at state-of-mind.de (Patrick Ben Koetter) Date: Sun, 28 Mar 2010 21:43:22 -0000 Subject: [Bug 543620] Re: command mailman info fails when Database url does not exist References: <20100321182256.2177.85290.malonedeb@soybean.canonical.com> <20100328212326.16706.46081.malone@gandwana.canonical.com> Message-ID: <20100328214322.GB1920@state-of-mind.de> * Barry Warsaw <543620 at bugs.launchpad.net>: > I just noticed a problem with the mailman.cfg file you posted. You've > set the layout to be 'dev' but you're overriding var_dir in the > [paths.master] section. That doesn't match, so it's not picking that > up. You can verify by running > > bin/mailman info -p > > See if > > s/paths.master/paths.dev/ > > fixes your problem. I noticed that too when I posted the config to you. The problem probably is - which is good in this case - that I am not an experienced python user nor developer and the relation between the two didn't strike me. I think I've even looked for a correlation in the original mailman/../mailman.cfg and didn't find one. Anyway. I will change it and see what happens. p at rick > > -- > command mailman info fails when Database url does not exist > https://bugs.launchpad.net/bugs/543620 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in GNU Mailman: Incomplete > Status in GNU Mailman 3.0 series: Incomplete > > Bug description: > The command "mailman info" crashes if the database path "url" points to a location that does not exist yet: > > root at mailman:~/mailman/bin# ./mailman info > Traceback (most recent call last): > File "./mailman", line 32, in > mailman.bin.mailman.main() > File "/root/mailman/src/mailman/bin/mailman.py", line 98, in main > initialize(config_file) > File "/root/mailman/src/mailman/core/initialize.py", line 175, in initialize > initialize_2(propagate_logs=propagate_logs) > File "/root/mailman/src/mailman/core/initialize.py", line 146, in initialize_2 > database.initialize(debug) > File "/root/mailman/src/mailman/database/stock.py", line 64, in initialize > self._create(debug) > File "/root/mailman/src/mailman/database/stock.py", line 98, in _create > touch(url) > File "/root/mailman/src/mailman/database/stock.py", line 141, in touch > fd = os.open(path, os.O_WRONLY | os.O_NONBLOCK | os.O_CREAT, 0666) > OSError: [Errno 2] No such file or directory: '/opt/mailman/data/mailman.db' > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/mailman/+bug/543620/+subscribe -- state of mind Digitale Kommunikation http://www.state-of-mind.de Franziskanerstra?e 15 Telefon +49 89 3090 4664 81669 M?nchen Telefax +49 89 3090 4666 Amtsgericht M?nchen Partnerschaftsregister PR 563 -- command mailman info fails when Database url does not exist https://bugs.launchpad.net/bugs/543620 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Sun Mar 28 23:42:07 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 21:42:07 -0000 Subject: [Bug 497968] Re: Need a 'no-daemonize' option for '/bin/mailman start' References: <20091217213007.23975.78442.malonedeb@wampee.canonical.com> Message-ID: <20100328214207.5798.11248.malone@soybean.canonical.com> I've decided to set this to Won't Fix because in Mailman 3, bin/mailman start is little more than a wrapper around bin/master, which does not daemonize. This has all been refactored for simplicity so if you really wanted a no-daemonizing 'bin/mailman start', you really should just be calling 'bin/master' instead. ** Changed in: mailman/3.0 Status: Triaged => Won't Fix -- Need a 'no-daemonize' option for '/bin/mailman start' https://bugs.launchpad.net/bugs/497968 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Mon Mar 29 00:20:54 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 28 Mar 2010 22:20:54 -0000 Subject: [Bug 526143] Re: List-Post header should be retained in MIME digest messages References: <20100223005814.14825.18826.malonedeb@soybean.canonical.com> Message-ID: <20100328222055.16706.80939.launchpad@gandwana.canonical.com> ** Changed in: mailman/3.0 Status: Triaged => Fix Committed -- List-Post header should be retained in MIME digest messages https://bugs.launchpad.net/bugs/526143 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Mon Mar 29 04:41:12 2010 From: barry at canonical.com (Barry Warsaw) Date: Mon, 29 Mar 2010 02:41:12 -0000 Subject: [Bug 543620] Re: command mailman info fails when Database url does not exist References: <20100321182256.2177.85290.malonedeb@soybean.canonical.com> Message-ID: <20100329024113.16706.76782.malone@gandwana.canonical.com> Cool, let me know. I do think we could use better documentation for the configuration options. ;/ -- command mailman info fails when Database url does not exist https://bugs.launchpad.net/bugs/543620 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From p at state-of-mind.de Mon Mar 29 12:53:10 2010 From: p at state-of-mind.de (Patrick Ben Koetter) Date: Mon, 29 Mar 2010 10:53:10 -0000 Subject: [Bug 543620] Re: command mailman info fails when Database url does not exist References: <20100321182256.2177.85290.malonedeb@soybean.canonical.com> <20100328212326.16706.46081.malone@gandwana.canonical.com> Message-ID: <20100329105310.GD1908@state-of-mind.de> * Barry Warsaw <543620 at bugs.launchpad.net>: > I just noticed a problem with the mailman.cfg file you posted. You've > set the layout to be 'dev' but you're overriding var_dir in the > [paths.master] section. That doesn't match, so it's not picking that > up. You can verify by running > > bin/mailman info -p > > See if > > s/paths.master/paths.dev/ > > fixes your problem. It fixed the problem. p at rick -- state of mind Digitale Kommunikation http://www.state-of-mind.de Franziskanerstra?e 15 Telefon +49 89 3090 4664 81669 M?nchen Telefax +49 89 3090 4666 Amtsgericht M?nchen Partnerschaftsregister PR 563 -- command mailman info fails when Database url does not exist https://bugs.launchpad.net/bugs/543620 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Mon Mar 29 16:09:54 2010 From: barry at canonical.com (Barry Warsaw) Date: Mon, 29 Mar 2010 14:09:54 -0000 Subject: [Bug 543620] Re: command mailman info fails when Database url does not exist References: <20100321182256.2177.85290.malonedeb@soybean.canonical.com> Message-ID: <20100329140956.5798.25598.launchpad@soybean.canonical.com> ** Changed in: mailman/3.0 Status: Incomplete => Invalid -- command mailman info fails when Database url does not exist https://bugs.launchpad.net/bugs/543620 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.