Mailman 3 November 2010 - Mailman-coders

[Bug 666181] [NEW] wrong From field in subscription notification to admin
by Ilya Belyy June 15, 2012

June 15, 2012

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 677115] [NEW] Reply to to part 3 of a held message notification containing a Approved: first body line fails if reply is base64 encoded.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: A list moderator receives a held message notification and attempts to approve the message by replying to the third part (second attachment) and including an Approved: <password> line as the first line of the reply. If the moderator's MUA base64 encodes the reply for i18n or other reasons, the Approved: line is not found and the message is discarded. ** Affects: mailman Importance: Undecided Status: New -- Reply to to part 3 of a held message notification containing a Approved: first body line fails if reply is base64 encoded. https://bugs.launchpad.net/bugs/677115 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 2

[Bug 670988] [NEW] Missing format character in Spanish translation
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: The Spanish (es) translation of the bin/check_perms message "%(path)s bad group (has: %(groupname)s, expected %(MAILMAN_GROUP)s)" is missing the 's' in '%(path)s'. This prevents check_perms from reporting/fixing group errors and any other problems not found before the first group error. ** Affects: mailman Importance: Undecided Status: New -- Missing format character in Spanish translation https://bugs.launchpad.net/bugs/670988 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 2

[Bug 600780] [NEW] Login function needed in rest-client
by Anna April 6, 2012

April 6, 2012

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 June 13, 2011

June 13, 2011

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 April 29, 2011

April 29, 2011

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 April 29, 2011

April 29, 2011

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 April 29, 2011

April 29, 2011

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 April 29, 2011

April 29, 2011

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 April 29, 2011

April 29, 2011

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