Mailman 3 February 2016 - Mailman-coders

[Bug 1450469] [NEW] install step using buildout fails with os.path.walk error
by Billy Glynn March 1, 2016

March 1, 2016

Public bug reported: (venv)[root@lists mailman-bundler-3.0.0]# buildout Creating directory '/usr/local/src/mailman-bundler-3.0.0/bin'. Creating directory '/usr/local/src/mailman-bundler-3.0.0/parts'. Creating directory '/usr/local/src/mailman-bundler-3.0.0/eggs'. Creating directory '/usr/local/src/mailman-bundler-3.0.0/develop-eggs'. Develop: '/usr/local/src/mailman-bundler-3.0.0/.' warning: no files found matching '*.in' under directory 'mailman_bundler' warning: no files found matching '*.in' under directory 'deployment' warning: no files found matching 'deployment/mailman-web.logrotate.conf' Getting distribution for 'djangorecipe'. Got djangorecipe 1.11. Getting distribution for 'Django'. warning: no previously-included files matching '__pycache__' found under directory '*' warning: no previously-included files matching '*.py[co]' found under directory '*' Got Django 1.8. Getting distribution for 'zc.recipe.egg>=2.0.0a3'. Got zc.recipe.egg 2.0.1. Getting distribution for 'collective.recipe.cmd'. warning: no previously-included files matching '*.pyc' found anywhere in distribution Got collective.recipe.cmd 0.10. Getting distribution for 'z3c.recipe.filetemplate'. Got z3c.recipe.filetemplate 2.2.0. While: Installing. Getting section templates. Initializing section templates. An internal error occurred due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "/usr/local/src/mailman-bundler-3.0.0/venv/lib/python3.4/site-packages/zc/buildout/buildout.py", line 1946, in main getattr(buildout, command)(args) File "/usr/local/src/mailman-bundler-3.0.0/venv/lib/python3.4/site-packages/zc/buildout/buildout.py", line 510, in install [self[part]['recipe'] for part in install_parts] File "/usr/local/src/mailman-bundler-3.0.0/venv/lib/python3.4/site-packages/zc/buildout/buildout.py", line 510, in <listcomp> [self[part]['recipe'] for part in install_parts] File "/usr/local/src/mailman-bundler-3.0.0/venv/lib/python3.4/site-packages/zc/buildout/buildout.py", line 1098, in __getitem__ options._initialize() File "/usr/local/src/mailman-bundler-3.0.0/venv/lib/python3.4/site-packages/zc/buildout/buildout.py", line 1202, in _initialize self.initialize() File "/usr/local/src/mailman-bundler-3.0.0/venv/lib/python3.4/site-packages/zc/buildout/buildout.py", line 1211, in initialize self.recipe = recipe_class(buildout, name, self) File "/usr/local/src/mailman-bundler-3.0.0/eggs/z3c.recipe.filetemplate-2.2.0-py3.4.egg/z3c/recipe/filetemplate/__init__.py", line 145, in __init__ os.path.walk( AttributeError: 'module' object has no attribute 'walk' ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1450469 Title: install step using buildout fails with os.path.walk error To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1450469/+subscriptions

3 3

[Bug 1517446] [NEW] Please add multipart/signed to DEFAULT_PASS_MIME_TYPES
by carloslp Feb. 28, 2016

Feb. 28, 2016

Public bug reported: Mailman tarballs contain a Defaults.py file with this configuration: DEFAULT_PASS_MIME_TYPES = ['multipart/mixed','multipart/alternative','text/plain'] NOTE: I don't know how this file is generated, I found it on the tarballs but not on the repository So, when someone enables filtering on a mailing list by mime-type, the default is to filter all emails not matching any of those 3 mime-types. This list of default mime types allowed misses to include "multipart/signed". Therefore, this is unfortunately filtering any "multipart/signed" emails. "multipart/signed" is defined on RFC 3156 <https://tools.ietf.org/html/rfc3156> and is the recommended way of signing mails with GPG. See http://wiki.gnupg.org/SignatureHandling The proposed change is to modify that default configuration to: DEFAULT_PASS_MIME_TYPES = ['multipart/mixed', 'multipart/alternative', 'multipart/signed', 'text/plain', ] This default causes trouble to people that signs their mails with GPG. I already had problems due to this default on the Alioth Debian mailing lists and on the WebKit mailing lists because the admin enabled filtering by mime-type and didn't changed the default. Please, change this default by adding at least 'multipart/signed' to the list of types allowed. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1517446 Title: Please add multipart/signed to DEFAULT_PASS_MIME_TYPES To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1517446/+subscriptions

3 5

[Bug 1546679] [NEW] User's acknowlege option doesn't work on anonymous lists.
by Mark Sapiro Feb. 28, 2016

Feb. 28, 2016

Public bug reported: We actually save the original sender for Acknowledge.py in the message metadata as it passes through the pipeline, but we don't save it soon enough. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1546679 Title: User's acknowlege option doesn't work on anonymous lists. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1546679/+subscriptions

2 3

[Bug 558167] Re: Use correct char set for command-line scripts
by Mark Sapiro Feb. 28, 2016

Feb. 28, 2016

** Changed in: mailman Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558167 Title: Use correct char set for command-line scripts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558167/+subscriptions

1 0

[Bug 1549420] [NEW] DMARC munging fails on subdomains that use parent domain policy
by Robert Mathews Feb. 28, 2016

Feb. 28, 2016

Public bug reported: An address ending with "@reply.yahoo.com" posted a message to a list that has "dmarc_moderation_action" set to "Munge From". This causes IsDMARCProhibited() in Utils.py to lookup TXT records for "_dmarc.reply.yahoo.com". It finds none, so Mailman does not apply the munging. However, in this situation, DMARC "clients" apparently need to look "up the chain" at "_dmarc.yahoo.com". See RFC 7489 section 4.3 point 7, and section 6.6.3 point 3 ("Organizational Domain"), and here's an example of it in action: https://dmarcian.com/dmarc-inspector/reply.yahoo.com The result of this bug is that mail from a subdomain like "@reply.yahoo.com" does not get munged, but does get rejected downstream by yahoo.com/gmail.com etc. for failing DMARC policy. (I'm using Mailman 2.1.20.) ** Affects: mailman Importance: Undecided Status: New ** Tags: dmarc -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1549420 Title: DMARC munging fails on subdomains that use parent domain policy To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1549420/+subscriptions

4 9

[Bug 558167] Re: Use correct char set for command-line scripts
by Mark Sapiro Feb. 27, 2016

Feb. 27, 2016

** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.21 ** 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/558167 Title: Use correct char set for command-line scripts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558167/+subscriptions

1 0

[Merge] lp:~futatuki/mailman/2.1-commandline-locale into lp:mailman/2.1
by Yasuhito FUTATSUKI＠POEM Feb. 27, 2016

Feb. 27, 2016

Yasuhito FUTATSUKI at POEM has proposed merging lp:~futatuki/mailman/2.1-commandline-locale into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~futatuki/mailman/2.1-commandline-locale/+merge/… This is a branch to fix bug #558167 . With this changes, command line utilities show messages as LC_CTYPE and LC_MESSAGES specified, if they have appropriate translation. -- Your team Mailman Coders is requested to review the proposed merge of lp:~futatuki/mailman/2.1-commandline-locale into lp:mailman/2.1.

2 1

[Bug 558167] Re: Use correct char set for command-line scripts
by Yasuhito FUTATSUKI＠POEM Feb. 26, 2016

Feb. 26, 2016

I have tested for each commands under bin, with -h option on both of ja_JP.UTF-8 and ja_JP.eucJP terminal environment by using LC_CTYPE and LC_MESSAGES environment variables. It works fine. Some commands still outputs untranslated messages, bin/b4b5-archfix and bin/transcheck for example, but It is because those messages are not wrapped in _() or C_(). I'll send merge request. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558167 Title: Use correct char set for command-line scripts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558167/+subscriptions

1 0

[Bug 558167] Re: Use correct char set for command-line scripts
by Yasuhito FUTATSUKI＠POEM Feb. 22, 2016

Feb. 22, 2016

** Branch linked: lp:mailman/2.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/558167 Title: Use correct char set for command-line scripts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558167/+subscriptions

1 0

[Bug 558167] Re: Use correct char set for command-line scripts
by Yasuhito FUTATSUKI＠POEM Feb. 22, 2016

Feb. 22, 2016

This bug still annoys Japanese users using ja_JP.UTF-8 locale on their terminals, using euc-jp as list charset. Fortunately, patch attached to comment #1 has been maintained on rpm sources for fedora/RHEL with additional patches, so I'm try to review them and working on a branch to follow latest 2.1 branch, lp:mailman/2.1-commandline-locale (merged these patches, fix for potfile making, but not tested yet). -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558167 Title: Use correct char set for command-line scripts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558167/+subscriptions

1 0