Mailman 3 October 2010 - Mailman-coders

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net 19 Aug '22

19 Aug '22

Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…

2 1

[Bug 544477] [NEW] setting localhost in postfix_lmtp breaks delivery
by Patrick Ben Koetter 27 Sep '20

27 Sep '20

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(a)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.

4 7

[Bug 576675] [NEW] Content filtering fails to collapse alternatives.
by Mark Sapiro 09 Jun '17

09 Jun '17

Public bug reported: Collapsing multipart/alternative parts to just the first alternative only works if the message itself is multipart/alternative, or the multipart/alternative part is at the first sub-level. For example, given this structure: multipart/mixed | multipart/related | | multipart/alternative | | | text/plain | | | text/html | | image/jpeg | application/msword The multipart/alternative part will not be collapsed. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: None => 2.1.14 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- Content filtering fails to collapse alternatives. https://bugs.launchpad.net/bugs/576675 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 7

[Bug 514625] [NEW] Mailman 3 member functions should "guess" address membership
by Stephen Turnbull 23 May '15

23 May '15

Public bug reported: Feature request Mailman 3 should try to fuzzily match unknown author addresses against the member database. For example, if "turnbull(a)sk.domain.tld" is subscribed, then "turnbull(a)shako.sk.domain.tld" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull@shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for <member name and address>. [ ] Add <unknown address> as an alias for <member>." ** Affects: mailman Importance: Undecided Status: New ** Description changed: Feature request Mailman 3 should try to fuzzily match unknown author addresses against the member database. For example, if "turnbull(a)sk.tsukuba.ac.jp" is subscribed, then "turnbull(a)shako.sk.tsukuba.ac.jp" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull@shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for <member name and - address>. [ ] Add <unknown> address as an alias for <member>." + address>. [ ] Add <unknown address> as an alias for <member>." ** Description changed: Feature request Mailman 3 should try to fuzzily match unknown author addresses against - the member database. For example, if "turnbull(a)sk.tsukuba.ac.jp" is - subscribed, then "turnbull(a)shako.sk.tsukuba.ac.jp" probably is the same + the member database. For example, if "turnbull(a)sk.domain.tld" is + subscribed, then "turnbull(a)shako.sk.domain.tld" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull@shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for <member name and address>. [ ] Add <unknown address> as an alias for <member>." -- 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.

4 5

[Bug 543618] [NEW] test breaks if existing mailman.cfg is found
by Patrick Ben Koetter 24 Mar '15

24 Mar '15

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.

4 6

[Bug 518517] [NEW] Add the equivalent of postconf(1)
by Barry Warsaw 22 Apr '14

22 Apr '14

Public bug reported: Postfix has a very handy command called postconf(1) which lets you dump all or one Postfix configuration variable. It would be very handy for Mailman 3 to have something similar. ** Affects: mailman Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged ** Affects: mailman/3.0 Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged ** Also affects: mailman/3.0 Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged -- 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.

5 19

[Bug 500955] [NEW] Templates for AST use inconsistent DOCTYPE
by Matt Selsky 15 Jun '12

15 Jun '12

Public bug reported: Most of the templates use a DOCTYPE of HTML 4.01 Transitional, but the AST templates use HTML 3.2. The patch updates the DOCTYPES for the AST templates. ** Affects: mailman Importance: Undecided Status: New -- Templates for AST use inconsistent DOCTYPE https://bugs.launchpad.net/bugs/500955 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 500952] [NEW] Extra escape characters in DOCTYPE
by Matt Selsky 15 Jun '12

15 Jun '12

Public bug reported: The DOCTYPE header for 2 files in the sk templates contain extra escape characters around the quote marks. ** Affects: mailman Importance: Undecided Status: New -- Extra escape characters in DOCTYPE https://bugs.launchpad.net/bugs/500952 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 637652] [NEW] mailman should respect LDFLAGS
by Hanno Böck 15 Jun '12

15 Jun '12

Public bug reported: mailman Makefile should respect the LDFLAGS variable. See attached patch. ** Affects: mailman Importance: Undecided Status: New -- mailman should respect LDFLAGS https://bugs.launchpad.net/bugs/637652 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 6

[Bug 666181] [NEW] wrong From field in subscription notification to admin
by Ilya Belyy 15 Jun '12

15 Jun '12

Public bug reported: Steps to reproduce: Create two mail lists ml01 (hosted on domain dom.1) and ml02 (hosted on domain dom.2) Add user to ml01 $ add_members -a y -r - ml01 lkjhlkhlkh(a)wefqwefqwef.com Subscribed: lkjhlkhlkh(a)wefqwefqwef.com Notification email to the admin of ml01 will look as following: Subject: Ml01 subscription notification From: mailman(a)dom.2 To: mladmin00(a)dom.1 Message-ID: <mailman.1.1287993063.7501.ml01(a)dom.1> Date: Mon, 25 Oct 2010 14:51:03 +0700 Subscribed: lkjhlkhlkh(a)wefqwefqwef.com Apparently, host name of the mail list is not considered when composing the notification message. I've checked 2.1.9 and 2.1.14 - both have the same bug ** Affects: mailman Importance: Undecided Status: New -- wrong From field in subscription notification to admin https://bugs.launchpad.net/bugs/666181 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 600780] [NEW] Login function needed in rest-client
by Anna 06 Apr '12

06 Apr '12

Public bug reported: For a good, working Mailman 3.0 UI we have to handle the passwords for each user (needed when they subscribe/unsubscribe/want to access their settings page but also for the admins and listowners). Hence, we need to implement the possibility to check for passwords in the rest-client (I believe these are saved in the user table in the core DB) and/or a login function. We should probably use https for the psw authentication. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 rest-api -- Login function needed in rest-client https://bugs.launchpad.net/bugs/600780 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 4

[Bug 667252] [NEW] Mailman 3 Branch, install fails with --prefix specified
by Simon Fraser 13 Jun '11

13 Jun '11

Public bug reported: When trying to install mailman outside the Python tree, I get the following error: (I've replaced my home directory with $HOME in the below text) $ whoami srf $ /software/bin/python-2.6.3 setup.py install --prefix=~srf/mailman-install running install Checking .pth file support in /$HOME/mailman-install/lib/python2.6/site-packages/ error: can't create or remove files in install directory The following error occurred while trying to add or remove files in the installation directory: [Errno 2] No such file or directory: '/$HOME/mailman- install/lib/python2.6/site-packages/test-easy-install-20075.pth' The installation directory you specified (via --install-dir, --prefix, or the distutils default setting) was: /$HOME/mailman-install/lib/python2.6/site-packages/ This directory does not currently exist. Please create it and try again, or choose a different installation directory (using the -d or --install-dir option). ** Affects: mailman Importance: Undecided Status: New -- Mailman 3 Branch, install fails with --prefix specified https://bugs.launchpad.net/bugs/667252 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 5

[Bug 667472] [NEW] Support Python 2.7
by Barry Warsaw 29 Apr '11

29 Apr '11

Public bug reported: Mailman 3 should support either Python 2.6 or Python 2.7. ** Affects: mailman Importance: Medium Assignee: Barry Warsaw (barry) Status: Fix Committed ** Tags: mailman3 ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a7 ** Tags added: mailman3 ** Changed in: mailman Status: In Progress => Fix Committed -- Support Python 2.7 https://bugs.launchpad.net/bugs/667472 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 2

[Bug 659951] [NEW] REST server should support a few more writable attributes to simplify integration
by Jimmy Bergman 29 Apr '11

29 Apr '11

Public bug reported: To make more options available to applications like web UI:s that want to integrate against mailman 3.0 i propose that the following writable attributes is made available through the REST server: reply_goes_to_list send_welcome_msg welcome_msg member_moderation_action default_member_moderation generic_nonmember_action ** Affects: mailman Importance: Undecided Assignee: Jimmy Bergman (jimmy-sigint) Status: New ** Changed in: mailman Assignee: (unassigned) => Jimmy Bergman (jimmy-sigint) -- REST server should support a few more writable attributes to simplify integration https://bugs.launchpad.net/bugs/659951 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 4

[Bug 643949] [NEW] Need REST API to change existing user's email
by Timr-probo 29 Apr '11

29 Apr '11

Public bug reported: Perhaps the most common administrative task I face is changing an existing user's email address. Many non-technical people change email addresses very often. This is easy to do with the command line clone_users command, but in a hosted environment, I have to find the user, delete them, go to "mass subscription", and re-enter them. It would be nice if the REST API included a "change one user's address" command. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- Need REST API to change existing user's email https://bugs.launchpad.net/bugs/643949 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 5

[Bug 645897] [NEW] mailman scan_message exception
by FreqMod 29 Apr '11

29 Apr '11

Public bug reported: scan_message in mailman/app/bounces.py causes exception becuase: for detector_class in find_components('mailman.bouncers', IBounceDetector): addresses = detector().process(msg) is not: for detector_class in find_components('mailman.bouncers', IBounceDetector): addresses = detector_class().process(msg) I'am working around it by reimplementing the function in my code, but I would be happy if I don't need to, because it touches more internal interfaces than neccesarry. ** Affects: mailman Importance: Undecided Status: New -- mailman scan_message exception https://bugs.launchpad.net/bugs/645897 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 656946] [NEW] Corrupt eggs in mailman-3.0.0a6.tar.gz
by Phil King 29 Apr '11

29 Apr '11

Public bug reported: Following up on this thread: http://www.mail-archive.com/mailman-developers%40python.org/msg12023.html I can reproduce the problem: [cp ~/local/src/mailman-3.0.0a6] ./bin/buildout Traceback (most recent call last): File "./bin/buildout", line 17, in <module> import zc.buildout.buildout ImportError: No module named zc.buildout.buildout The eggs/zc-buildout* directory is missing the *.py files. Similarly, the z3c.recipe.sphinxdox and zc.recipe.egg. In the end, I removed the eggs/ directory completely, and got much further down the road. (I am new to eggs, so I am not sure this is the best idea.) Now, installation seems to fail at the logilab-common step. Develop: '/home/phil/local/src/mailman-3.0.0a6/.' Page at http://pypi.python.org/simple/argparse/ links to .py file(s) without version info; an index scan is required. Uninstalling filetemplates. Updating docs. Generated script '/home/phil/local/src/mailman-3.0.0a6/bin/docs'. Installing filetemplates. Updating interpreter. Installing pylint. Getting distribution for 'logilab-common>=0.50.1'. Traceback (most recent call last): File "<string>", line 1, in <module> File "/home/phil/local/src/mailman-3.0.0a6/eggs/setuptools-0.6c12dev_r85190-py2.6.egg/setuptools/command/easy_install.py", line 1712, in main with_ei_usage(lambda: File "/home/phil/local/src/mailman-3.0.0a6/eggs/setuptools-0.6c12dev_r85190-py2.6.egg/setuptools/command/easy_install.py", line 1700, in with_ei_usage return f() File "/home/phil/local/src/mailman-3.0.0a6/eggs/setuptools-0.6c12dev_r85190-py2.6.egg/setuptools/command/easy_install.py", line 1716, in <lambda> distclass=DistributionWithoutHelpCommands, **kw File "/usr/lib/python2.6/distutils/core.py", line 152, in setup dist.run_commands() File "/usr/lib/python2.6/distutils/dist.py", line 975, in run_commands self.run_command(cmd) File "/usr/lib/python2.6/distutils/dist.py", line 995, in run_command cmd_obj.run() File "/home/phil/local/src/mailman-3.0.0a6/eggs/setuptools-0.6c12dev_r85190-py2.6.egg/setuptools/command/easy_install.py", line 211, in run self.easy_install(spec, not self.no_deps) File "/home/phil/local/src/mailman-3.0.0a6/eggs/setuptools-0.6c12dev_r85190-py2.6.egg/setuptools/command/easy_install.py", line 427, in easy_install return self.install_item(None, spec, tmpdir, deps, True) File "/home/phil/local/src/mailman-3.0.0a6/eggs/setuptools-0.6c12dev_r85190-py2.6.egg/setuptools/command/easy_install.py", line 476, in install_item dists = self.install_eggs(spec, download, tmpdir) File "/home/phil/local/src/mailman-3.0.0a6/eggs/setuptools-0.6c12dev_r85190-py2.6.egg/setuptools/command/easy_install.py", line 626, in install_eggs unpack_archive(dist_filename, tmpdir, self.unpack_progress) File "/home/phil/local/src/mailman-3.0.0a6/eggs/setuptools-0.6c12dev_r85190-py2.6.egg/setuptools/archive_util.py", line 67, in unpack_archive driver(filename, extract_dir, progress_filter) File "/home/phil/local/src/mailman-3.0.0a6/eggs/setuptools-0.6c12dev_r85190-py2.6.egg/setuptools/archive_util.py", line 188, in unpack_tarfile while member.islnk() or member.issym(): AttributeError: 'NoneType' object has no attribute 'islnk' An error occurred when trying to install logilab-common 0.52.0. Look above this message for any errors that were output by easy_install. While: Installing pylint. Getting distribution for 'logilab-common>=0.50.1'. Error: Couldn't install: logilab-common 0.52.0 Let me know what else I can send you in regards to my environment. I am running a fairly fresh Ubuntu-10.04.1 with Python 2.6. ** Affects: mailman Importance: Undecided Status: New -- Corrupt eggs in mailman-3.0.0a6.tar.gz https://bugs.launchpad.net/bugs/656946 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 5

[Merge] lp:~jimmy-sigint/mailman/restapi_additional_attributes into lp:mailman
by Jimmy Bergman 29 Dec '10

29 Dec '10

Jimmy Bergman has proposed merging lp:~jimmy-sigint/mailman/restapi_additional_attributes into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) Related bugs: #659951 REST server should support a few more writable attributes to simplify integration https://bugs.launchpad.net/bugs/659951 -- https://code.launchpad.net/~jimmy-sigint/mailman/restapi_additional_attribu… Your team Mailman Coders is requested to review the proposed merge of lp:~jimmy-sigint/mailman/restapi_additional_attributes into lp:mailman.

2 1

[Merge] lp:~flo-fuchs/mailman/restclient into lp:mailman
by florianfuchs 26 Dec '10

26 Dec '10

florianfuchs has proposed merging lp:~flo-fuchs/mailman/restclient into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) I added a rest client in src/mailmanclient as well as a doctest in src/mailman/rest/docs/restclient.txt. -- 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.

3 6

[Bug 667249] [NEW] locknix should not depend on setuptools_bzr
by Barry Warsaw 27 Oct '10

27 Oct '10

Public bug reported: setuptools_bzr was a nice idea, but ultimately just a PITA. locknix depending on setuptools_bzr breaks Mailman 3 installation on Python 2.7 for Ubuntu and Debian. This dependency should just be removed. ** Affects: locknix Importance: Critical Assignee: Barry Warsaw (barry) Status: Confirmed ** Affects: mailman Importance: Critical Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: locknix Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: locknix Importance: Undecided => Critical ** Changed in: locknix Status: New => Triaged ** Changed in: locknix Status: Triaged => Confirmed ** Also affects: mailman Importance: Undecided Status: New ** Changed in: mailman Milestone: None => 3.0.0a7 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Importance: Undecided => Critical ** Changed in: mailman Status: New => Confirmed ** Changed in: locknix Milestone: None => 1.0.3 -- locknix should not depend on setuptools_bzr https://bugs.launchpad.net/bugs/667249 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 2

[Bug 661399] [NEW] Quiet parametr for creating "manual" MTA is noisy
by Bartosz Szatkowski 24 Oct '10

24 Oct '10

Public bug reported: [ steps ] call Mailman.MTA.Manual.create(..., quiet=True) eg if mm_cfg.MTA: modname = 'Mailman.MTA.' + mm_cfg.MTA __import__(modname) sys.modules[modname].create(mlist, quiet=True) [ result ] output: test-devel: "|/var/lib/mailman/mail/mailman post test-devel" test-devel-admin: "|/var/lib/mailman/mail/mailman admin test-devel" test-devel-bounces: "|/var/lib/mailman/mail/mailman bounces test-devel" test-devel-confirm: "|/var/lib/mailman/mail/mailman confirm test-devel" test-devel-join: "|/var/lib/mailman/mail/mailman join test-devel" test-devel-leave: "|/var/lib/mailman/mail/mailman leave test-devel" test-devel-owner: "|/var/lib/mailman/mail/mailman owner test-devel" test-devel-request: "|/var/lib/mailman/mail/mailman request test-devel" test-devel-subscribe: "|/var/lib/mailman/mail/mailman subscribe test-devel" test-devel-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe test-devel" [ expected result] totaly quiet "output" [ fix ] Sorry Iam kind of busy right now - cant make the patch Line 82-87 in Mailman/MTA/Manual.py should be indented one more level 82 print _("""\ 83 ## %(listname)s mailing list""") 84 outfp = sys.stdout 85 # Common path 86 for k, v in makealiases(listname): 87 print >> outfp, k + ':', ((fieldsz - len(k)) * ' '), v ** Affects: mailman Importance: Undecided Status: New -- Quiet parametr for creating "manual" MTA is noisy https://bugs.launchpad.net/bugs/661399 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 1

[Bug 265851] Re: feature: unified membership allow post list.
by Mark Sapiro 22 Oct '10

22 Oct '10

It seems that creating a list, say post-only, and putting '@post-only' in accept_these_nonmembers of those lists for which you want this enabled satisfies this request. This has been available since Mailman 2.1.10. See <https://bugs.launchpad.net/mailman/+bug/558204>. ** Changed in: mailman Status: New => Fix Committed -- feature: unified membership allow post list. https://bugs.launchpad.net/bugs/265851 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 265851] Re: feature: unified membership allow post list.
by Dave Neary 22 Oct '10

22 Oct '10

There is a patch for this by Jon Carnes from 2003 that uses the special list name "post-only" for mailman 2.1 which still applies pretty cleanly to Mailman/Handlers/Moderate.py on the tip of the 2.1 branch today. I assume it could easily be adapted for the 3.0 branch. http://www.mail-archive.com/mailman-users@python.org/msg14876.html The patch: *** jonc.Moderate.py Mon Jan 27 10:23:03 2003 --- Moderate.py Mon Jan 27 13:19:33 2003 *************** *** 25,28 **** --- 25,30 ---- from Mailman import Utils from Mailman import Message + from Mailman import MailList + from Mailman import MemberAdaptor from Mailman import Errors from Mailman.i18n import _ *************** *** 45,48 **** --- 47,59 ---- ^L + def CheckPostOnly(sender): + try: + m = MailList.MailList('post-only', lock=0) + return m.isMember(sender) + except Errors.MMListError: + return 0 + + + ^L def process(mlist, msg, msgdata): if msgdata.get('approved'): *************** *** 89,92 **** --- 100,105 ---- # From here on out, we're dealing with non-members. if matches_p(sender, mlist.accept_these_nonmembers): + return + if CheckPostOnly(sender): return if matches_p(sender, mlist.hold_these_nonmembers): -- feature: unified membership allow post list. https://bugs.launchpad.net/bugs/265851 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Merge] lp:~mmlmtp/mailman/mm3lmtp into lp:mailman
by Ian Eiloart 14 Oct '10

14 Oct '10

Ian Eiloart has proposed merging lp:~mmlmtp/mailman/mm3lmtp into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) Gives LMTP server the ability to reject mail to non-existent lists at LMTP time, and to reject mail from people who don't have permission to post to a list. -- The attached diff has been truncated due to its size. https://code.launchpad.net/~mmlmtp/mailman/mm3lmtp/+merge/38413 Your team Mailman Coders is requested to review the proposed merge of lp:~mmlmtp/mailman/mm3lmtp into lp:mailman.

1 0

Correction: Launchpad Bugs Re-enabling Auto Expiring Bugs
by deryck.hodge＠canonical.com 05 Oct '10

05 Oct '10

I recently sent you email about your project mailman at https://launchpad.net/mailman. You may have found that you could not view the configure bug tracker page. This is because the email was incorrectly sent to bug supervisors for the project, rather than project owners. Please disregard the previous email. Another email will be sent out shortly to project owners, who can then re-enable the bug expiry setting if this is desired. Deryck Hodge Launchpad Bugs Team Lead

1 0

Launchpad Bugs Re-enabling Auto Expiring Bugs
by deryck.hodge＠canonical.com 05 Oct '10

05 Oct '10

Bug expiry in Launchpad is changing ------------------------------------ The way Launchpad handles inactive bugs is changing. This affects your project GNU Mailman at https://launchpad.net/mailman What's going to change ----------------------- Right now, the bug expiry option is enabled for GNU Mailman but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including GNU Mailman. What this means for your project -------------------------------- If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire "Incomplete" bug reports when they become inactive' option on this page: https://bugs.launchpad.net/mailman/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this --------------------- Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Deryck Hodge Launchpad Bugs Team Lead

1 0

[Bug 617285] [NEW] Possible regression issue in MM3
by Anna 04 Oct '10

04 Oct '10

Public bug reported: Trying to retrieve a list of all mailing lists in the system (using the rest client) MM3 crashes with the traceback below. It seems to be a regression issue but I think it might also be a general bug since a non existing column in the DB is called. About the lock mentioned in the traceback: gallia is my wireless network and the processes I have running are Mailman 3 core and a Django app for the MM3 UI which should work together. anna@athena:~/Documents/Programmering/mailman3/mailman$ Traceback (most recent call last): File "/usr/lib/python2.6/wsgiref/handlers.py", line 93, in run self.result = application(self.environ, self.start_response) File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/wsgiapp.py", line 58, in __call__ environ, start_response) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/app.py", line 18, in __call__ response = self.get_response(request, resource_or_response) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/app.py", line 65, in get_response resource_or_response = resource_or_response(request) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/resource.py", line 211, in __call__ return _dispatch(request, match, lambda r: callable(self, r)) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/resource.py", line 239, in _dispatch response = func(request) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/resource.py", line 211, in <lambda> return _dispatch(request, match, lambda r: callable(self, r)) File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/lists.py", line 215, in collection resource = self._make_collection(request) File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/helpers.py", line 140, in _make_collection collection = self._get_collection(request) File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/lists.py", line 134, in _get_collection return list(getUtility(IListManager)) File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/model/listmanager.py", line 84, in __iter__ for fqdn_listname in self.names: File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/model/listmanager.py", line 90, in names for mlist in config.db.store.find(MailingList): File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/store.py", line 968, in __iter__ result = self._store._connection.execute(self._get_select()) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/database.py", line 217, in execute raw_cursor = self.raw_execute(statement, params) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/databases/sqlite.py", line 153, in raw_execute return Connection.raw_execute(self, statement, params) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/database.py", line 299, in raw_execute self._check_disconnect(raw_cursor.execute, *args) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/database.py", line 342, in _check_disconnect return function(*args, **kwargs) OperationalError: no such column: mailinglist.last_post_at Aug 13 10:52:47 2010 (2982) timed out Usage: master [options] Master sub-process watcher. Start and watch the configured queue runners and ensure that they stay alive and kicking. Each are fork and exec'd in turn, with the master waiting on their process ids. When it detects a child queue runner has exited, it may restart it. The queue runners respond to SIGINT, SIGTERM, SIGUSR1 and SIGHUP. SIGINT, SIGTERM and SIGUSR1 all cause the qrunners to exit cleanly. The master will restart qrunners that have exited due to a SIGUSR1 or some kind of other exit condition (say because of an exception). SIGHUP causes the master and the qrunners to close their log files, and reopen then upon the next printed message. The master also responds to SIGINT, SIGTERM, SIGUSR1 and SIGHUP, which it simply passes on to the qrunners. Note that the master will close and reopen its own log files on receipt of a SIGHUP. The master also leaves its own process id in the file `data/master-qrunner.pid` but you normally don't need to use this pid directly. master: error: The master qrunner lock could not be acquired, because it appears as if some process on some other host may have acquired it. We can't test for stale locks across host boundaries, so you'll have to clean this up manually. Lock file: /home/anna/Documents/Programmering/mailman3/mailman/var/locks/master-qrunner.lck Lock host: gallia Exiting. Traceback (most recent call last): File "/usr/lib/python2.6/wsgiref/handlers.py", line 93, in run self.result = application(self.environ, self.start_response) File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/wsgiapp.py", line 58, in __call__ environ, start_response) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/app.py", line 18, in __call__ response = self.get_response(request, resource_or_response) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/app.py", line 65, in get_response resource_or_response = resource_or_response(request) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/resource.py", line 211, in __call__ return _dispatch(request, match, lambda r: callable(self, r)) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/resource.py", line 239, in _dispatch response = func(request) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/resource.py", line 211, in <lambda> return _dispatch(request, match, lambda r: callable(self, r)) File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/lists.py", line 215, in collection resource = self._make_collection(request) File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/helpers.py", line 140, in _make_collection collection = self._get_collection(request) File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/lists.py", line 134, in _get_collection return list(getUtility(IListManager)) File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/model/listmanager.py", line 84, in __iter__ for fqdn_listname in self.names: File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/model/listmanager.py", line 90, in names for mlist in config.db.store.find(MailingList): File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/store.py", line 968, in __iter__ result = self._store._connection.execute(self._get_select()) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/database.py", line 217, in execute raw_cursor = self.raw_execute(statement, params) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/databases/sqlite.py", line 153, in raw_execute return Connection.raw_execute(self, statement, params) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/database.py", line 299, in raw_execute self._check_disconnect(raw_cursor.execute, *args) File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/database.py", line 342, in _check_disconnect return function(*args, **kwargs) OperationalError: no such column: mailinglist.last_post_at ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 rest-api -- Possible regression issue in MM3 https://bugs.launchpad.net/bugs/617285 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 4

[Bug 266317] Re: attachments archived even when archiving disabled
by Mark Sapiro 01 Oct '10

01 Oct '10

The question is what to do? The attachments are not really stored "in the archive". They are just stored in a web accessible place with a known, hopefully valid URL. In fact, if the list does do archiving and is digestible, the scrubbed attachments are stored twice, once for the archive and linked from the archive and once for the digest and linked from the digest. (This duplication probably is a bug, but not one I know how to fix for MM 2.1.) If the list is digestable, any MIME parts which are not text/plain with known character set cannot be directly included in the plain (RFC 1153) format digest. They either have to be stored aside in some accessible place and linked from the digest, or a note can be put in the digest that an attachment has been removed and if you want attachments in the future switch to messages or the MIME digest, or the attachments can be silently ignored. I suppose this choice could be a site or list setting, instead of being fixed at the first alternative, but I think this is properly called a design decision, not a bug. -- attachments archived even when archiving disabled https://bugs.launchpad.net/bugs/266317 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 266317] Re: attachments archived even when archiving disabled
by Barry Warsaw 01 Oct '10

01 Oct '10

Setting back to New state because I do think that when archiving is disabled, the scrubber shouldn't store the attachments on disk. IOW, it's a legitimate bug. ** Changed in: mailman Status: Invalid => New -- attachments archived even when archiving disabled https://bugs.launchpad.net/bugs/266317 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 651980] [NEW] Friendlier "awaits moderator approval text"
by spaetz 01 Oct '10

01 Oct '10

Public bug reported: Here is the reaction of Kernel Hacker Neil brown, trying to send a mail to a mailman-member only list. I agree that the standard blurb reads drier and more unfriendly than it could be and I would love to see mailman adopt a text similar to what he proposed: I tried to identify what I really didn't like about the "Your message awaits moderator approval" email I got and it seems to come down to the "to a members only list" part. It comes across as saying "we are a closed community and aren't interested in what others have to say" - which clearly isn't true, but does seem to be implied by the text. Had the message been more friendly, e.g. ------------ Thanks for your email with subject: $SUBJECT As this is your first post to $LISTNAME the message will require approval by a moderator after which it will, if acceptable, be forwarded to the list. This normally takes $AVERAGE_WAIT_TIME. Subsequent posts by you will then be accepted without moderation. ------------ then I would have had nothing to complain about. I think it is important that newcomers feel welcomed and "members only" doesn't sound welcoming. ** Affects: mailman Importance: Undecided Status: New -- Friendlier "awaits moderator approval text" https://bugs.launchpad.net/bugs/651980 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 2