From 266397 at bugs.launchpad.net Fri Dec 3 07:27:59 2010 From: 266397 at bugs.launchpad.net (uggtodoor) Date: Fri, 03 Dec 2010 06:27:59 -0000 Subject: [Bug 266397] Re: misc/KoreanCodecs-2.0.5/src/hangul.c does not compile References: <20080905193144.27052.45077.launchpad@forster.canonical.com> Message-ID: <20101203062759.2427.4380.malone@wampee.canonical.com> Ugg boots are good. They have many advantages. One of the most important features is that they are very comfortable and warm. Sheepskin ugg boots are made. Because of the sheepskin, ugg boots are so soft and comfortable. For this reason, they are very fashion. There are most flat ugg boots, and we also have other styles of high heels.Wellcome to: http://www.uggtodoor.com -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266397 Title: misc/KoreanCodecs-2.0.5/src/hangul.c does not compile From 244233 at bugs.launchpad.net Fri Dec 3 07:30:20 2010 From: 244233 at bugs.launchpad.net (uggtodoor) Date: Fri, 03 Dec 2010 06:30:20 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20101203063020.2507.73908.malone@wampee.canonical.com> Ugg boots are good. They have many advantages. One of the most important features is that they are very comfortable and warm. Sheepskin ugg boots are made. Because of the sheepskin, ugg boots are so soft and comfortable. For this reason, they are very fashion. There are most flat ugg boots, and we also have other styles of high heels.Wellcome to: http://www.uggtodoor.com -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/244233 Title: Logrotate is noisy with: Re-opening all log files From 398030 at bugs.launchpad.net Sat Dec 4 02:49:14 2010 From: 398030 at bugs.launchpad.net (uggtodoor) Date: Sat, 04 Dec 2010 01:49:14 -0000 Subject: [Bug 398030] Re: A CSS-controlled mailman interface References: <20090710225619.32615.16035.malonedeb@potassium.ubuntu.com> Message-ID: <20101204014914.2507.66403.malone@wampee.canonical.com> Ugg boots are good. They have many advantages. One of the most important features is that they are very comfortable and warm. Sheepskin ugg boots are made. Because of the sheepskin, ugg boots are so soft and comfortable. For this reason, they are very fashion. There are most flat ugg boots, and we also have other styles of high heels.Wellcome to: http://www.uggtodoor.com -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/398030 Title: A CSS-controlled mailman interface From 266806 at bugs.launchpad.net Sat Dec 4 02:48:59 2010 From: 266806 at bugs.launchpad.net (uggtodoor) Date: Sat, 04 Dec 2010 01:48:59 -0000 Subject: [Bug 266806] Re: unsubscribe removal confirmation should be optional References: <20080905194251.1806.9377.launchpad@forster.canonical.com> Message-ID: <20101204014900.2507.41813.malone@wampee.canonical.com> Ugg boots are good. They have many advantages. One of the most important features is that they are very comfortable and warm. Sheepskin ugg boots are made. Because of the sheepskin, ugg boots are so soft and comfortable. For this reason, they are very fashion. There are most flat ugg boots, and we also have other styles of high heels.Wellcome to: http://www.uggtodoor.com -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266806 Title: unsubscribe removal confirmation should be optional From mark at msapiro.net Sat Dec 4 20:04:41 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 04 Dec 2010 19:04:41 -0000 Subject: [Bug 685261] [NEW] emailed command in subject header is ignored References: <20101204190441.22665.47438.malonedeb@palladium.canonical.com> Message-ID: <20101204190441.22665.47438.malonedeb@palladium.canonical.com> Public bug reported: For example, a held message notification to the list owner/moderator contains an attached message/rfc822 part with subject "confirm " and this message can be replied to with or without an "Approved: " header/first body line to accept or discard the held message. The code allows for an MUA possibly inserting 'Re:' or some l10n equivalent in the subject making it "Re: confirm ", but if the l10n equivalent contains a non-ascii character, the entire command is ignored and the message continues to be held. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/685261 Title: emailed command in subject header is ignored From mark at msapiro.net Sat Dec 4 20:49:36 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 04 Dec 2010 19:49:36 -0000 Subject: [Bug 680447] Re: parts of recipients adresses between square brackets in are interpreted as seperate addresses References: <20101123111701.25625.86306.malonedeb@gandwana.canonical.com> Message-ID: <20101204194936.2574.43786.malone@wampee.canonical.com> There's not much Mailman can easily do about this. The issue is in the Python email library. email.utils.getaddresses() is used by Mailman to get a list of addresses and the length of that list is used as the number of recipients. getaddresses() treats the brackets as a kind of delimiter. Thus, email.utils.getaddresses(['jefke [jefke2 at foo.example.net]']) returns this list of (name, address) tuples [('', 'jefke'), ('', ''), ('', 'jefke2 at foo.example.net'), ('', '')] of length 4 instead of the list [('jefke', 'jefke2 at foo.example.net')] of length 1 that you expect. Escaping the brackets as you suggest changes the result only in that a '\' is appended to the jefke2 at foo.example.net address returned in the third tuple. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Won't Fix ** 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/680447 Title: parts of recipients adresses between square brackets in are interpreted as seperate addresses From mark at msapiro.net Sat Dec 4 22:26:26 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 04 Dec 2010 21:26:26 -0000 Subject: [Bug 685261] Re: emailed command in subject header is ignored References: <20101204190441.22665.47438.malonedeb@palladium.canonical.com> Message-ID: <20101204212629.15974.24015.launchpad@potassium.ubuntu.com> ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.15 ** 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/685261 Title: emailed command in subject header is ignored From mark at msapiro.net Sat Dec 4 22:25:45 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 04 Dec 2010 21:25:45 -0000 Subject: [Bug 677115] Re: Reply to to part 3 of a held message notification containing a Approved: first body line fails if reply is base64 encoded. References: <20101118175326.31311.55632.malonedeb@wampee.canonical.com> Message-ID: <20101204212546.15974.62633.launchpad@potassium.ubuntu.com> ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.15 ** 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/677115 Title: Reply to to part 3 of a held message notification containing a Approved: first body line fails if reply is base64 encoded. From mark at msapiro.net Sun Dec 5 00:28:12 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 04 Dec 2010 23:28:12 -0000 Subject: [Bug 685261] Re: emailed command in subject header is ignored References: <20101204190441.22665.47438.malonedeb@palladium.canonical.com> Message-ID: <20101204232812.22720.96757.malone@palladium.canonical.com> Note that the committed fix assumes that the l10n of the 'Re:' prefix is properly RFC 2047 encoded. If the raw Subject: header contains non- ascii, the command in the subject will still be ignored. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/685261 Title: emailed command in subject header is ignored From mark at msapiro.net Tue Dec 7 01:57:57 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 07 Dec 2010 00:57:57 -0000 Subject: [Bug 266554] Re: Integration of Mailman and htdig for archiving References: <20080905193728.32763.34621.launchpad@forster.canonical.com> Message-ID: <20101207005757.2427.74480.malone@wampee.canonical.com> More recent versions of this patch can be found at and . -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266554 Title: Integration of Mailman and htdig for archiving From mark at msapiro.net Tue Dec 7 01:58:29 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 07 Dec 2010 00:58:29 -0000 Subject: [Bug 266553] Re: Archive indexer control to improve index References: <20080905193726.32763.50718.launchpad@forster.canonical.com> Message-ID: <20101207005829.7172.45507.malone@wampee.canonical.com> More recent versions of this patch can be found at and . -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266553 Title: Archive indexer control to improve index From gimre at narancs.net Mon Dec 13 14:31:07 2010 From: gimre at narancs.net (Imre Gergely) Date: Mon, 13 Dec 2010 13:31:07 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20101213133107.2406.67233.malone@potassium.ubuntu.com> I've updated the bug description with some details for a SRU and I've tested the patch provided by pearcec and it's working as expected. ** Description changed: Binary package hint: mailman When logrotate runs for mailman you get this: /etc/cron.daily/logrotate: Re-opening all log files Re-opening all log files It calls mailmanctl reopen. If it called it with a -q it would be quiet. + + IMPACT: when rotating the mailman logfiles, 'mailmanctl reopen' is called from + /etc/logrotate.d/mailman, to get mailman to reopen the new logfiles. For every + call, mailman prints message "Re-opening all log files", which gets sent to + the user in a (useless) email. + + This was fixed upstream in mailman 2.1.9-10 and Karmic has 2.1.12-2. + + TEST CASE: + + - install mailman (apt-get install mailman) + - create the default mailman list with the following command: + newlist mailman + - start mailman (/etc/init.d/mailman start), there should be a couple of files + in /var/log/mailman + - force a logrotate of these files by running: + logrotate -f /etc/logrotate.d/mailman + - you should see the following output: + + root at utest-hhs32:/var/log/mailman# logrotate -f /etc/logrotate.d/mailman + Re-opening all log files + Re-opening all log files + + This is called from crontab so there will be an email sent to users + every time. + + - install the patched version, and run the above command again, it should be + quiet, without any messages. + + REGRESSION POTENTIAL: low. According to the mailmanctl help page: + + -q/--quiet + Don't print status messages. Error messages are still printed to + standard error. + + By applying this patch, users will not get the informational messages but they + will still get any error message. ** Description changed: Binary package hint: mailman When logrotate runs for mailman you get this: /etc/cron.daily/logrotate: Re-opening all log files Re-opening all log files It calls mailmanctl reopen. If it called it with a -q it would be quiet. IMPACT: when rotating the mailman logfiles, 'mailmanctl reopen' is called from /etc/logrotate.d/mailman, to get mailman to reopen the new logfiles. For every call, mailman prints message "Re-opening all log files", which gets sent to the user in a (useless) email. This was fixed upstream in mailman 2.1.9-10 and Karmic has 2.1.12-2. TEST CASE: - install mailman (apt-get install mailman) - create the default mailman list with the following command: - newlist mailman + ????newlist mailman - start mailman (/etc/init.d/mailman start), there should be a couple of files - in /var/log/mailman + ??in /var/log/mailman - force a logrotate of these files by running: - logrotate -f /etc/logrotate.d/mailman + ????logrotate -f /etc/logrotate.d/mailman - you should see the following output: root at utest-hhs32:/var/log/mailman# logrotate -f /etc/logrotate.d/mailman Re-opening all log files Re-opening all log files This is called from crontab so there will be an email sent to users every time. - install the patched version, and run the above command again, it should be quiet, without any messages. REGRESSION POTENTIAL: low. According to the mailmanctl help page: - -q/--quiet - Don't print status messages. Error messages are still printed to - standard error. + ????-q/--quiet + ??????Don't print status messages. Error messages are still printed to + ??????standard error. By applying this patch, users will not get the informational messages but they will still get any error message. ** Description changed: Binary package hint: mailman When logrotate runs for mailman you get this: /etc/cron.daily/logrotate: Re-opening all log files Re-opening all log files It calls mailmanctl reopen. If it called it with a -q it would be quiet. - IMPACT: when rotating the mailman logfiles, 'mailmanctl reopen' is called from - /etc/logrotate.d/mailman, to get mailman to reopen the new logfiles. For every - call, mailman prints message "Re-opening all log files", which gets sent to - the user in a (useless) email. + IMPACT: when rotating the mailman logfiles, 'mailmanctl reopen' is called + from /etc/logrotate.d/mailman, to get mailman to reopen the new logfiles. + For every call, mailman prints message "Re-opening all log files", which + gets sent to the user in a (useless) email. This was fixed upstream in mailman 2.1.9-10 and Karmic has 2.1.12-2. TEST CASE: - install mailman (apt-get install mailman) - create the default mailman list with the following command: ????newlist mailman - - start mailman (/etc/init.d/mailman start), there should be a couple of files - ??in /var/log/mailman + - start mailman (/etc/init.d/mailman start), there should be a couple of + files in /var/log/mailman - force a logrotate of these files by running: ????logrotate -f /etc/logrotate.d/mailman - you should see the following output: root at utest-hhs32:/var/log/mailman# logrotate -f /etc/logrotate.d/mailman Re-opening all log files Re-opening all log files - This is called from crontab so there will be an email sent to users - every time. + This is called from crontab so there will be an email sent to users every + time. - - install the patched version, and run the above command again, it should be - quiet, without any messages. + - install the patched version, and run the above command again, it should + be quiet, without any messages. REGRESSION POTENTIAL: low. According to the mailmanctl help page: ????-q/--quiet ??????Don't print status messages. Error messages are still printed to ??????standard error. - By applying this patch, users will not get the informational messages but they - will still get any error message. + By applying this patch, users will not get the informational messages but + they will still get any error message. ** Description changed: Binary package hint: mailman When logrotate runs for mailman you get this: /etc/cron.daily/logrotate: Re-opening all log files Re-opening all log files It calls mailmanctl reopen. If it called it with a -q it would be quiet. IMPACT: when rotating the mailman logfiles, 'mailmanctl reopen' is called from /etc/logrotate.d/mailman, to get mailman to reopen the new logfiles. For every call, mailman prints message "Re-opening all log files", which gets sent to the user in a (useless) email. This was fixed upstream in mailman 2.1.9-10 and Karmic has 2.1.12-2. TEST CASE: - install mailman (apt-get install mailman) - create the default mailman list with the following command: ????newlist mailman - start mailman (/etc/init.d/mailman start), there should be a couple of - files in /var/log/mailman + ??files in /var/log/mailman - force a logrotate of these files by running: ????logrotate -f /etc/logrotate.d/mailman - you should see the following output: root at utest-hhs32:/var/log/mailman# logrotate -f /etc/logrotate.d/mailman Re-opening all log files Re-opening all log files This is called from crontab so there will be an email sent to users every time. - install the patched version, and run the above command again, it should be quiet, without any messages. REGRESSION POTENTIAL: low. According to the mailmanctl help page: ????-q/--quiet ??????Don't print status messages. Error messages are still printed to ??????standard error. - By applying this patch, users will not get the informational messages but - they will still get any error message. + By applying this patch, users will not get the informational messages + but they will still get any error message. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/244233 Title: Logrotate is noisy with: Re-opening all log files From gimre at narancs.net Mon Dec 13 14:38:19 2010 From: gimre at narancs.net (Imre Gergely) Date: Mon, 13 Dec 2010 13:38:19 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20101213133819.22946.23830.malone@soybean.canonical.com> Attached debdiff. ** Patch added: "mailman-hardy.diff" https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/244233/+attachment/1764691/+files/mailman-hardy.diff -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/244233 Title: Logrotate is noisy with: Re-opening all log files From mihai at mihaic.ro Tue Dec 14 18:40:38 2010 From: mihai at mihaic.ro (=?utf-8?q?Mihai_Capot=C4=83?=) Date: Tue, 14 Dec 2010 17:40:38 -0000 Subject: [Bug 558014] Re: Generate RSS summary in archives References: <20100408090423.1687.21024.launchpad@loganberry.canonical.com> Message-ID: <20101214174039.24149.41104.launchpad@wampee.canonical.com> *** This bug is a duplicate of bug 317453 *** https://bugs.launchpad.net/bugs/317453 ** This bug has been marked a duplicate of bug 317453 Atom (/RSS?) feeds of Mailing lists * You can subscribe to bug 317453 by following this link: https://bugs.launchpad.net/launchpad-registry/+bug/317453/+subscribe -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558014 Title: Generate RSS summary in archives From mihai at mihaic.ro Tue Dec 14 18:41:04 2010 From: mihai at mihaic.ro (=?utf-8?q?Mihai_Capot=C4=83?=) Date: Tue, 14 Dec 2010 17:41:04 -0000 Subject: [Bug 266649] Re: Automatic RSS feed generation References: <20080905194203.1806.73464.launchpad@forster.canonical.com> Message-ID: <20101214174105.5618.38545.launchpad@soybean.canonical.com> *** This bug is a duplicate of bug 317453 *** https://bugs.launchpad.net/bugs/317453 ** This bug has been marked a duplicate of bug 317453 Atom (/RSS?) feeds of Mailing lists * You can subscribe to bug 317453 by following this link: https://bugs.launchpad.net/launchpad-registry/+bug/317453/+subscribe -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266649 Title: Automatic RSS feed generation From smoser at canonical.com Tue Dec 14 18:55:04 2010 From: smoser at canonical.com (Scott Moser) Date: Tue, 14 Dec 2010 17:55:04 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20101214175504.24239.62998.malone@wampee.canonical.com> Imre, Thanks for the debdiff. I'm not able to sponsor this, but looked at the patch, and it is an exact backport of the commit to debian/mailman.logrotate at at [1]. I can +1 the patch. -- [1] http://bazaar.launchpad.net/%7Eubuntu-branches/ubuntu/natty/mailman/natty/revision/17/debian/mailman.logrotate#debian/mailman.logrotate -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/244233 Title: Logrotate is noisy with: Re-opening all log files From martin.pitt at ubuntu.com Wed Dec 15 12:52:24 2010 From: martin.pitt at ubuntu.com (Martin Pitt) Date: Wed, 15 Dec 2010 11:52:24 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20101215115224.5618.71670.malone@soybean.canonical.com> Accepted mailman into hardy-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: mailman (Ubuntu Hardy) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/244233 Title: Logrotate is noisy with: Re-opening all log files From 244233 at bugs.launchpad.net Wed Dec 15 13:15:49 2010 From: 244233 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Wed, 15 Dec 2010 12:15:49 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20101215121551.6406.37938.launchpad@loganberry.canonical.com> ** Branch linked: lp:ubuntu/hardy-proposed/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/244233 Title: Logrotate is noisy with: Re-opening all log files From 690656 at bugs.launchpad.net Wed Dec 15 15:23:44 2010 From: 690656 at bugs.launchpad.net (Vladimir Rutsky) Date: Wed, 15 Dec 2010 14:23:44 -0000 Subject: =?utf-8?q?=5BBug_690656=5D_=5BNEW=5D_Typo_in_russian_translation_?= =?utf-8?b?KCLQtNCw0L3QvdC+0LzRg9C80YMiKQ==?= References: <20101215142344.20749.85666.malonedeb@potassium.ubuntu.com> Message-ID: <20101215142344.20749.85666.malonedeb@potassium.ubuntu.com> Public bug reported: There is a typo in Russian translation. Please see attached patch for details. ** Affects: mailman Importance: Undecided Status: New ** Tags: typo -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/690656 Title: Typo in russian translation ("?????????") From 690656 at bugs.launchpad.net Wed Dec 15 15:23:44 2010 From: 690656 at bugs.launchpad.net (Vladimir Rutsky) Date: Wed, 15 Dec 2010 14:23:44 -0000 Subject: =?utf-8?q?=5BBug_690656=5D_Re=3A_Typo_in_russian_translation_=28?= =?utf-8?b?ItC00LDQvdC90L7QvNGD0LzRgyIp?= References: <20101215142344.20749.85666.malonedeb@potassium.ubuntu.com> Message-ID: <20101215142345.20749.62523.malone@potassium.ubuntu.com> ** Patch added: "Fix for typo" https://bugs.launchpad.net/bugs/690656/+attachment/1766731/+files/mailman-ru-typo.patch -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/690656 Title: Typo in russian translation ("?????????") From gimre at narancs.net Wed Dec 15 15:37:24 2010 From: gimre at narancs.net (Imre Gergely) Date: Wed, 15 Dec 2010 14:37:24 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20101215143724.24149.95438.malone@wampee.canonical.com> Did the test case and everythings seems ok. root at utest-hhs32:~# apt-cache policy mailman mailman: Installed: 1:2.1.9-9ubuntu1.2 Candidate: 1:2.1.9-9ubuntu1.2 Version table: *** 1:2.1.9-9ubuntu1.2 0 500 http://archive.ubuntu.com hardy-proposed/main Packages 100 /var/lib/dpkg/status 1:2.1.9-9ubuntu1.1 0 500 http://ro.archive.ubuntu.com hardy-updates/main Packages 1:2.1.9-9ubuntu1 0 500 http://ro.archive.ubuntu.com hardy/main Packages root at utest-hhs32:~# ls -la /var/log/mailman/ total 12 drwxrws--- 2 root list 4096 2010-12-15 16:36 . drwxr-xr-x 11 root root 4096 2010-12-15 16:33 .. -rw-rw-r-- 1 list list 0 2010-12-15 16:34 error -rw-rw-r-- 1 list list 729 2010-12-15 16:34 qrunner root at utest-hhs32:~# logrotate -f /etc/logrotate.d/mailman <--- (notice how there is no message displayed) root at utest-hhs32:~# ls -la /var/log/mailman/ total 16 drwxrws--- 2 root list 4096 2010-12-15 16:36 . drwxr-xr-x 11 root root 4096 2010-12-15 16:33 .. -rw-rw-r-- 1 list list 0 2010-12-15 16:36 error -rw-rw-r-- 1 list list 0 2010-12-15 16:34 error.1 -rw-rw-r-- 1 list list 729 2010-12-15 16:36 qrunner -rw-rw-r-- 1 list list 1458 2010-12-15 16:36 qrunner.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/244233 Title: Logrotate is noisy with: Re-opening all log files From 674619 at bugs.launchpad.net Wed Dec 15 19:23:39 2010 From: 674619 at bugs.launchpad.net (dreamhosttest) Date: Wed, 15 Dec 2010 18:23:39 -0000 Subject: [Bug 674619] Re: " Not metoo " feature appears to be broken References: <20101112180433.1220.98104.malonedeb@wampee.canonical.com> Message-ID: <20101215182340.24239.71985.malone@wampee.canonical.com> I am the primary mailman admin at DreamHost and am unable to replicate this issue. The user has since removed their list so I can not troubleshoot this further, however I suspect they were using Gmail (which has resulted in this same problem in the past). Thank you for your time and we will update this bug in the future if it turns out to be valid after all. ** Changed in: mailman Status: Incomplete => Invalid -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/674619 Title: " Not metoo " feature appears to be broken From martin.pitt at ubuntu.com Wed Dec 15 20:14:51 2010 From: martin.pitt at ubuntu.com (Martin Pitt) Date: Wed, 15 Dec 2010 19:14:51 -0000 Subject: [Bug 244233] Re: Logrotate is noisy with: Re-opening all log files References: <20080630134437.14161.96026.malonedeb@gandwana.canonical.com> Message-ID: <20101215191451.5740.61588.launchpad@soybean.canonical.com> ** Tags added: verification-done ** Tags removed: verification-needed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/244233 Title: Logrotate is noisy with: Re-opening all log files From danny.piccirillo at ubuntu.com Thu Dec 16 08:25:03 2010 From: danny.piccirillo at ubuntu.com (Danny Piccirillo) Date: Thu, 16 Dec 2010 07:25:03 -0000 Subject: [Bug 302813] Re: [feature-request] hierarchical list organisation References: <20081127135614.19319.61599.malonedeb@palladium.canonical.com> Message-ID: <20101216072503.28241.67019.malone@gandwana.canonical.com> 1. This isn't a bad idea, but it won't get anywhere until it is pushed upstream. =] 2. I got here looking for something like this. I have a similar idea, but a bit simpler and non hierarchical. It would just be a way to have sublists that only go to subset of the whole list (and possibly people not on the "main" list?). Any mechanism for that would be cool. It's pretty open-ended, but here's more of what i had in mind and how it's different: I imagine that the sublists could be similar to gmail allowing the use of +something on the end of your email address for different things***. I see them as leaves on a tree, rather than branches, so non- hierarchical. The use case i had in mind was: i have a group of people (friends, coworkers, whoever), and some of them are planning something (a trip, an event, whatever), and they would like to plan this on the list, without it necessarily going out to everyone. They may have a short lifespan, but are useful. Since these discussions would be part of the main list, and presumably archived on it somehow, it probably makes sense to allow anyone on the main list to opt-in to the discussion, but perhaps let the creator of the sub-list to choose who to invite/include initially. So, perhaps this should be filed separately? *** Gmail allows you to add +anything to the end of your gmail address, and receive messages that way. for example, if you have youremailaddress at gmail.com, and someone emails youremailaddress+whatever at gmail.com, it will go through as normal. This is useful for blocking spam (adding a suffix to the local part of your email address, thus allowing you to block all incoming mail addressed to that suffix). -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/302813 Title: [feature-request] hierarchical list organisation From 693134 at bugs.launchpad.net Tue Dec 21 19:53:25 2010 From: 693134 at bugs.launchpad.net (JorSol) Date: Tue, 21 Dec 2010 18:53:25 -0000 Subject: [Bug 693134] [NEW] Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Public bug reported: I have a Debian 5 (Lenny) server with Postfix - Dovecot and Mailman 2.1.11 and 1700+ users. The problem is when Dovecot returns the bounce message about "Quota exceeded", Mailman don't recognize the format: Your message to was automatically rejected: Quota exceeded It's suposed that Mailman recognize this type of message using the VERP feature, I have "recipient_delimiter = +" in Postfix but Mailman don't detect message coming from Dovecot. /var/log/mailman/bounce: Dec 21 10:58:08 2010 (3214) listnews: bounce message w/no discernable addresses: Dec 21 10:58:08 2010 (3214) noticias: forwarding unrecognized, message-id: ** Affects: mailman Importance: Undecided Status: New ** Tags: dovecot mailman postfix -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded From 693134 at bugs.launchpad.net Tue Dec 21 20:04:54 2010 From: 693134 at bugs.launchpad.net (JorSol) Date: Tue, 21 Dec 2010 19:04:54 -0000 Subject: [Bug 693134] Re: Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20101221190454.3045.69482.launchpad@potassium.ubuntu.com> ** Description changed: I have a Debian 5 (Lenny) server with Postfix - Dovecot and Mailman 2.1.11 and 1700+ users. The problem is when Dovecot returns the bounce message about "Quota exceeded", Mailman don't recognize the format: Your message to was automatically rejected: Quota exceeded It's suposed that Mailman recognize this type of message using the VERP feature, I have "recipient_delimiter = +" in Postfix but Mailman don't detect message coming from Dovecot. /var/log/mailman/bounce: Dec 21 10:58:08 2010 (3214) listnews: bounce message w/no discernable addresses: - Dec 21 10:58:08 2010 (3214) noticias: forwarding unrecognized, message-id: + Dec 21 10:58:08 2010 (3214) listnews: forwarding unrecognized, message-id: -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded From mark at msapiro.net Tue Dec 21 20:47:50 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 21 Dec 2010 19:47:50 -0000 Subject: [Bug 693134] Re: Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20101221194751.31492.33150.malone@palladium.canonical.com> VERP must be enabled in Mailman. Putting VERP_DELIVERY_INTERVAL = 1 in mm_cfg.py will enable Mailman's VERP for all messages. If you attach a copy of the raw bounce message from Dovecot to this report, I will try to update the heuristic recognizers to recognize it. You can obfuscate any personal information such as email addresses or domain names. Note that if Dovecot sends an RFC 1894/RFC 3464 compliant DSN, it should be recognized. ** Changed in: mailman Importance: Undecided => Low ** 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/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded From 693134 at bugs.launchpad.net Tue Dec 21 21:28:51 2010 From: 693134 at bugs.launchpad.net (JorSol) Date: Tue, 21 Dec 2010 20:28:51 -0000 Subject: [Bug 693134] Re: Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20101221202851.18078.29516.malone@gandwana.canonical.com> Attach raw message.... I added "VERP_DELIVERY_INTERVAL = 1" to mm_cfg.py.... when I try it I will post the results. Thanks for you quick response. ** Attachment added: "Automatically rejected mail.msg" https://bugs.launchpad.net/mailman/+bug/693134/+attachment/1773018/+files/Automatically%20rejected%20mail.msg -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded From mark at msapiro.net Wed Dec 22 00:52:14 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 21 Dec 2010 23:52:14 -0000 Subject: [Bug 693134] Re: Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20101221235214.29758.19159.malone@wampee.canonical.com> The underlying issue is that the bounce from the Dovecot LDA is not an RFC 3464 Delivery Status Notification, but rather is an RFC 3798 Message Disposition Notification and Mailman doesn't currently recognize these. I have worked around this for the moment by adding the "Your message to was automatically rejected:" line to the simple text matcher, but the proper fix is to add recognition for RFC 3798 Message Disposition Notifications to Mailman. ** Changed in: mailman Status: Incomplete => In Progress ** Changed in: mailman Milestone: None => 2.1.15 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded From mark at msapiro.net Wed Dec 22 07:23:24 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 22 Dec 2010 06:23:24 -0000 Subject: [Bug 693134] Re: Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20101222062324.29758.80987.malone@wampee.canonical.com> I have thought about this some more and looked more carefully at RFC 3798, and I don't think RFC 3798 MDNs should be considered bounces. The first paragraph of the Abstract of RFC 3798 says: This memo defines a MIME content-type that may be used by a mail user agent (MUA) or electronic mail gateway to report the disposition of a message after it has been successfully delivered to a recipient. This content-type is intended to be machine-processable. Additional message headers are also defined to permit Message Disposition Notifications (MDNs) to be requested by the sender of a message. The purpose is to extend Internet Mail to support functionality often found in other messaging systems, such as X.400 and the proprietary "LAN-based" systems, and often referred to as "read receipts," "acknowledgements", or "receipt notifications." The intention is to do this while respecting privacy concerns, which have often been expressed when such functions have been discussed in the past. The key point is that the purpose of an MDN is for an MUA to report the disposition of a message after it has been successfully delivered to a recipient. Thus, it's use by the Dovecot LDA to report non-delivery due to over quota or other reasons seems incorrect, and Dovecot should be sending a DSN with a 'failed' action for the recipient rather than an MDN with a 'deleted' disposition which is intended to report that the message was deleted by the recipient after successful delivery and which should not in general be interpreted as a bounce. Thus, I think Dovecot's behavior is incorrect, and the best we can do in Mailman is to recognize the "Your message to was automatically rejected:" line in the simple text matcher as a work around. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded From 693134 at bugs.launchpad.net Wed Dec 22 20:48:23 2010 From: 693134 at bugs.launchpad.net (JorSol) Date: Wed, 22 Dec 2010 19:48:23 -0000 Subject: [Bug 693134] Re: Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20101222194823.908.71130.malone@soybean.canonical.com> Then is a Dovecot bug, the problem is that the version in Debian Lenny is 1.0.15 and the lastest stable is 2.0.8 (1.2.16 in the 1.x brach) so is hard to know if it's already fixed in the lastest versions. I tested the "VERP_DELIVERY_INTERVAL = 1".... It works, but I don't like the results since it sends one message per recipient and the Postfix queque gets saturated and the whole system is slow down and I'm not able to throttle or assign a lower priority to Mailman. I'm going to check out the simple text matcher as work around. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded From mark at msapiro.net Thu Dec 23 00:39:13 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 22 Dec 2010 23:39:13 -0000 Subject: [Bug 693134] Re: Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20101222233913.19375.70639.malone@wampee.canonical.com> Note that it is possible to do the VERPing in Postfix rather than in Mailman. See the patch at . -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded From mark at msapiro.net Thu Dec 23 00:38:35 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 22 Dec 2010 23:38:35 -0000 Subject: [Bug 558067] Re: Postfix XVERP support for SMTPDirect.py References: <20100408090522.1687.65054.launchpad@loganberry.canonical.com> Message-ID: <20101222233835.974.81649.malone@soybean.canonical.com> An updated version of the patch for Mailman 2.1.14 which includes a minor refactoring due the the change in SMTPDirect for the include_sender_header option is attached. ** Attachment added: "Postfix VERP patch for Mailman 2.1.14" https://bugs.launchpad.net/mailman/+bug/558067/+attachment/1774159/+files/VERP.patch.txt -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558067 Title: Postfix XVERP support for SMTPDirect.py From mark at msapiro.net Thu Dec 23 00:04:25 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 22 Dec 2010 23:04:25 -0000 Subject: [Bug 693134] Re: Uncaught bounce from Dovecot when Quota Exceeded References: <20101221185325.20409.19945.malonedeb@soybean.canonical.com> Message-ID: <20101222230425.908.18772.malone@soybean.canonical.com> The patch to Mailman/Bouncers/SimpleMatch.py is at . I reported this issue to the Dovecot mailing list at , but no response so far. ** 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/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded From noreply at launchpad.net Sun Dec 26 16:29:26 2010 From: noreply at launchpad.net (noreply at launchpad.net) Date: Sun, 26 Dec 2010 15:29:26 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 9: Only start the REST qrunner. Message-ID: <20101226152926.20989.56775.launchpad@loganberry.canonical.com> ------------------------------------------------------------ revno: 9 committer: Barry Warsaw branch nick: trunk timestamp: Sun 2010-12-26 10:24:41 -0500 message: Only start the REST qrunner. modified: mailman/client/tests/test_docs.py -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 1162 bytes Desc: not available URL: From noreply at launchpad.net Sun Dec 26 20:09:27 2010 From: noreply at launchpad.net (noreply at launchpad.net) Date: Sun, 26 Dec 2010 19:09:27 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 10: Members and subscriptions. Message-ID: <20101226190927.744.20407.launchpad@loganberry.canonical.com> ------------------------------------------------------------ revno: 10 committer: Barry Warsaw branch nick: trunk timestamp: Sun 2010-12-26 14:07:13 -0500 message: Members and subscriptions. modified: mailman/client/_client.py mailman/client/docs/using.txt -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 4504 bytes Desc: not available URL: From noreply at launchpad.net Sun Dec 26 22:14:26 2010 From: noreply at launchpad.net (noreply at launchpad.net) Date: Sun, 26 Dec 2010 21:14:26 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 12: .get_member() for a mailing list Message-ID: <20101226211426.16340.86295.launchpad@loganberry.canonical.com> ------------------------------------------------------------ revno: 12 committer: Barry Warsaw branch nick: trunk timestamp: Sun 2010-12-26 16:11:54 -0500 message: .get_member() for a mailing list .unsubscribe() on a mailing list .unsubscribe() on a member. modified: mailman/client/_client.py mailman/client/docs/using.txt -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 3164 bytes Desc: not available URL: From noreply at launchpad.net Sun Dec 26 22:14:26 2010 From: noreply at launchpad.net (noreply at launchpad.net) Date: Sun, 26 Dec 2010 21:14:26 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 11: Mailing list members. Message-ID: <20101226211426.16340.79124.launchpad@loganberry.canonical.com> ------------------------------------------------------------ revno: 11 committer: Barry Warsaw branch nick: trunk timestamp: Sun 2010-12-26 16:00:02 -0500 message: Mailing list members. modified: mailman/client/_client.py mailman/client/docs/using.txt -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 1385 bytes Desc: not available URL: From barry at canonical.com Sun Dec 26 22:21:11 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 26 Dec 2010 21:21:11 -0000 Subject: [Merge] lp:~flo-fuchs/mailman/restclient into lp:mailman In-Reply-To: <20100625165042.6066.5358.launchpad@loganberry.canonical.com> Message-ID: <20101226211946.13191.5788.codereview@gandwana.canonical.com> Review: Approve I finally managed to figure out how to deploy this. See http://launchpad.net/mailman.client and the trunk branch of that. Thanks so much for the contribution! -- https://code.launchpad.net/~flo-fuchs/mailman/restclient/+merge/28522 Your team Mailman Coders is requested to review the proposed merge of lp:~flo-fuchs/mailman/restclient into lp:mailman. From barry at canonical.com Sun Dec 26 22:23:52 2010 From: barry at canonical.com (Barry Warsaw) Date: Sun, 26 Dec 2010 21:23:52 -0000 Subject: [Merge] lp:~flo-fuchs/mailman/restclient into lp:mailman In-Reply-To: <20100625165042.6066.5358.launchpad@loganberry.canonical.com> Message-ID: <20101226212352.22689.45222.launchpad@loganberry.canonical.com> The proposal to merge lp:~flo-fuchs/mailman/restclient into lp:mailman has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~flo-fuchs/mailman/restclient/+merge/28522 -- https://code.launchpad.net/~flo-fuchs/mailman/restclient/+merge/28522 Your team Mailman Coders is requested to review the proposed merge of lp:~flo-fuchs/mailman/restclient into lp:mailman. From noreply at launchpad.net Sun Dec 26 22:24:28 2010 From: noreply at launchpad.net (noreply at launchpad.net) Date: Sun, 26 Dec 2010 21:24:28 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 13: Add Acknowledgements. Message-ID: <20101226212428.22730.18011.launchpad@loganberry.canonical.com> ------------------------------------------------------------ revno: 13 committer: Barry Warsaw branch nick: trunk timestamp: Sun 2010-12-26 16:22:12 -0500 message: Add Acknowledgements. modified: README.txt -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 374 bytes Desc: not available URL: From noreply at launchpad.net Wed Dec 29 16:54:40 2010 From: noreply at launchpad.net (noreply at launchpad.net) Date: Wed, 29 Dec 2010 15:54:40 -0000 Subject: [Merge] lp:~jimmy-sigint/mailman/restapi_additional_attributes into lp:mailman In-Reply-To: <20101014073144.8590.88742.launchpad@loganberry.canonical.com> Message-ID: <20101229155440.5416.23066.launchpad@loganberry.canonical.com> The proposal to merge lp:~jimmy-sigint/mailman/restapi_additional_attributes into lp:mailman has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~jimmy-sigint/mailman/restapi_additional_attributes/+merge/38390 -- https://code.launchpad.net/~jimmy-sigint/mailman/restapi_additional_attributes/+merge/38390 Your team Mailman Coders is requested to review the proposed merge of lp:~jimmy-sigint/mailman/restapi_additional_attributes into lp:mailman.