From mark at msapiro.net Fri Oct 1 07:15:08 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 01 Oct 2010 05:15:08 -0000 Subject: [Bug 651980] Re: Friendlier "awaits moderator approval text" References: <20100930120424.24671.32739.malonedeb@soybean.canonical.com> Message-ID: <20101001051508.18487.72159.malone@wampee.canonical.com> Actually, the message is configurable, but not by the list owner. It is built from the postheld.txt template which is not currently editable by the list owner, but can be edited and installed either sitewide, domainwide or for a specific list or lists by the site admin. See the FAQ at for information on editing templates. I have marked this as a wishlist item specifically as a request to make this template editable from the list admin GUI. ** Changed in: mailman Importance: Undecided => Wishlist ** Changed in: mailman Status: New => Opinion -- 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. From 266317 at bugs.launchpad.net Fri Oct 1 18:20:23 2010 From: 266317 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 01 Oct 2010 16:20:23 -0000 Subject: [Bug 266317] Re: attachments archived even when archiving disabled References: <20080905193054.27052.86428.launchpad@forster.canonical.com> Message-ID: <20101001162023.7138.90542.malone@soybean.canonical.com> 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. From mark at msapiro.net Fri Oct 1 18:57:59 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 01 Oct 2010 16:57:59 -0000 Subject: [Bug 266317] Re: attachments archived even when archiving disabled References: <20080905193054.27052.86428.launchpad@forster.canonical.com> Message-ID: <20101001165759.2618.14119.malone@palladium.canonical.com> 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. From anna.granudd at gmail.com Mon Oct 4 12:18:02 2010 From: anna.granudd at gmail.com (Anna) Date: Mon, 04 Oct 2010 10:18:02 -0000 Subject: [Bug 617285] Re: Possible regression issue in MM3 References: <20100813091958.4924.37465.malonedeb@gandwana.canonical.com> Message-ID: <20101004101802.15155.23184.malone@potassium.ubuntu.com> Sorry for the late response. I've been trying to reproduce the bug but just like you I'm not able to any more. It is possible that it was due to a migration issue and that the data base was out of sync so I think the bug can be closed for now. If I'll find a way to reproduce the bug later I'll let you know. -- 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. From 617285 at bugs.launchpad.net Mon Oct 4 16:01:20 2010 From: 617285 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 04 Oct 2010 14:01:20 -0000 Subject: [Bug 617285] Re: Possible regression issue in MM3 References: <20100813091958.4924.37465.malonedeb@gandwana.canonical.com> Message-ID: <20101004140120.2665.27094.malone@wampee.canonical.com> Thanks Anna. Closing. ** Changed in: mailman Status: Incomplete => Invalid -- 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. From deryck.hodge at canonical.com Tue Oct 5 21:15:39 2010 From: deryck.hodge at canonical.com (deryck.hodge at canonical.com) Date: Tue, 05 Oct 2010 19:15:39 -0000 Subject: Launchpad Bugs Re-enabling Auto Expiring Bugs Message-ID: <20101005191539.4244.78111.launchpad@loganberry.canonical.com> 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 From deryck.hodge at canonical.com Wed Oct 6 00:11:45 2010 From: deryck.hodge at canonical.com (deryck.hodge at canonical.com) Date: Tue, 05 Oct 2010 22:11:45 -0000 Subject: Correction: Launchpad Bugs Re-enabling Auto Expiring Bugs Message-ID: <20101005221145.22631.60279.launchpad@loganberry.canonical.com> 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 From 656946 at bugs.launchpad.net Fri Oct 8 17:46:14 2010 From: 656946 at bugs.launchpad.net (Phil King) Date: Fri, 08 Oct 2010 15:46:14 -0000 Subject: [Bug 656946] [NEW] Corrupt eggs in mailman-3.0.0a6.tar.gz References: <20101008154614.6625.95606.malonedeb@wampee.canonical.com> Message-ID: <20101008154614.6625.95606.malonedeb@wampee.canonical.com> 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 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 "", line 1, in 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 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. From 656946 at bugs.launchpad.net Fri Oct 8 21:03:14 2010 From: 656946 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 08 Oct 2010 19:03:14 -0000 Subject: [Bug 656946] Re: Corrupt eggs in mailman-3.0.0a6.tar.gz References: <20101008154614.6625.95606.malonedeb@wampee.canonical.com> Message-ID: <20101008190315.24431.63047.launchpad@wampee.canonical.com> ** Tags added: mailman3 -- 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. From 656946 at bugs.launchpad.net Fri Oct 8 21:17:15 2010 From: 656946 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 08 Oct 2010 19:17:15 -0000 Subject: [Bug 656946] Re: Corrupt eggs in mailman-3.0.0a6.tar.gz References: <20101008154614.6625.95606.malonedeb@wampee.canonical.com> Message-ID: <20101008191715.24431.82660.malone@wampee.canonical.com> The first problem (no module named zc.buildout.buildout) is due to a faulty MANIFEST.in that let the eggs/ and parts/ directories leak into the tarball. I've fixed this for alpha7 but you were exactly right that the workaround is just to delete those two directories and start over. I can reproduce the AttributeError locally. I suspect this is a bug in setuptools-0.6c12dev. I'll see if pinning the version for that fixes the problem and make sure that it's reported upstream. I'll follow up when any workaround I find. ** Changed in: mailman Status: New => Triaged ** Changed in: mailman Status: Triaged => In Progress ** Changed in: mailman Importance: Undecided => Critical ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a7 -- 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. From 656946 at bugs.launchpad.net Fri Oct 8 21:20:44 2010 From: 656946 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 08 Oct 2010 19:20:44 -0000 Subject: [Bug 656946] Re: Corrupt eggs in mailman-3.0.0a6.tar.gz References: <20101008154614.6625.95606.malonedeb@wampee.canonical.com> Message-ID: <20101008192047.18543.47281.launchpad@loganberry.canonical.com> ** Branch linked: lp:mailman -- 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. From 656946 at bugs.launchpad.net Mon Oct 11 17:45:05 2010 From: 656946 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 11 Oct 2010 15:45:05 -0000 Subject: [Bug 656946] Re: Corrupt eggs in mailman-3.0.0a6.tar.gz References: <20101008154614.6625.95606.malonedeb@wampee.canonical.com> Message-ID: <20101011154505.24291.95840.malone@palladium.canonical.com> The logilab problem was a bug in setuptools, which has since been fixed. ** Changed in: mailman Status: In Progress => Fix Committed -- 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. From jimmy at sigint.se Wed Oct 13 16:31:42 2010 From: jimmy at sigint.se (Jimmy Bergman) Date: Wed, 13 Oct 2010 14:31:42 -0000 Subject: [Bug 659951] [NEW] REST server should support a few more writable attributes to simplify integration References: <20101013143142.4876.20255.malonedeb@palladium.canonical.com> Message-ID: <20101013143142.4876.20255.malonedeb@palladium.canonical.com> 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. From jimmy at sigint.se Wed Oct 13 16:40:07 2010 From: jimmy at sigint.se (Jimmy Bergman) Date: Wed, 13 Oct 2010 14:40:07 -0000 Subject: [Bug 659951] Re: REST server should support a few more writable attributes to simplify integration References: <20101013143142.4876.20255.malonedeb@palladium.canonical.com> Message-ID: <20101013144008.6924.15835.launchpad@potassium.ubuntu.com> ** Branch linked: lp:~jimmy-sigint/mailman/restapi_additional_attributes ** Tags added: mailman3 -- 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. From 659951 at bugs.launchpad.net Wed Oct 13 22:25:55 2010 From: 659951 at bugs.launchpad.net (Barry Warsaw) Date: Wed, 13 Oct 2010 20:25:55 -0000 Subject: [Bug 659951] Re: REST server should support a few more writable attributes to simplify integration References: <20101013143142.4876.20255.malonedeb@palladium.canonical.com> Message-ID: <20101013202555.3009.37489.malone@soybean.canonical.com> Hi Jimmy. You should do a merge proposal for your branch. :) ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Milestone: None => 3.0.0a7 ** Changed in: mailman Importance: Undecided => Medium -- 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. From jimmy at sigint.se Thu Oct 14 09:31:45 2010 From: jimmy at sigint.se (Jimmy Bergman) Date: Thu, 14 Oct 2010 07:31:45 -0000 Subject: [Merge] lp:~jimmy-sigint/mailman/restapi_additional_attributes into lp:mailman Message-ID: <20101014073144.8590.88742.launchpad@loganberry.canonical.com> 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_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. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 4892 bytes Desc: not available URL: From iane at sussex.ac.uk Thu Oct 14 14:16:40 2010 From: iane at sussex.ac.uk (Ian Eiloart) Date: Thu, 14 Oct 2010 12:16:40 -0000 Subject: [Merge] lp:~mmlmtp/mailman/mm3lmtp into lp:mailman Message-ID: <20101014121640.27616.42090.launchpad@loganberry.canonical.com> 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 524288 bytes Desc: not available URL: From bulislaw at gmail.com Fri Oct 15 20:34:23 2010 From: bulislaw at gmail.com (Bartosz Szatkowski) Date: Fri, 15 Oct 2010 18:34:23 -0000 Subject: [Bug 661399] [NEW] Quiet parametr for creating "manual" MTA is noisy References: <20101015183423.8128.86866.malonedeb@palladium.canonical.com> Message-ID: <20101015183423.8128.86866.malonedeb@palladium.canonical.com> 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. From dneary at gnome.org Fri Oct 22 10:57:52 2010 From: dneary at gnome.org (Dave Neary) Date: Fri, 22 Oct 2010 08:57:52 -0000 Subject: [Bug 265851] Re: feature: unified membership allow post list. References: <20080905192629.27052.58703.launchpad@forster.canonical.com> Message-ID: <20101022085752.24035.61257.malone@potassium.ubuntu.com> 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 at 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. From mark at msapiro.net Fri Oct 22 20:44:45 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 22 Oct 2010 18:44:45 -0000 Subject: [Bug 265851] Re: feature: unified membership allow post list. References: <20080905192629.27052.58703.launchpad@forster.canonical.com> Message-ID: <20101022184446.31341.68331.malone@gandwana.canonical.com> 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 . ** 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. From mark at msapiro.net Sun Oct 24 19:33:16 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 24 Oct 2010 17:33:16 -0000 Subject: [Bug 661399] Re: Quiet parametr for creating "manual" MTA is noisy References: <20101015183423.8128.86866.malonedeb@palladium.canonical.com> Message-ID: <20101024173317.12745.23676.malone@wampee.canonical.com> The current behavior is what is intended. The only thing in Mailman which calls MTA.Manual.create(..., quiet=True) is "bin/genaliases --quiet" when MTA="Manual". The documentation for the genaliases --quiet option is . Some MTA output can include more verbose help text. Use this to tone . down the verbosity. Further, when MTA = "Manual" the only thing genaliases does is print aliases. Thus, if calling MTA.Manual.create(..., quiet=True) produced no output, "bin/genaliases --quiet" would do nothing so why would one want to run it at all. ** Changed in: mailman Status: New => Invalid ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- 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. From 666181 at bugs.launchpad.net Mon Oct 25 10:37:00 2010 From: 666181 at bugs.launchpad.net (Ilya Belyy) Date: Mon, 25 Oct 2010 08:37:00 -0000 Subject: [Bug 666181] [NEW] wrong From field in subscription notification to admin References: <20101025083700.23959.33.malonedeb@potassium.ubuntu.com> Message-ID: <20101025083700.23959.33.malonedeb@potassium.ubuntu.com> 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 at wefqwefqwef.com Subscribed: lkjhlkhlkh at wefqwefqwef.com Notification email to the admin of ml01 will look as following: Subject: Ml01 subscription notification From: mailman at dom.2 To: mladmin00 at dom.1 Message-ID: Date: Mon, 25 Oct 2010 14:51:03 +0700 Subscribed: lkjhlkhlkh at 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. From 666181 at bugs.launchpad.net Mon Oct 25 10:37:00 2010 From: 666181 at bugs.launchpad.net (Ilya Belyy) Date: Mon, 25 Oct 2010 08:37:00 -0000 Subject: [Bug 666181] Re: wrong From field in subscription notification to admin References: <20101025083700.23959.33.malonedeb@potassium.ubuntu.com> Message-ID: <20101025083701.23959.50216.malone@potassium.ubuntu.com> ** Patch added: "mailman-2.1.9-fix.diff" https://bugs.launchpad.net/bugs/666181/+attachment/1710237/+files/mailman-2.1.9-fix.diff -- 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. From 667249 at bugs.launchpad.net Wed Oct 27 14:10:42 2010 From: 667249 at bugs.launchpad.net (Barry Warsaw) Date: Wed, 27 Oct 2010 12:10:42 -0000 Subject: [Bug 667249] [NEW] locknix should not depend on setuptools_bzr References: <20101027121042.17514.84808.malonedeb@potassium.ubuntu.com> Message-ID: <20101027121042.17514.84808.malonedeb@potassium.ubuntu.com> 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. From 667252 at bugs.launchpad.net Wed Oct 27 14:23:55 2010 From: 667252 at bugs.launchpad.net (Simon Fraser) Date: Wed, 27 Oct 2010 12:23:55 -0000 Subject: [Bug 667252] [NEW] Mailman 3 Branch, install fails with --prefix specified References: <20101027122355.7038.41189.malonedeb@gandwana.canonical.com> Message-ID: <20101027122355.7038.41189.malonedeb@gandwana.canonical.com> 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. From 667252 at bugs.launchpad.net Wed Oct 27 15:04:47 2010 From: 667252 at bugs.launchpad.net (Barry Warsaw) Date: Wed, 27 Oct 2010 13:04:47 -0000 Subject: [Bug 667252] Re: Mailman 3 Branch, install fails with --prefix specified References: <20101027122355.7038.41189.malonedeb@gandwana.canonical.com> Message-ID: <20101027130447.28216.60598.launchpad@soybean.canonical.com> ** Tags added: mailman3 ** Changed in: mailman Status: New => Triaged -- 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. From 667249 at bugs.launchpad.net Wed Oct 27 17:11:27 2010 From: 667249 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Wed, 27 Oct 2010 15:11:27 -0000 Subject: [Bug 667249] Re: locknix should not depend on setuptools_bzr References: <20101027121042.17514.84808.malonedeb@potassium.ubuntu.com> Message-ID: <20101027151128.14391.43720.launchpad@loganberry.canonical.com> ** Branch linked: lp:locknix -- 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. From 667249 at bugs.launchpad.net Wed Oct 27 17:24:26 2010 From: 667249 at bugs.launchpad.net (Barry Warsaw) Date: Wed, 27 Oct 2010 15:24:26 -0000 Subject: [Bug 667249] Re: locknix should not depend on setuptools_bzr References: <20101027121042.17514.84808.malonedeb@potassium.ubuntu.com> Message-ID: <20101027152428.8539.13286.launchpad@gandwana.canonical.com> ** Changed in: locknix Status: Confirmed => Fix Released ** Changed in: mailman Status: Confirmed => Fix Released -- 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. From 667472 at bugs.launchpad.net Wed Oct 27 23:21:00 2010 From: 667472 at bugs.launchpad.net (Barry Warsaw) Date: Wed, 27 Oct 2010 21:21:00 -0000 Subject: [Bug 667472] [NEW] Support Python 2.7 References: <20101027212100.17225.39924.malonedeb@gandwana.canonical.com> Message-ID: <20101027212100.17225.39924.malonedeb@gandwana.canonical.com> 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. From 667472 at bugs.launchpad.net Wed Oct 27 23:24:50 2010 From: 667472 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Wed, 27 Oct 2010 21:24:50 -0000 Subject: [Bug 667472] Re: Support Python 2.7 References: <20101027212100.17225.39924.malonedeb@gandwana.canonical.com> Message-ID: <20101027212502.9215.74104.launchpad@loganberry.canonical.com> ** Branch linked: lp:mailman -- 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.