Mailman 3 July 2014 - Mailman-coders

[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 967951] [NEW] The LMTP runner should reject messages with duplicate Message-IDs
by Barry Warsaw 06 Mar '15

06 Mar '15

Public bug reported: Subject says it all. Mailman 3 requires unique Message-IDs for posts. ** Affects: mailman Importance: Undecided Status: New ** Tags: easy mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/967951 Title: The LMTP runner should reject messages with duplicate Message-IDs To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967951/+subscriptions

6 8

[Merge] lp:~mgill25/mailman/mailman into lp:mailman
by Manish Gill 05 Mar '15

05 Mar '15

Manish Gill has proposed merging lp:~mgill25/mailman/mailman into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) Related bugs: Bug #1166911 in GNU Mailman: "domain option for `bin/mailman lists` doesn't work as expected" https://bugs.launchpad.net/mailman/+bug/1166911 For more details, see: https://code.launchpad.net/~mgill25/mailman/mailman/+merge/157920 Fix for #1166911 -- https://code.launchpad.net/~mgill25/mailman/mailman/+merge/157920 Your team Mailman Coders is requested to review the proposed merge of lp:~mgill25/mailman/mailman into lp:mailman.

2 1

[Bug 1287604] [NEW] Enhancement: Sanity Check Subscribers MX Record
by John Howe 15 Feb '15

15 Feb '15

Public bug reported: Attempted to path mailman 2.1.17 with a simple MX record check on web- based subscribers. Running Debian 7.4 python 2.7.3-4+deb7u1 python-dns 2.3.6-1+deb7u1 Python-dns installed to /usr/lib/python2.7/dist-packages/DNS Attempted patches follow dragon@quantum:/usr/local/mailman/Mailman/Cgi $ diff subscribe.py subscribe.py.dns 212a213,221 > except Errors.MMBadEmailHostNotFoundError: > results = _("""\ > The email address you supplied is not valid. Host not found.""") > except Errors.MMBadEmailMXRecordNotFoundError: > results = _("""\ > The email address you supplied does not have a MX record.""") > except Errors.MMBadEmailUnknownDNSError: > results = _("""\ > The email address you supplied had some unknown DNS error.""") dragon@quantum:/usr/local/mailman/Mailman $ diff Utils.py Utils.py.dns 40a41 > import DNS 237a239,247 > # MX Record sanity checks > try: > mx_host - DNS.mxlookup(domain_parts) > if len(mx_host) < 1: > raise Errors.MMBadEmailMXRecordNotFoundError, s > except DNS.Base.ServerError: > raise Errors.MMBadEmailHostNotFoundError, s > except: > raise Errors.MMBadEmailUnknownDNSError, s dragon@quantum:/usr/local/mailman/Mailman $ diff Errors.py Errors.py.dns 98a99,110 > class MMBadEmailHostNotFoundError(EmailAddressError): > """Email address domain name does not resolve to a known host.""" > pass > > class MMBadEmailMXRecordNotFoundError(EmailAddressError): > """Email address domain name does not have a MX record.""" > pass > > class MMBadEmailUnknownDNSError(EmailAddressError): > """Email address domain name had unknown DNS error.""" > pass > When running said patches, mailman complained with: admin(13907): [----- Mailman Version: 2.1.17 -----] admin(13907): [----- Traceback ------] admin(13907): Traceback (most recent call last): admin(13907): File "/usr/local/mailman-2.1.17/scripts/driver", line 102, in run_main admin(13907): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(13907): File "/usr/local/mailman-2.1.17/Mailman/Cgi/confirm.py", line 27, in <module> admin(13907): from Mailman import MailList admin(13907): File "/usr/local/mailman-2.1.17/Mailman/MailList.py", line 45, in <module> admin(13907): from Mailman import Utils admin(13907): File "/usr/local/mailman-2.1.17/Mailman/Utils.py", line 41, in <module> admin(13907): import DNS admin(13907): ImportError: No module named DNS admin(13907): [----- Python Information -----] admin(13907): sys.version = 2.7.3 (default, Jan 2 2013, 13:56:14) [GCC 4.7.2] admin(13907): sys.executable = /usr/bin/python admin(13907): sys.prefix = /usr admin(13907): sys.exec_prefix = /usr admin(13907): sys.path = ['/usr/local/mailman-2.1.17/pythonlib', '/usr/local/mailman-2.1.17', '/usr/local/mailman-2.1.17/scripts', '/usr/local/mailman-2.1.17', '/usr/lib/python2.7/', '/usr/lib/python2.7/plat-linux2', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/lib/python2.7/site-packages'] admin(13907): sys.platform = linux2 AFAICS, it seems like Utils.py isn't locating the system wide python-dns library. How do I modify the sys.path to include python-dns under /usr/lib/python2.7/dist-packages? Thanks ** 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/1287604 Title: Enhancement: Sanity Check Subscribers MX Record To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1287604/+subscriptions

2 5

[Bug 1234567] [NEW] Czech catalog bug
by Jan Kratochvil 30 Jan '15

30 Jan '15

Public bug reported: obvious ** Affects: mailman Importance: Undecided Status: New ** Patch added: "fix" https://bugs.launchpad.net/bugs/1234567/+attachment/3856819/+files/mailman-… -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1234567 Title: Czech catalog bug To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1234567/+subscriptions

4 5

[Bug 1331194] [NEW] French translation on main Mailman page
by Emmanuel Décarie 29 Jan '15

29 Jan '15

Public bug reported: Mailman version 2.1.15 On the main page of a list: /cgi-bin/mailman/listinfo/mylist.org the french translation is: "Vous recevrez un courriel de requête de confirmation, cela empêche que d'autres personnes vous abonnement impunément. " but should be: "Vous recevrez un courriel de requête de confirmation, cela empêche que d'autres personnes vous abonne impunément. " ** Affects: mailman Importance: Undecided Status: New ** Tags: french translation -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1331194 Title: French translation on main Mailman page To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1331194/+subscriptions

3 5

[Bug 1318025] [NEW] The DMARC mitigatation actions do not include a Reply-To: header in rare cases.
by Mark Sapiro 29 Jan '15

29 Jan '15

Public bug reported: If the incoming message contains no From: header or it's From: header can't be parsed into a display name and email address, the DMARC mitigation actions that try to put the From: address in Reply-To: fail to do so. In these cases and also in the non-compliant case where there are multiple From: addresses, just take the sender address from Mailman's get_sender() message method and use that in liu of the From address. ** Affects: mailman Importance: Low 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/1318025 Title: The DMARC mitigatation actions do not include a Reply-To: header in rare cases. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1318025/+subscriptions

2 4

[Bug 1327404] [NEW] Mailman's log files are world readable
by Mark Sapiro 29 Jan '15

29 Jan '15

Public bug reported: Mailman creates log files with permissions -rw-rw-r--. This allows possibly untrusted local users to read those logs and possibly find sensitive information therein. The same is true of lists/LISTNAME/request.pck files. ** 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/1327404 Title: Mailman's log files are world readable To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1327404/+subscriptions

2 4

[Bug 1334450] [NEW] If a message is held for header_filter_rules and subsequently approved, dmarc_moderation_action is bypassed.
by Mark Sapiro 29 Jan '15

29 Jan '15

Public bug reported: Messages which are pre-approved with an Approved: header or held by a pipeline handler earlier than Moderate and accepted by a moderator will bypass the dmarc_moderation_action test and applicable action. Clearly Munge From or Wrap Message actions should be done in this case. What to do in a case of a dmarc_moderation_action of Reject or Discard is not so clear, but either they should be honored or at least the Wrap Message action should be applied. Given that a moderator likely approved the message based on content without considering DMARC, probably Reject and Discard actions should be honored. ** Affects: mailman Importance: High 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/1334450 Title: If a message is held for header_filter_rules and subsequently approved, dmarc_moderation_action is bypassed. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1334450/+subscriptions

3 5

[Bug 1324541] [NEW] If the dnspython package is not available and dmarc_moderation_action is not accept, nothing is logged.
by Mark Sapiro 29 Jan '15

29 Jan '15

Public bug reported: dmarc_moderation_action other than accept relies on DNS lookups via the dnspython package to check DMARC policy of the From: domain, but if the package is not available, the check silently returns no DMARC policy. It should at least log the fact that the package isn't there. ** Affects: mailman Importance: High 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/1324541 Title: If the dnspython package is not available and dmarc_moderation_action is not accept, nothing is logged. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1324541/+subscriptions

2 3