From mark at msapiro.net Sun Jul 1 04:39:07 2012 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 01 Jul 2012 02:39:07 -0000 Subject: [Bug 1019660] Re: Include references in replies to requests. References: <20120630205633.19504.65414.malonedeb@soybean.canonical.com> Message-ID: <20120701023908.5448.6854.launchpad@wampee.canonical.com> ** Changed in: mailman Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1019660 Title: Include references in replies to requests. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1019660/+subscriptions From ubuntu at fachschaft.physik.uni-bielefeld.de Mon Jul 2 08:56:02 2012 From: ubuntu at fachschaft.physik.uni-bielefeld.de (fs-physik-bielefeld) Date: Mon, 02 Jul 2012 06:56:02 -0000 Subject: [Bug 558106] Re: A MemberAdaptor for LDAP-based membership References: <20100408090607.1687.22727.launchpad@loganberry.canonical.com> Message-ID: <20120702065602.18174.15282.malone@soybean.canonical.com> So I used that adapter, but I had the problem that the mail server was more important to be accessible without interruption that the ldap server. So I tried replicating the ldap server to the mail server, but since I did not want the password hashes on the mail server, I tried a partial replication which somehow did not always work. Although the ldap-server for the adapter was ldapi:///, it sometimes said 'connection refused' and shunted my mails. I finally changed LdapMemberships.py to FileMemberships.py, which is minimal and just reads the list entries from files that are created with python's pickle module. The files, on the other hand, are populated by a cron job which contacts the original LDAP-Server. The disadvantage is that changes to the LDAP entries get realized with a delay of one hour at most, but the advantage is that if there is some problem with the LDAP server, the files are just left as they are and the mails get delivered. For my case this is more important. For the implementation of FileMemberships, I was guided by this module, so thanks for that. If someone else is interested, my version is attached. ** Attachment added: "ldapsync.tar.gz" https://bugs.launchpad.net/mailman/+bug/558106/+attachment/3210464/+files/ldapsync.tar.gz -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558106 Title: A MemberAdaptor for LDAP-based membership To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558106/+subscriptions From 1015758 at bugs.launchpad.net Tue Jul 3 16:43:49 2012 From: 1015758 at bugs.launchpad.net (Barry Warsaw) Date: Tue, 03 Jul 2012 14:43:49 -0000 Subject: [Bug 1015758] Re: Deprecate in favor of passlib References: <20120620190803.30614.54376.malonedeb@chaenomeles.canonical.com> Message-ID: <20120703144350.28773.19018.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1015758 Title: Deprecate in favor of passlib To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.password/+bug/1015758/+subscriptions From dukrat at mit.edu Tue Jul 3 20:18:18 2012 From: dukrat at mit.edu (Robert Arlt Jr.) Date: Tue, 03 Jul 2012 18:18:18 -0000 Subject: [Bug 1020683] [NEW] Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). References: <20120703181818.4927.56021.malonedeb@soybean.canonical.com> Message-ID: <20120703181818.4927.56021.malonedeb@soybean.canonical.com> Public bug reported: It would be very useful if sibling lists could be nested. The same goes for non-member lists. It would also be nice if non-member lists could also include the members of sibling lists. ** 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/1020683 Title: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions From mark at msapiro.net Wed Jul 4 01:22:31 2012 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 03 Jul 2012 23:22:31 -0000 Subject: [Bug 1020683] Re: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). References: <20120703181818.4927.56021.malonedeb@soybean.canonical.com> Message-ID: <20120703232232.29508.32121.malone@chaenomeles.canonical.com> I don't understand what you mean by "It would also be nice if non-member lists could also include the members of sibling lists". You can already put any @listname in *_these_nonmembers to include the members of listname. Is that what you mean? Or do you mean something else such as accept_these_nonmembers should automatically and implicitly include the members of any regular_include_lists? ** Changed in: mailman Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1020683 Title: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions From dukrat at mit.edu Thu Jul 5 15:24:15 2012 From: dukrat at mit.edu (Robert Arlt Jr.) Date: Thu, 05 Jul 2012 13:24:15 -0000 Subject: [Bug 1020683] Re: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). References: <20120703181818.4927.56021.malonedeb@soybean.canonical.com> Message-ID: <20120705132415.5607.54813.malone@wampee.canonical.com> Automatically and implicitly would seem to be a little strong. What I'm asking for is an option that allows regular_include_lists and/or lists that are members of lists to have their members count for *_these_nonmembers and in a recursive manner. For example: listA: members: jack at ... accept_these_nonmembers: @listB listB: members: jill at ... regular_include_lists or accept_these_nonmembers or members: @listC with the result that listC can send to listA unmoderated. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1020683 Title: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions From 1021364 at bugs.launchpad.net Thu Jul 5 17:51:48 2012 From: 1021364 at bugs.launchpad.net (Florian Fuchs) Date: Thu, 05 Jul 2012 15:51:48 -0000 Subject: [Bug 1021364] [NEW] Catch httplib2 error if REST API is not available References: <20120705155149.5384.41016.malonedeb@wampee.canonical.com> Message-ID: <20120705155149.5384.41016.malonedeb@wampee.canonical.com> Public bug reported: httplib2 (used in mailman.client) throws "[Errno 111] Connection refused" if the core api isn't available. This should be turned into a nice error page with a meaningful description (possibly depending on the visiting user's role - details for admins and a more vague error msg for everyone else). ** Affects: mailman.client Importance: Undecided Status: New ** Affects: postorius Importance: Medium Status: Confirmed ** Tags: api ** Description changed: - httplib2 throws "[Errno 111] Connection refused" if the core api isn't - available. + httplib2 (used in mailman.client) throws "[Errno 111] Connection + refused" if the core api isn't available. This should be turned into a nice error page with a meaningful description (possibly depending on the visiting user's role - details for admins and a more vague error msg for everyone else). ** Also affects: mailman.client Importance: Undecided Status: New ** Changed in: postorius Milestone: None => 1.0.0a2 -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1021364 Title: Catch httplib2 error if REST API is not available To manage notifications about this bug go to: https://bugs.launchpad.net/mailman.client/+bug/1021364/+subscriptions From mark at msapiro.net Thu Jul 5 19:29:06 2012 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 05 Jul 2012 17:29:06 -0000 Subject: [Bug 1020683] Re: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). References: <20120703181818.4927.56021.malonedeb@soybean.canonical.com> Message-ID: <20120705172906.21278.55416.malone@chaenomeles.canonical.com> I understand the recursive request. Leaving that aside for a moment, it seems you already have the rest of your request. Your option is to just put @listname in accept_these_nonmembers for every list in regular_include_lists. So it seems that all you are really requesting is that @listname lists in *_these_nonmembers be processed recursively. Is that correct or am I missing something? -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1020683 Title: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions From dukrat at mit.edu Thu Jul 5 19:53:13 2012 From: dukrat at mit.edu (Robert Arlt Jr.) Date: Thu, 05 Jul 2012 17:53:13 -0000 Subject: [Bug 1020683] Re: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). References: <20120703181818.4927.56021.malonedeb@soybean.canonical.com> Message-ID: <20120705175313.20355.63604.malone@chaenomeles.canonical.com> I think making it recursive would be sufficient. However, it isn't really that I want *_these_nonmembers to be recursive to *_these_nonmembers as I may want different sets of lists to be able to send to a particular list. I guess it might be better if I just explained what I really want, which is the ability to add @listC to the members of listB such that listA, which has accept_these_nonmembers set to @listB, can be sent to unmoderated by members of listC. In otherwords making the @listname format usable as a list member such that *_these_nonmembers and sibling lists can transverse them. Neither of the solutions you have talked about are exactly that, but could be used instead to obtain the same goal. Basically what I am trying to do is minimize the number of lists that would have to be changed if a new lists is created that should have rights to send to a number of lists. Perhaps I should have split this into two feature requests, the recursion request is by far more of a useful feature. The other feature would add on only a minimal amount of capability. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1020683 Title: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions From mark at msapiro.net Thu Jul 5 20:57:47 2012 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 05 Jul 2012 18:57:47 -0000 Subject: [Bug 1020683] Re: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). References: <20120703181818.4927.56021.malonedeb@soybean.canonical.com> Message-ID: <20120705185747.12971.25202.malone@gac.canonical.com> "I guess it might be better if I just explained what I really want, which is the ability to add @listC to the members of listB such that listA, which has accept_these_nonmembers set to @listB, can be sent to unmoderated by members of listC." And wouldn't this be the case if @listC was in listB's accept_these_nonmembers and @listB was in listA's accept_these_nonmembers and accept_these_nonmembers were processed recursively? As far as allowing members of a regular_include_lists list to post is concerned, this is already easily accomplished by simply adding the @LISTNAME to accept_these_nonmembers at the same time as you add the list posting address to regular_include_lists. So it still seems to me that you can easily accomplish everything you ask if *these_nonmembers were processed recursively. If this is not the case, please give an example of what would not be configurable in this way. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1020683 Title: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions From richard at nfsnet.org Thu Jul 5 20:58:11 2012 From: richard at nfsnet.org (Richard Wackerbarth) Date: Thu, 05 Jul 2012 18:58:11 -0000 Subject: [Bug 1020683] Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). References: <20120703181818.4927.56021.malonedeb@soybean.canonical.com> <20120705175313.20355.63604.malone@chaenomeles.canonical.com> Message-ID: <865949D8-F83F-4FB2-B7DA-363560456FC6@NFSNet.org> Robert, Although I recognize your goal, it isn't as easy as simply providing transitive membership. First, I presume that you are willing to restrict yourself to the case where lists listA, listB, and listC are served by the same instance of MM. On the distribution side, that restriction certainly is not necessary for list inclusion, but, in general, there is no mechanism for listA to learn the members of listC unless they are served by a common server instance. Even so, the issue is whether, or not, everyone who receives listB should be allowed to submit to listA (without moderation). Or perhaps you would only want those who can make unmoderated submissions to listB to have that transitive permission. I can visualize both use cases. Richard On Jul 5, 2012, at 12:53 PM, Robert Arlt Jr. wrote: > I think making it recursive would be sufficient. > > However, it isn't really that I want *_these_nonmembers to be recursive > to *_these_nonmembers as I may want different sets of lists to be able > to send to a particular list. I guess it might be better if I just > explained what I really want, which is the ability to add @listC to the > members of listB such that listA, which has accept_these_nonmembers set > to @listB, can be sent to unmoderated by members of listC. In > otherwords making the @listname format usable as a list member such that > *_these_nonmembers and sibling lists can transverse them. > > Neither of the solutions you have talked about are exactly that, but > could be used instead to obtain the same goal. Basically what I am > trying to do is minimize the number of lists that would have to be > changed if a new lists is created that should have rights to send to a > number of lists. > > Perhaps I should have split this into two feature requests, the > recursion request is by far more of a useful feature. The other feature > would add on only a minimal amount of capability. > > -- > You received this bug notification because you are a member of Mailman > Coders, which is subscribed to GNU Mailman. > https://bugs.launchpad.net/bugs/1020683 > > Title: > Feature Request: Make regular_*_lists and *_these_nonmembers recursive > (and aware of each other). > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions > _______________________________________________ > Mailman-coders mailing list > Mailman-coders at python.org > http://mail.python.org/mailman/listinfo/mailman-coders -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1020683 Title: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions From 1020683 at bugs.launchpad.net Thu Jul 5 21:22:39 2012 From: 1020683 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 05 Jul 2012 19:22:39 -0000 Subject: [Mailman-Developers] [Bug 1020683] Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). References: <20120703181818.4927.56021.malonedeb@soybean.canonical.com> <20120705175313.20355.63604.malone@chaenomeles.canonical.com> <865949D8-F83F-4FB2-B7DA-363560456FC6@NFSNet.org> Message-ID: <20120705152239.2d6180ca@limelight.wooz.org> On Jul 05, 2012, at 01:58 PM, Richard Wackerbarth wrote: >First, I presume that you are willing to restrict yourself to the case where >lists listA, listB, and listC are served by the same instance of MM. On the >distribution side, that restriction certainly is not necessary for list >inclusion, but, in general, there is no mechanism for listA to learn the >members of listC unless they are served by a common server instance. > >Even so, the issue is whether, or not, everyone who receives listB should be >allowed to submit to listA (without moderation). Or perhaps you would only >want those who can make unmoderated submissions to listB to have that >transitive permission. I'll note that with Mailman 3 and clever implementation of the IRoster interface, various riffs on this should be doable. Most implementations of IRoster are not physical objects persisted in the database, but instead "virtual" objects such as queries. There's no reason I can think of that an IRoster implementation couldn't perform cross-list queries, or even for that matter cross-server queries, assuming the necessary communication channels were available. I've not actually tried to implement anything like this, but I can somewhat visualize how this would work. I invite you to experiment with this. Cheers, -Barry -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1020683 Title: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions From dukrat at mit.edu Thu Jul 5 21:48:22 2012 From: dukrat at mit.edu (Robert Arlt Jr.) Date: Thu, 05 Jul 2012 19:48:22 -0000 Subject: [Bug 1020683] Re: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). References: <20120703181818.4927.56021.malonedeb@soybean.canonical.com> Message-ID: <20120705194822.29278.93580.malone@soybean.canonical.com> "And wouldn't this be the case if @listC was in listB's accept_these_nonmembers and @listB was in listA's accept_these_nonmembers and accept_these_nonmembers were processed recursively?" Yes, but what if I only wanted listC to be able to send to listA and not listB (I personally don't want to do this, but I could see someone else wanting to). "served by a common server instance" Yes, that would be an expected requirement for this feature to work. "I can visualize both use cases." I can as well. In my view of the issue I believe that allowing everyone on listB to submit is the better option as I can easily make a list composed of those allowed to send unmoderated to listB, call it listB2 and add listB2 to listB then use listB2 as the list allowed to send to listA (all of this assuming recursion is implemented). "with Mailman 3... various riffs on this should be doable" Thanks for letting me know, I will look into that. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1020683 Title: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions From mark at msapiro.net Thu Jul 5 22:29:48 2012 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 05 Jul 2012 20:29:48 -0000 Subject: [Bug 1020683] Re: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). References: <20120703181818.4927.56021.malonedeb@soybean.canonical.com> Message-ID: <20120705202948.29164.55326.malone@soybean.canonical.com> I wrote: "And wouldn't this be the case if @listC was in listB's accept_these_nonmembers and @listB was in listA's accept_these_nonmembers and accept_these_nonmembers were processed recursively?" Robert replied: "Yes, but what if I only wanted listC to be able to send to listA and not listB (I personally don't want to do this, but I could see someone else wanting to)." Well, if I wanted to do that, I would just put @listC in listA's accept_these_nonmembers, but I suppose you envision a case where listB and ListC are siblings and listB is in listA's accept_these_nonmembers and then listC members can post to listA because some "include siblings members as posters (recursively)" option is selected for listA, but they can't post to listB because that "include siblings" option is not selected for listB. This seems so complicated and error prone that I don't think it could even be explained in a way that people could use it, but perhaps you can see some more straightforward way of setting this up. I also wonder if listC members can't post to listB, how does referencing listB (recursively) from listA give listC's members any posting rights on listA. In any case, I don't see it ever being implemented in Mailman 2.1 which is virtually at the end of it's development life anyway. Perhaps something will be done for Mailman 3. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1020683 Title: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions From richard at nfsnet.org Thu Jul 5 22:33:29 2012 From: richard at nfsnet.org (Richard Wackerbarth) Date: Thu, 05 Jul 2012 20:33:29 -0000 Subject: [Bug 1020683] Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). References: <20120703181818.4927.56021.malonedeb@soybean.canonical.com> <20120705194822.29278.93580.malone@soybean.canonical.com> Message-ID: On Jul 5, 2012, at 2:48 PM, Robert Arlt Jr. wrote: > I can as well. In my view of the issue I believe that allowing everyone > on listB to submit is the better option as I can easily make a list > composed of those allowed to send unmoderated to listB, call it listB2 > and add listB2 to listB then use listB2 as the list allowed to send to > listA (all of this assuming recursion is implemented). But that would be confusing to the members of listB. They would have to realize that they are not really a member of listB, but that they are actually a member of listB2. So, if you are going to do that, and perhaps for any inclusion that is transparent on message delivery, an attempt to change delivery preferences on listA should take the user to the listB2 preferences. However, if the delivery of listA is done by publishing a copy of the message on listB, then, for the purpose of preferences, the listB user should not be considered a member of listA. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1020683 Title: Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other). To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions From dukrat at mit.edu Fri Jul 6 19:32:19 2012 From: dukrat at mit.edu (Robert Arlt Jr.) Date: Fri, 06 Jul 2012 17:32:19 -0000 Subject: [Merge] lp:~dukrat/mailman/star_accept_these_nonmembers_override into lp:mailman/2.1 Message-ID: <20120706173218.16338.53494.launchpad@ackee.canonical.com> Robert Arlt Jr. has proposed merging lp:~dukrat/mailman/star_accept_these_nonmembers_override into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~dukrat/mailman/star_accept_these_nonmembers_override/+merge/113779 Adds options to have the *_these_nonmembers override the posting rights of members included in *_these_nonmembers on a per list per *_these_nonmembers basis. -- https://code.launchpad.net/~dukrat/mailman/star_accept_these_nonmembers_override/+merge/113779 Your team Mailman Coders is requested to review the proposed merge of lp:~dukrat/mailman/star_accept_these_nonmembers_override into lp:mailman/2.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 5871 bytes Desc: not available URL: From 971013 at bugs.launchpad.net Sat Jul 7 02:59:45 2012 From: 971013 at bugs.launchpad.net (Barry Warsaw) Date: Sat, 07 Jul 2012 00:59:45 -0000 Subject: [Bug 971013] Re: 3.0b2 database schema migrations References: <20120401185611.26818.71942.malonedeb@gac.canonical.com> Message-ID: <20120707005945.7422.45024.launchpad@gac.canonical.com> ** Branch linked: lp:~barry/mailman/bug-971013 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/971013 Title: 3.0b2 database schema migrations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/971013/+subscriptions From 971013 at bugs.launchpad.net Sat Jul 7 03:31:30 2012 From: 971013 at bugs.launchpad.net (Barry Warsaw) Date: Sat, 07 Jul 2012 01:31:30 -0000 Subject: [Bug 971013] Re: 3.0b2 database schema migrations References: <20120401185611.26818.71942.malonedeb@gac.canonical.com> Message-ID: <20120707013130.14629.78090.launchpad@chaenomeles.canonical.com> ** Branch linked: lp:~barry/mailman/alembic -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/971013 Title: 3.0b2 database schema migrations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/971013/+subscriptions From danci_emanuel at yahoo.com Tue Jul 10 13:50:24 2012 From: danci_emanuel at yahoo.com (Emanuel Danci) Date: Tue, 10 Jul 2012 11:50:24 -0000 Subject: [Merge] lp:~danci-emanuel/postorius/UI_dlists_support into lp:postorius Message-ID: <20120710115023.30206.30683.launchpad@ackee.canonical.com> Emanuel Danci has proposed merging lp:~danci-emanuel/postorius/UI_dlists_support into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~danci-emanuel/postorius/UI_dlists_support/+merge/114170 -- https://code.launchpad.net/~danci-emanuel/postorius/UI_dlists_support/+merge/114170 Your team Mailman Coders is requested to review the proposed merge of lp:~danci-emanuel/postorius/UI_dlists_support into lp:postorius. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 2882 bytes Desc: not available URL: From alexander at sulfrian.net Thu Jul 12 03:50:59 2012 From: alexander at sulfrian.net (AlexanderS) Date: Thu, 12 Jul 2012 01:50:59 -0000 Subject: [Bug 1023681] [NEW] bin/mailman -C config start does not work with a relativ config path References: <20120712015059.28836.62326.malonedeb@gac.canonical.com> Message-ID: <20120712015059.28836.62326.malonedeb@gac.canonical.com> Public bug reported: During testing I encountered, that bin/mailman is not working correctly if you supply a relative path as -C argument. For the main process the path is converted into a absolute path during startup but the bin/master process is getting the relative filename but maybe a different working directory. The attached patch fixes that behavior by supplying the generated absolute pathname to the new process. ** 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/1023681 Title: bin/mailman -C config start does not work with a relativ config path To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1023681/+subscriptions From alexander at sulfrian.net Thu Jul 12 03:50:59 2012 From: alexander at sulfrian.net (AlexanderS) Date: Thu, 12 Jul 2012 01:50:59 -0000 Subject: [Bug 1023681] Re: bin/mailman -C config start does not work with a relativ config path References: <20120712015059.28836.62326.malonedeb@gac.canonical.com> Message-ID: <20120712015100.28836.37710.malone@gac.canonical.com> ** Patch added: "bin-master-absolute-config-path.patch" https://bugs.launchpad.net/bugs/1023681/+attachment/3220342/+files/bin-master-absolute-config-path.patch -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1023681 Title: bin/mailman -C config start does not work with a relativ config path To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1023681/+subscriptions From 1023681 at bugs.launchpad.net Thu Jul 12 04:30:51 2012 From: 1023681 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 12 Jul 2012 02:30:51 -0000 Subject: [Bug 1023681] Re: bin/mailman -C config start does not work with a relativ config path References: <20120712015059.28836.62326.malonedeb@gac.canonical.com> Message-ID: <20120712023052.25417.91727.launchpad@chaenomeles.canonical.com> ** Tags added: mailm ** Tags removed: mailm ** Tags added: 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/1023681 Title: bin/mailman -C config start does not work with a relativ config path To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1023681/+subscriptions From sladev5976 at yahoo.com Thu Jul 12 07:30:55 2012 From: sladev5976 at yahoo.com (Bernard Keimel) Date: Thu, 12 Jul 2012 05:30:55 -0000 Subject: [Bug 1023681] Re: bin/mailman -C config start does not work with a relativ config path References: <20120712015059.28836.62326.malonedeb@gac.canonical.com> Message-ID: <20120712053057.2448.59531.launchpad@soybean.canonical.com> ** Changed in: mailman Status: New => Confirmed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1023681 Title: bin/mailman -C config start does not work with a relativ config path To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1023681/+subscriptions From 1024509 at bugs.launchpad.net Fri Jul 13 20:35:23 2012 From: 1024509 at bugs.launchpad.net (Barry Warsaw) Date: Fri, 13 Jul 2012 18:35:23 -0000 Subject: [Bug 1024509] [NEW] Link between members and mailing lists should use List-ID References: <20120713183523.30338.13311.malonedeb@gac.canonical.com> Message-ID: <20120713183523.30338.13311.malonedeb@gac.canonical.com> Public bug reported: The link between users and the mailing lists they are subscribed to is kept in the IMember implementation (and the member table). To allow for separation of database, these are not foreign keys, but instead string references using the fqdn_listname. However, mailing lists can be renamed, so using the fqdn_listname is wrong. List-ID is a much more stable identifier, so that should be used instead. ** Affects: mailman Importance: Undecided Status: New ** Tags: 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/1024509 Title: Link between members and mailing lists should use List-ID To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1024509/+subscriptions From franck at avonsys.com Sun Jul 15 21:39:20 2012 From: franck at avonsys.com (Franck) Date: Sun, 15 Jul 2012 19:39:20 -0000 Subject: [Merge] lp:~mlm-author/mailman/2.1-author into lp:mailman/2.1 Message-ID: <20120715193919.11005.10102.launchpad@ackee.canonical.com> Franck has proposed merging lp:~mlm-author/mailman/2.1-author into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~mlm-author/mailman/2.1-author/+merge/115035 This change is optional through the use of the author_list variable and is set to off by default. Once set to on, it will use the list address in the From: header changing the display name to indicate who is the author of the post. The email address of the original post will be added to the reply-to field. It does also some cleansing of some authentications headers. Overall, this change allows mailing lists that choose so, to be able to be compatible with authentication schemes such as ADSP or DMARC. A test list using this branch is at http://lists.peachymango.org/mailman/listinfo/mlm-auth -- https://code.launchpad.net/~mlm-author/mailman/2.1-author/+merge/115035 Your team Mailman Coders is requested to review the proposed merge of lp:~mlm-author/mailman/2.1-author into lp:mailman/2.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 5853 bytes Desc: not available URL: From 1004055 at bugs.launchpad.net Tue Jul 17 00:01:17 2012 From: 1004055 at bugs.launchpad.net (Florian Fuchs) Date: Mon, 16 Jul 2012 22:01:17 -0000 Subject: [Bug 1004055] Re: tutorial on running Postorius via Apache References: <20120524165605.26515.4459.malonedeb@gac.canonical.com> Message-ID: <20120716220118.25553.23679.malone@chaenomeles.canonical.com> Documentation for running Postorius under Apache/mod_wsgi has been added to src/postorius/docs/setup.rst ** Changed in: postorius Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1004055 Title: tutorial on running Postorius via Apache To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1004055/+subscriptions From noreply at launchpad.net Tue Jul 17 17:10:24 2012 From: noreply at launchpad.net (noreply at launchpad.net) Date: Tue, 17 Jul 2012 15:10:24 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 29: catch IOError (failing to connect to Mailman API) and raise custom Exception Message-ID: <20120717151024.18928.84379.launchpad@ackee.canonical.com> ------------------------------------------------------------ revno: 29 committer: Florian Fuchs branch nick: mailman.client timestamp: Tue 2012-07-17 17:08:13 +0200 message: catch IOError (failing to connect to Mailman API) and raise custom Exception modified: mailman/client/__init__.py mailman/client/_client.py -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 2381 bytes Desc: not available URL: From 1021364 at bugs.launchpad.net Tue Jul 17 17:03:01 2012 From: 1021364 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Tue, 17 Jul 2012 15:03:01 -0000 Subject: [Bug 1021364] Re: Catch httplib2 error if REST API is not available References: <20120705155149.5384.41016.malonedeb@wampee.canonical.com> Message-ID: <20120717150303.5276.96979.launchpad@ackee.canonical.com> ** Branch linked: lp:~flo-fuchs/postorius/bug-1021364 -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1021364 Title: Catch httplib2 error if REST API is not available To manage notifications about this bug go to: https://bugs.launchpad.net/mailman.client/+bug/1021364/+subscriptions From 1021364 at bugs.launchpad.net Tue Jul 17 17:11:33 2012 From: 1021364 at bugs.launchpad.net (Florian Fuchs) Date: Tue, 17 Jul 2012 15:11:33 -0000 Subject: [Bug 1021364] Re: Catch httplib2 error if REST API is not available References: <20120705155149.5384.41016.malonedeb@wampee.canonical.com> Message-ID: <20120717151133.13561.86494.malone@gac.canonical.com> Fix commited. Please update both postorius as well as mailman.client. ** Changed in: mailman.client Status: New => Fix Committed ** Changed in: postorius Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1021364 Title: Catch httplib2 error if REST API is not available To manage notifications about this bug go to: https://bugs.launchpad.net/mailman.client/+bug/1021364/+subscriptions From 1025709 at bugs.launchpad.net Tue Jul 17 17:19:10 2012 From: 1025709 at bugs.launchpad.net (Florian Fuchs) Date: Tue, 17 Jul 2012 15:19:10 -0000 Subject: [Bug 1025709] [NEW] When logging in through BrowserID or django.contrib.auth: Create new MM user if none exists References: <20120717151910.26084.37208.malonedeb@chaenomeles.canonical.com> Message-ID: <20120717151910.26084.37208.malonedeb@chaenomeles.canonical.com> Public bug reported: Currently user data held by Postorius is not neccessarily connected to Mailman. Once logged in, it should be checked if the user already exists in MM and a new user should be added to via the API if necessary. ** Affects: postorius Importance: Undecided Status: New ** Description changed: Currently user data held by Postorius is not neccessarily connected to - Mailman. Once logged in, it should be checked if the user exists in MM - and add a new user if necessary. + Mailman. Once logged in, it should be checked if the user already exists + in MM and a new user should be added to via the API if necessary. -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1025709 Title: When logging in through BrowserID or django.contrib.auth: Create new MM user if none exists To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1025709/+subscriptions From 1021364 at bugs.launchpad.net Tue Jul 17 19:45:57 2012 From: 1021364 at bugs.launchpad.net (Florian Fuchs) Date: Tue, 17 Jul 2012 17:45:57 -0000 Subject: [Bug 1021364] Re: Catch httplib2 error if REST API is not available References: <20120705155149.5384.41016.malonedeb@wampee.canonical.com> Message-ID: <20120717174557.27616.78001.malone@soybean.canonical.com> The first solution was to catch IOError. But because urllib2.HTTPError inherits from IOError, that's too general. Re-opening the ticket... ** Changed in: mailman.client Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1021364 Title: Catch httplib2 error if REST API is not available To manage notifications about this bug go to: https://bugs.launchpad.net/mailman.client/+bug/1021364/+subscriptions From noreply at launchpad.net Tue Jul 17 19:58:10 2012 From: noreply at launchpad.net (noreply at launchpad.net) Date: Tue, 17 Jul 2012 17:58:10 -0000 Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 30: added catch for urllib2.HTTPError before catching IOError Message-ID: <20120717175810.4071.26898.launchpad@ackee.canonical.com> ------------------------------------------------------------ revno: 30 fixes bug: https://launchpad.net/bugs/1021364 committer: Florian Fuchs branch nick: mailman.client timestamp: Tue 2012-07-17 19:56:36 +0200 message: added catch for urllib2.HTTPError before catching IOError modified: mailman/client/_client.py -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription -------------- next part -------------- A non-text attachment was scrubbed... Name: revision-diff.txt Type: text/x-diff Size: 489 bytes Desc: not available URL: From 1021364 at bugs.launchpad.net Tue Jul 17 19:59:42 2012 From: 1021364 at bugs.launchpad.net (Florian Fuchs) Date: Tue, 17 Jul 2012 17:59:42 -0000 Subject: [Bug 1021364] Re: Catch httplib2 error if REST API is not available References: <20120705155149.5384.41016.malonedeb@wampee.canonical.com> Message-ID: <20120717175942.13561.87942.malone@gac.canonical.com> urllib2.HTTPError is now catched before IOError, so HTTP exceptions are raised again. ** Changed in: mailman.client Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1021364 Title: Catch httplib2 error if REST API is not available To manage notifications about this bug go to: https://bugs.launchpad.net/mailman.client/+bug/1021364/+subscriptions From 1021364 at bugs.launchpad.net Tue Jul 17 19:57:31 2012 From: 1021364 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Tue, 17 Jul 2012 17:57:31 -0000 Subject: [Bug 1021364] Re: Catch httplib2 error if REST API is not available References: <20120705155149.5384.41016.malonedeb@wampee.canonical.com> Message-ID: <20120717175731.5276.33746.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman.client -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1021364 Title: Catch httplib2 error if REST API is not available To manage notifications about this bug go to: https://bugs.launchpad.net/mailman.client/+bug/1021364/+subscriptions From 1004053 at bugs.launchpad.net Fri Jul 20 23:50:04 2012 From: 1004053 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 20 Jul 2012 21:50:04 -0000 Subject: [Bug 1004053] Re: list members view References: <20120524165341.11307.92442.malonedeb@chaenomeles.canonical.com> Message-ID: <20120720215005.30672.40020.launchpad@ackee.canonical.com> ** Branch linked: lp:postorius -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1004053 Title: list members view To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1004053/+subscriptions From 1004053 at bugs.launchpad.net Fri Jul 20 23:50:44 2012 From: 1004053 at bugs.launchpad.net (Florian Fuchs) Date: Fri, 20 Jul 2012 21:50:44 -0000 Subject: [Bug 1004053] Re: list members view References: <20120524165341.11307.92442.malonedeb@chaenomeles.canonical.com> Message-ID: <20120720215046.15861.83884.launchpad@soybean.canonical.com> ** Changed in: postorius Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1004053 Title: list members view To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1004053/+subscriptions From 1027496 at bugs.launchpad.net Sat Jul 21 23:26:33 2012 From: 1027496 at bugs.launchpad.net (Florian Fuchs) Date: Sat, 21 Jul 2012 21:26:33 -0000 Subject: [Bug 1027496] [NEW] Check code against pep8 conventions References: <20120721212633.20708.2253.malonedeb@wampee.canonical.com> Message-ID: <20120721212633.20708.2253.malonedeb@wampee.canonical.com> Public bug reported: It's a dirty job, but someone's gotta do it. ** Affects: postorius Importance: Undecided Status: In Progress ** Changed in: postorius Status: New => In Progress ** Changed in: postorius Milestone: None => 1.0.0a2 ** Branch linked: lp:~flo-fuchs/postorius/pep8 -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1027496 Title: Check code against pep8 conventions To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1027496/+subscriptions From sladev5976 at yahoo.com Sun Jul 22 14:20:18 2012 From: sladev5976 at yahoo.com (Bernard Keimel) Date: Sun, 22 Jul 2012 12:20:18 -0000 Subject: [Bug 1024509] Re: Link between members and mailing lists should use List-ID References: <20120713183523.30338.13311.malonedeb@gac.canonical.com> Message-ID: <20120722122019.1827.48021.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Assignee: (unassigned) => Bernard Keimel (sladev5976) ** Changed in: mailman Status: Confirmed => 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/1024509 Title: Link between members and mailing lists should use List-ID To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1024509/+subscriptions From 971013 at bugs.launchpad.net Thu Jul 26 05:08:54 2012 From: 971013 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 26 Jul 2012 03:08:54 -0000 Subject: [Bug 971013] Re: 3.0b2 database schema migrations References: <20120401185611.26818.71942.malonedeb@gac.canonical.com> Message-ID: <20120726030854.871.6101.malone@wampee.canonical.com> include_list_post_header -> allow_list_posts When set to False, add List_Post: NO -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/971013 Title: 3.0b2 database schema migrations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/971013/+subscriptions From 967238 at bugs.launchpad.net Thu Jul 26 05:08:06 2012 From: 967238 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 26 Jul 2012 03:08:06 -0000 Subject: [Bug 967238] Re: Expose IMailingList.archive and .archive_private in the REST API References: <20120328154636.3793.85472.malonedeb@soybean.canonical.com> Message-ID: <20120726030807.15756.68188.launchpad@gac.canonical.com> ** Changed in: mailman Milestone: None => 3.0.0b2 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/967238 Title: Expose IMailingList.archive and .archive_private in the REST API To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967238/+subscriptions From 971013 at bugs.launchpad.net Thu Jul 26 06:23:37 2012 From: 971013 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 26 Jul 2012 04:23:37 -0000 Subject: [Bug 971013] Re: 3.0b2 database schema migrations References: <20120401185611.26818.71942.malonedeb@gac.canonical.com> Message-ID: <20120726042338.29833.83784.launchpad@soybean.canonical.com> ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/971013 Title: 3.0b2 database schema migrations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/971013/+subscriptions From 967238 at bugs.launchpad.net Thu Jul 26 06:22:48 2012 From: 967238 at bugs.launchpad.net (Barry Warsaw) Date: Thu, 26 Jul 2012 04:22:48 -0000 Subject: [Bug 967238] Re: Expose IMailingList.archive and .archive_private in the REST API References: <20120328154636.3793.85472.malonedeb@soybean.canonical.com> Message-ID: <20120726042249.1930.74096.launchpad@wampee.canonical.com> ** Changed in: mailman Status: In Progress => Fix Committed ** Tags removed: easy -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/967238 Title: Expose IMailingList.archive and .archive_private in the REST API To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967238/+subscriptions From 1027496 at bugs.launchpad.net Thu Jul 26 11:17:20 2012 From: 1027496 at bugs.launchpad.net (Florian Fuchs) Date: Thu, 26 Jul 2012 09:17:20 -0000 Subject: [Bug 1027496] Re: Check code against pep8 conventions References: <20120721212633.20708.2253.malonedeb@wampee.canonical.com> Message-ID: <20120726091721.16590.47396.launchpad@gac.canonical.com> ** Changed in: postorius Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1027496 Title: Check code against pep8 conventions To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1027496/+subscriptions From 996624 at bugs.launchpad.net Thu Jul 26 11:23:22 2012 From: 996624 at bugs.launchpad.net (Florian Fuchs) Date: Thu, 26 Jul 2012 09:23:22 -0000 Subject: [Bug 996624] Re: dev_setup website needs to be a separate branch References: <20120508163905.8762.10622.malonedeb@gac.canonical.com> Message-ID: <20120726092322.2032.80921.malone@wampee.canonical.com> I added a separate branch that contains only the project files for Postorius here: https://code.launchpad.net/~mailman- coders/postorius/postorius_standalone @Robert: Thanks for creating this buildout! I added the link to the github repository to the installation docs. ** Changed in: postorius Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/996624 Title: dev_setup website needs to be a separate branch To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/996624/+subscriptions From corbellini.andrea at gmail.com Thu Jul 26 18:18:33 2012 From: corbellini.andrea at gmail.com (Andrea Corbellini) Date: Thu, 26 Jul 2012 16:18:33 -0000 Subject: [Bug 1029536] [NEW] cannot determine whether you are subscribed to a mailing list and how References: <20120726161833.27347.11289.malonedeb@chaenomeles.canonical.com> Message-ID: <20120726161833.27347.11289.malonedeb@chaenomeles.canonical.com> Public bug reported: There is really not a reliable and useful way to know whether you are subscribed to a mailing list and, if so, the email address you used. The only way currently is to try registering with all your own email addresses till you get an "already subscribed" error. ** 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/1029536 Title: cannot determine whether you are subscribed to a mailing list and how To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1029536/+subscriptions From mark at msapiro.net Thu Jul 26 22:20:41 2012 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 26 Jul 2012 20:20:41 -0000 Subject: [Bug 1029536] Re: cannot determine whether you are subscribed to a mailing list and how References: <20120726161833.27347.11289.malonedeb@chaenomeles.canonical.com> Message-ID: <20120726202042.30237.38487.malone@soybean.canonical.com> If the list has a public roster, you can visit the roster and look for your email address(es). If the roster is not public, it is because the list owner has decided to not make this information publicly available. This is the list owner's decision. ** Changed in: mailman Status: New => Invalid -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1029536 Title: cannot determine whether you are subscribed to a mailing list and how To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1029536/+subscriptions From sladev5976 at yahoo.com Mon Jul 30 07:32:10 2012 From: sladev5976 at yahoo.com (Bernard Keimel) Date: Mon, 30 Jul 2012 05:32:10 -0000 Subject: [Bug 971013] Re: 3.0b2 database schema migrations References: <20120401185611.26818.71942.malonedeb@gac.canonical.com> Message-ID: <20120730053211.2086.87052.launchpad@soybean.canonical.com> ** Changed in: mailman Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/971013 Title: 3.0b2 database schema migrations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/971013/+subscriptions From 971013 at bugs.launchpad.net Mon Jul 30 14:37:40 2012 From: 971013 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 30 Jul 2012 12:37:40 -0000 Subject: [Bug 971013] Re: 3.0b2 database schema migrations References: <20120401185611.26818.71942.malonedeb@gac.canonical.com> Message-ID: <20120730123740.3814.95209.malone@soybean.canonical.com> Bernard. I appreciate your help, but please don't change the status of fix committed bugs. This status helps us track issues for releases, adn "Confirmed" means it's an open bug. Even if the bug hasn't been fixed, please simply enter a comment instead of changing the bug status. Thanks. ** Changed in: mailman Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/971013 Title: 3.0b2 database schema migrations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/971013/+subscriptions From rnix at squarewave.at Tue Jul 31 17:24:50 2012 From: rnix at squarewave.at (Robert Niederreiter) Date: Tue, 31 Jul 2012 15:24:50 -0000 Subject: [Bug 1031393] [NEW] wrong attribute name according to mailman.interfaces.mailinglist.IMailingList References: <20120731152450.28453.79751.malonedeb@gac.canonical.com> Message-ID: <20120731152450.28453.79751.malonedeb@gac.canonical.com> Public bug reported: as pointed out here... http://bazaar.launchpad.net/~rnix/mailman/anon-subscribe/revision/7160 http://bazaar.launchpad.net/~rnix/mailman/anon-subscribe/revision/7161 ...it seems that mlist.archive is no longer or is declared in the interface the wrong way cheers robert ** 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/1031393 Title: wrong attribute name according to mailman.interfaces.mailinglist.IMailingList To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1031393/+subscriptions From rnix at squarewave.at Tue Jul 31 17:20:43 2012 From: rnix at squarewave.at (Robert Niederreiter) Date: Tue, 31 Jul 2012 15:20:43 -0000 Subject: [Bug 1031391] [NEW] remove msgdata['received_time'] in mailman.app.moderator before calling IListRequests.hold_request References: <20120731152043.27128.42546.malonedeb@gac.canonical.com> Message-ID: <20120731152043.27128.42546.malonedeb@gac.canonical.com> Public bug reported: msgdata['received_time'] in mailman.app.moderator.hold_message contains datetime.datetime object when being called. this causes hold_request to fail -> it expects only strings as additional data. so either remove received_time like so: http://bazaar.launchpad.net/~rnix/mailman/anon-subscribe/revision/7159 before calling hold_request, convert received_time to string before calling hold_request, or improve mailman.model.request.ListRequests.hold_request as already commented in source code (maybe to also accept datetime instances?) cheers, robert ** Affects: mailman Importance: Undecided Status: New ** Description changed: msgdata['received_time'] in mailman.app.moderator.hold_message contains datetime.datetime object when being called. this causes hold_request to fail -> it expects only strings as additional data. so either remove received_time like so: http://bazaar.launchpad.net/~rnix/mailman/anon-subscribe/revision/7159 before calling hold_request, convert received_time to string before calling hold_request, or improve mailman.model.request.ListRequests.hold_request as already - commented in source code + commented in source code (maybe to also accept datetime instances?) cheers, robert -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1031391 Title: remove msgdata['received_time'] in mailman.app.moderator before calling IListRequests.hold_request To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1031391/+subscriptions From sladev5976 at yahoo.com Tue Jul 31 22:09:17 2012 From: sladev5976 at yahoo.com (Bernard Keimel) Date: Tue, 31 Jul 2012 20:09:17 -0000 Subject: [Bug 1031391] Re: remove msgdata['received_time'] in mailman.app.moderator before calling IListRequests.hold_request References: <20120731152043.27128.42546.malonedeb@gac.canonical.com> Message-ID: <20120731200918.18457.32064.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Assignee: (unassigned) => Bernard Keimel (sladev5976) ** Changed in: mailman Assignee: Bernard Keimel (sladev5976) => (unassigned) ** Changed in: mailman Assignee: (unassigned) => Bernard Keimel (sladev5976) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1031391 Title: remove msgdata['received_time'] in mailman.app.moderator before calling IListRequests.hold_request To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1031391/+subscriptions