From mark at msapiro.net Sat May 1 02:26:34 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 01 May 2010 00:26:34 -0000 Subject: [Bug 558204] Re: allow specifying another list in accept_these_nonmembers References: <20100408090748.1687.80336.launchpad@loganberry.canonical.com> Message-ID: <20100501002634.25029.18631.malone@wampee.canonical.com> The attached list inclusion patch is a one-line change to the original patch plus expansion of some tabs. The change replaces "if mother.members.has_key(sender)" with "if mother.isMember(sender)". Using the isMember() method will work with all MemberAdaptors, not just OldStyleMemberships.py. Also, members.has_key(sender) only tests regular members, not digest members. This corrected patch is provided for those still using Mailman 2.1.9 or older that want this functionality. The patch is not required for Mailman 2.1.10 and newer. ** Patch added: "List Inclusion patch with correction." http://launchpadlibrarian.net/46775788/listinclusion.patch -- allow specifying another list in accept_these_nonmembers https://bugs.launchpad.net/bugs/558204 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From ovadbar at gmail.com Wed May 5 23:04:03 2010 From: ovadbar at gmail.com (ovadbar) Date: Wed, 05 May 2010 21:04:03 -0000 Subject: [Bug 328353] Re: decoding unicode (still) not supported bug References: <20090212023754.4890.76025.malonedeb@potassium.ubuntu.com> Message-ID: <20100505210404.14310.30276.malone@palladium.canonical.com> I tried to add both patches and the same error shows up. I also don't want to use a different version of python because of another error that shows up. Before I ran the fix I was not able to run bin/arch now I am. My current solution is to run a cronjob to run bin/arch since it seemed to be a partial solution. -- decoding unicode (still) not supported bug https://bugs.launchpad.net/bugs/328353 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Thu May 6 03:42:32 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 06 May 2010 01:42:32 -0000 Subject: [Bug 328353] Re: decoding unicode (still) not supported bug References: <20090212023754.4890.76025.malonedeb@potassium.ubuntu.com> Message-ID: <20100506014232.21146.84067.malone@wampee.canonical.com> ovadbar: I assume "both patches" are those in comments #10 and #11. Did you restart Mailman after applying the patches? If so, please post one of the tracebacks from the archiving error. Also, please post the output from an interactive bin/withlist session similar to the following: [msapiro at msapiro ...f/test-mailman]$ bin/withlist -i No list name supplied. Python 2.6.5 (r265:79063, May 1 2010, 12:04:38) [GCC 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)] on cygwin Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> import email >>> email.__version__ '4.0.1' >>> -- decoding unicode (still) not supported bug https://bugs.launchpad.net/bugs/328353 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 May 7 00:26:29 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 06 May 2010 22:26:29 -0000 Subject: [Bug 576675] [NEW] Content filtering fails to collapse alternatives. References: <20100506222630.1851.73554.malonedeb@gandwana.canonical.com> Message-ID: <20100506222630.1851.73554.malonedeb@gandwana.canonical.com> 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. From ovadbar at gmail.com Fri May 7 16:15:40 2010 From: ovadbar at gmail.com (ovadbar) Date: Fri, 07 May 2010 14:15:40 -0000 Subject: [Bug 328353] Re: decoding unicode (still) not supported bug References: <20090212023754.4890.76025.malonedeb@potassium.ubuntu.com> Message-ID: <20100507141540.1918.5231.malone@gandwana.canonical.com> Thanks I had not restarted mailman. Both patches were the ones in 10 and 11. What's strange is that the owner of the mailman qrunner process was not mailman me or root. In fact it was a person that had been added to the project recently in order to use samba but doesn't use uniix. Thank you for the help. -- decoding unicode (still) not supported bug https://bugs.launchpad.net/bugs/328353 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 May 7 17:03:25 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 07 May 2010 15:03:25 -0000 Subject: [Bug 576675] Re: Content filtering fails to collapse alternatives. References: <20100506222630.1851.73554.malonedeb@gandwana.canonical.com> Message-ID: <20100507150326.14362.33263.launchpad@palladium.canonical.com> ** Changed in: mailman Status: In Progress => Fix Committed ** Branch linked: lp:mailman/2.1 -- 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. From mark at msapiro.net Fri May 7 17:02:10 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 07 May 2010 15:02:10 -0000 Subject: [Bug 328353] Re: decoding unicode (still) not supported bug References: <20090212023754.4890.76025.malonedeb@potassium.ubuntu.com> Message-ID: <20100507150210.21146.45359.malone@wampee.canonical.com> If 'mailmanctl start' is run as root as it should be, the owner of all the processes should be the mailman user, so yes, that's strange. -- decoding unicode (still) not supported bug https://bugs.launchpad.net/bugs/328353 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Mon May 10 22:11:22 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 10 May 2010 20:11:22 -0000 Subject: [Bug 266043] Re: virtual-mailman is missing domain entry References: <20080905192821.27052.26521.launchpad@forster.canonical.com> Message-ID: <20100510201123.9360.65178.malone@soybean.canonical.com> Current Postfix allows specification of the domain in virtual_alias_domains so the "domain anything" line is not needed in virtual-mailman. ** Changed in: mailman Status: New => Won't Fix -- virtual-mailman is missing domain entry https://bugs.launchpad.net/bugs/266043 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Mon May 10 22:44:15 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 10 May 2010 20:44:15 -0000 Subject: [Bug 328907] Re: Simple patch to make genaliases explicitly vmap to @localhost References: <20090213033246.20561.4110.malonedeb@palladium.canonical.com> Message-ID: <20100510204415.21203.14747.malone@wampee.canonical.com> This will be in 2.1.14, but there will be an mm_cfg.py entry to specify the local host if any. ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: None => 2.1.14 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- Simple patch to make genaliases explicitly vmap to @localhost https://bugs.launchpad.net/bugs/328907 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Mon May 10 23:51:52 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 10 May 2010 21:51:52 -0000 Subject: [Bug 328907] Re: Simple patch to make genaliases explicitly vmap to @localhost References: <20090213033246.20561.4110.malonedeb@palladium.canonical.com> Message-ID: <20100510215153.9412.64085.launchpad@soybean.canonical.com> ** Branch linked: lp:mailman/2.1 ** Changed in: mailman Status: In Progress => Fix Committed -- Simple patch to make genaliases explicitly vmap to @localhost https://bugs.launchpad.net/bugs/328907 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From josh at joshtriplett.org Thu May 13 02:21:05 2010 From: josh at joshtriplett.org (Josh Triplett) Date: Thu, 13 May 2010 00:21:05 -0000 Subject: [Bug 571904] Re: Aggregated list with subscribers from other lists References: <20100429212144.25029.95715.malonedeb@wampee.canonical.com> Message-ID: <20100513002105.17516.35438.malone@soybean.canonical.com> Closing this bug per comment 1 pointing at the existing implementation of this feature. ** Changed in: mailman Status: New => Fix Released -- Aggregated list with subscribers from other lists https://bugs.launchpad.net/bugs/571904 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From jakobunt at gmail.com Mon May 17 01:28:28 2010 From: jakobunt at gmail.com (Jakob Unterwurzacher) Date: Sun, 16 May 2010 23:28:28 -0000 Subject: [Bug 581518] [NEW] list_members --fullnames kills umlauts in names References: <20100516232828.31203.35488.malonedeb@wampee.canonical.com> Message-ID: <20100516232828.31203.35488.malonedeb@wampee.canonical.com> Public bug reported: Running ???list_members --fullnames testlist should output this, as seen correctly in the web interface: ???J?rgen <... at gmx.de> Actually, it outputs: ???J?rgen <... at gmx.de> with the umlaut ? replaced by a question mark. ** Affects: mailman Importance: Undecided Status: New ** Description changed: Running - list_members --fullnames testlist + ???list_members --fullnames testlist should output this, as seen correctly in the web interface: - J?rgen <... at gmx.de> + ???J?rgen <... at gmx.de> Actually, it outputs: - J?rgen <... at gmx.de> - with the umlaut ? removed. + ???J?rgen <... at gmx.de> + with the umlaut ? replaced by a question mark. -- list_members --fullnames kills umlauts in names https://bugs.launchpad.net/bugs/581518 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Mon May 17 02:04:09 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 17 May 2010 00:04:09 -0000 Subject: [Bug 581518] Re: list_members --fullnames kills umlauts in names References: <20100516232828.31203.35488.malonedeb@wampee.canonical.com> Message-ID: <20100517000409.31255.19914.launchpad@wampee.canonical.com> ** Changed in: mailman Status: New => Invalid -- list_members --fullnames kills umlauts in names https://bugs.launchpad.net/bugs/581518 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Mon May 17 02:32:48 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 17 May 2010 00:32:48 -0000 Subject: [Bug 581518] Re: list_members --fullnames kills umlauts in names References: <20100516232828.31203.35488.malonedeb@wampee.canonical.com> Message-ID: <20100517003248.15293.29295.malone@gandwana.canonical.com> This is not a bug in list_members. list_members encodes the full names for output in the default encoding of the Python installation. If you want this to be, e.g., iso-8859-1 or utf-8 as opposed to ascii which is the normal Python default, you have to add, e.g., sys.setdefaultencoding('utf-8') to a sitecustomize.py module. See . For example, if you want utf-8 encoding as the Python default, you could create /usr/lib/pythonv.v/site-packages/sitecustomize.py containing the two lines: import sys sys.setdefaultencoding('utf-8') -- list_members --fullnames kills umlauts in names https://bugs.launchpad.net/bugs/581518 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From jakobunt at gmail.com Mon May 17 13:03:08 2010 From: jakobunt at gmail.com (Jakob Unterwurzacher) Date: Mon, 17 May 2010 11:03:08 -0000 Subject: [Bug 581518] Re: list_members --fullnames kills umlauts in names References: <20100516232828.31203.35488.malonedeb@wampee.canonical.com> Message-ID: <20100517110308.31255.22842.malone@wampee.canonical.com> Thanks, that worked! Nice-to-have would be if list_members used the LANG setting (f.x. I have LANG=de_DE.UTF-8) to determine the output encoding to use. -- list_members --fullnames kills umlauts in names https://bugs.launchpad.net/bugs/581518 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Mon May 17 15:41:03 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 17 May 2010 13:41:03 -0000 Subject: [Bug 581518] Re: list_members --fullnames kills umlauts in names References: <20100516232828.31203.35488.malonedeb@wampee.canonical.com> Message-ID: <20100517134103.17464.51342.malone@soybean.canonical.com> This is really still a Python request, but I changed it back to New->Wishlist per comment #2. ** Changed in: mailman Importance: Undecided => Wishlist ** Changed in: mailman Status: Invalid => New -- list_members --fullnames kills umlauts in names https://bugs.launchpad.net/bugs/581518 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Tue May 18 23:04:46 2010 From: barry at canonical.com (Barry Warsaw) Date: Tue, 18 May 2010 21:04:46 -0000 Subject: [Bug 582524] [NEW] Use IMAP CREATE to add folders to IMAP archiver on list creation References: <20100518210446.13964.80423.malonedeb@palladium.canonical.com> Message-ID: <20100518210446.13964.80423.malonedeb@palladium.canonical.com> Public bug reported: For every mailing list we expose to IMAP, we'll want to create a few folders. Hook in the IMAP folder creation to the list creation hooks. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a6 -- Use IMAP CREATE to add folders to IMAP archiver on list creation https://bugs.launchpad.net/bugs/582524 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Tue May 18 23:01:31 2010 From: barry at canonical.com (Barry Warsaw) Date: Tue, 18 May 2010 21:01:31 -0000 Subject: [Bug 582522] [NEW] Implement archive delivery via LMTP References: <20100518210131.22841.77980.malonedeb@gandwana.canonical.com> Message-ID: <20100518210131.22841.77980.malonedeb@gandwana.canonical.com> Public bug reported: Dovecot beta supports delivery via LMTP. Mailman 3 should implement a generic archive delivery implementation that delivers via LMTP. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Milestone: None => 3.0.0a6 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Importance: Undecided => High -- Implement archive delivery via LMTP https://bugs.launchpad.net/bugs/582522 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Tue May 18 23:06:40 2010 From: barry at canonical.com (Barry Warsaw) Date: Tue, 18 May 2010 21:06:40 -0000 Subject: [Bug 582525] [NEW] Add sieve rules to route messages properly to IMAP server References: <20100518210640.13964.16830.malonedeb@palladium.canonical.com> Message-ID: <20100518210640.13964.16830.malonedeb@palladium.canonical.com> Public bug reported: When a message from Mailman gets routed to an IMAP server (e.g. for archiving or administration), we need a sieve rule to do proper routing. E.g. for dovecot. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a6 -- Add sieve rules to route messages properly to IMAP server https://bugs.launchpad.net/bugs/582525 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mats.ahlgren+launchpad at gmail.com Wed May 19 07:43:53 2010 From: mats.ahlgren+launchpad at gmail.com (Mats Ahlgren) Date: Wed, 19 May 2010 05:43:53 -0000 Subject: [Bug 266821] Re: privacy hole in password reminder References: <20080905194256.1806.8914.launchpad@forster.canonical.com> Message-ID: <20100519054353.32316.28080.malone@wampee.canonical.com> The following major security issues also exist: - If an email account is compromised, an attacker (or even an automated virus) can easily gather all passwords. This would *NOT* happen if no reminders were sent, nor would it happen if the classic "answer the security questions to receive a password reset form" strategy were used. - Additionally, once the attacker has the dozens of passwords one might use for various mailman lists, the attack can attempt to use those passwords on other websites or computer systems (e.g. SSH) in automated attacks. The most basic attack would merely use the password, but more sophisticated attacks can use the passwords as seeds in an automated cracker. > Mark Sapiro: "Are you aware of an attack that would enable this?" - As the original poster wrote: the password reminders are in plaintext. As far as I know, aren't all email messages sent in plaintext that thus absolutely trivial to eavesdrop on? All the attack would need is a compromised relay on the internet, which I hear is getting more common these days. Just run one of the many network-traffic-monitoring programs and listen for the string "password". -- privacy hole in password reminder https://bugs.launchpad.net/bugs/266821 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Wed May 19 15:18:10 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 19 May 2010 13:18:10 -0000 Subject: [Bug 266821] Re: privacy hole in password reminder References: <20080905194256.1806.8914.launchpad@forster.canonical.com> Message-ID: <20100519131810.31731.14579.malone@wampee.canonical.com> We know that plain text emailed passwords are a bad idea. This will be fixed in MM 3. For MM 2.1, as a list member, you can turn off the periodic reminder for any list of which you are a member. As a list owner, you can turn off all periodic reminders from your lists. As a site admin, you can turn off all periodic reminders from the site. That leaves only the "request an immediate reminder and intercept the email" attack as a vulnerability. The list subscribe form says: You may enter a privacy password below. This provides only mild security, but should prevent others from messing with your subscription. *Do not use a valuable password* as it will occasionally be emailed back to you in cleartext. which implies that such a password, even if it is not an autogenerated one, is less likely to work in other contexts. ** Changed in: mailman Importance: Medium => High ** Changed in: mailman Status: New => Triaged ** Changed in: mailman Milestone: None => mailman-2.2-3.0 -- privacy hole in password reminder https://bugs.launchpad.net/bugs/266821 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From abe at deuxchevaux.org Wed May 19 18:04:37 2010 From: abe at deuxchevaux.org (Axel Beckert) Date: Wed, 19 May 2010 16:04:37 -0000 Subject: [Bug 582911] [NEW] Umbrella flag should be per subscriber not per list References: <20100519160437.15293.39262.malonedeb@gandwana.canonical.com> Message-ID: <20100519160437.15293.39262.malonedeb@gandwana.canonical.com> Public bug reported: Currently a list can be either an umbrella list or not, but a list which has normal and other lists as subscriber is currently not possible or an administrative problem. IMHO making the umbrella flag (as previously the moderated flag) per subscribe instead of per list, this would allow to make lists with mixed types of subscribers. This would probably also make the following helpful automatisms possible or at least easier: Mailman sould recognize mailing lists on the same server when they are subscribed to another list and set the umbrella flag for that subscriber automatically. Mailman should automatically add the umbrella list's aliases as well as non-members which are allowed to post to the appropriate fields of the subscriber-lists on the same server. I suspect at least 90% of all subscriber-lists are configured that way. ** Affects: mailman Importance: Undecided Status: New ** Tags: umbrella -- Umbrella flag should be per subscriber not per list https://bugs.launchpad.net/bugs/582911 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From abe at deuxchevaux.org Wed May 19 18:13:57 2010 From: abe at deuxchevaux.org (Axel Beckert) Date: Wed, 19 May 2010 16:13:57 -0000 Subject: [Bug 582911] Re: Umbrella flag should be per subscriber not per list References: <20100519160437.15293.39262.malonedeb@gandwana.canonical.com> Message-ID: <20100519161358.29377.65213.launchpad@soybean.canonical.com> ** Description changed: Currently a list can be either an umbrella list or not, but a list which has normal and other lists as subscriber is currently not possible or an administrative problem. IMHO making the umbrella flag (as previously the moderated flag) per - subscribe instead of per list, this would allow to make lists with mixed - types of subscribers. + subscriber instead of per list, this would allow to make lists with + mixed types of subscribers. This would probably also make the following helpful automatisms possible or at least easier: Mailman sould recognize mailing lists on the same server when they are subscribed to another list and set the umbrella flag for that subscriber automatically. Mailman should automatically add the umbrella list's aliases as well as non-members which are allowed to post to the appropriate fields of the subscriber-lists on the same server. I suspect at least 90% of all subscriber-lists are configured that way. -- Umbrella flag should be per subscriber not per list https://bugs.launchpad.net/bugs/582911 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From lists at amk.ca Fri May 21 16:28:18 2010 From: lists at amk.ca (A.M. Kuchling) Date: Fri, 21 May 2010 14:28:18 -0000 Subject: [Bug 266375] Re: mailman corrupts RFC2047-encoded headers References: <20080905193128.27052.65988.launchpad@forster.canonical.com> Message-ID: <20100521142818.29486.94243.malone@soybean.canonical.com> One possible fix is to parse the subject header's content by turning it into a Header object. This seems to work for simply sending a message through, but I don't know if every use of the Subject header in Mailman works correctly if the value is a Header object instead of a string. It does seem like a bug in the underlying email package, though; I've filed http://bugs.python.org/issue8769 in the Python bug tracker. ** Bug watch added: Python Roundup #8769 http://bugs.python.org/issue8769 ** Attachment added: "Possible fix" http://launchpadlibrarian.net/48871021/rfc2047-patch.txt -- mailman corrupts RFC2047-encoded headers https://bugs.launchpad.net/bugs/266375 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Tue May 25 20:32:10 2010 From: barry at canonical.com (Barry Warsaw) Date: Tue, 25 May 2010 18:32:10 -0000 Subject: [Bug 585512] [NEW] Set up virtualenv (and ditch buildout?) References: <20100525183210.5848.24765.malonedeb@palladium.canonical.com> Message-ID: <20100525183210.5848.24765.malonedeb@palladium.canonical.com> Public bug reported: Mailman 3 development needs more isolation from system Python. Two recent reports are semi-related: * On Ubuntu systems that have been upgraded from Karmic to Lucid, there is a bug in python-setuptools that causes buildout to fail with cryptic error messages. See bug 576434 and bug 585188 for related failures (though not in Mailman). * Strange import conflicts with system installed Mailman that are hard to debug. This is related to mailman.testing.i18n giving TypeErrors on incorrect number of arguments when initializing flufl.i18n. I think the fix is to make sure the build works with virtualenv. Then we have to decide whether it's still worth keeping the buildout infrastructure for testing purposes. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Affects: mailman/3.0 Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a6 ** Also affects: mailman/3.0 Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed -- Set up virtualenv (and ditch buildout?) https://bugs.launchpad.net/bugs/585512 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 May 30 23:06:05 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 30 May 2010 21:06:05 -0000 Subject: [Bug 587657] [NEW] bin/genaliases throws TypeError if MTA = None. References: <20100530210605.2136.60657.malonedeb@wampee.canonical.com> Message-ID: <20100530210605.2136.60657.malonedeb@wampee.canonical.com> Public bug reported: if MTA = None in mm_cfg.py, genaliases can't do anything, but it should be more graceful than throwing TypeError: cannot concatenate 'str' and 'NoneType' objects. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: Fix Committed ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.14 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- bin/genaliases throws TypeError if MTA = None. https://bugs.launchpad.net/bugs/587657 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 May 30 23:17:38 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 30 May 2010 21:17:38 -0000 Subject: [Bug 587657] Re: bin/genaliases throws TypeError if MTA = None. References: <20100530210605.2136.60657.malonedeb@wampee.canonical.com> Message-ID: <20100530211739.2282.56972.launchpad@wampee.canonical.com> ** Branch linked: lp:mailman/2.1 -- bin/genaliases throws TypeError if MTA = None. https://bugs.launchpad.net/bugs/587657 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.