Re: [Mailman-Developers] Event notifications

On Sep 07, 2012, at 02:25 PM, George Chatzisofroniou wrote: >[1]: https://bugs.launchpad.net/mailman/+bug/1047286 I've added the mailman3 tag. Cheers, -Barry signature.asc Description: PGP signature ___ Mailman-Developers mailing list Mailman-Develop

Re: [Mailman-Developers] 3.0.0b1 fails bootstrap.py on Mountain Lion

On Sep 06, 2012, at 10:23 PM, Richard Wackerbarth wrote: >I have 10.7 and, today, I had the same problem. > >Yesterday, I was able to set things up without any problems. > >I think that the difference is that z3c.recipe.tag has bumped the version >number to 0.5 but that the distribution is missing

Re: [Mailman-Developers] 3.0.0b1 fails bootstrap.py on Mountain Lion

On Sep 06, 2012, at 11:11 AM, G B wrote: >I initially posted this to mailman-users, but it was suggested that this >would be a better list. > >I'm installing Mailman for the first time, and chose to try the beta. I'm >installing on a Mountain Lion Server, that was cleanly installed. I've since >

Re: [Mailman-Developers] Event notifications

On Aug 02, 2012, at 12:13 PM, George Chatzisofroniou wrote: >It looks like the only notification the core provides is that of new >postings (through the IArchiver interface). It would be great if core >could provide notifications for more events (like someone subscribed >or a new thread started) t

Re: [Mailman-Developers] Sample / dummy / generated data for mailman?

On Sep 05, 2012, at 02:01 PM, Ethan Fremen wrote: >Is there any way to automatically generate lists/messages/members etc? > >If not, how do you (existing devs) go about setting up mailman with said >data? > >I am interested in working on >https://bugs.launchpad.net/postorius/+bug/1004049 , and so

Re: [Mailman-Developers] Working on Postorius

On Sep 02, 2012, at 02:23 PM, Ethan Fremen wrote: >OK, I finally got postorius running. Excellent! >I had to make a few small changes to postorius_standalone to get it >working, and I would like to add instructions to the 5 minute guide for >getting things set up with Virtualenv so you don't hav

Re: [Mailman-Developers] NNTP Archive - final report

Thanks for the update Alex. I can confirm that Thunderbird on Ubuntu 12.10 can read the one newsgroup that has about 88 messages in it. Claws cannot though - it thinks the newsgroup is empty. I only tried port 119. I have not had a chance to look at the code yet. Cheers, -Barry signature.asc

Re: [Mailman-Developers] translation of mail templates

On Aug 21, 2012, at 01:04 PM, Stephen J. Turnbull wrote: >Patrick Ben Koetter writes: > > > They have free accounts for open source projects. It might be a > > nice way to organize a translation community. > >It's likely that we don't have to organize one, we already have one. >Barry, why don't yo

Re: [Mailman-Developers] status of mailman 3.0 web stuff

On Aug 21, 2012, at 11:08 AM, Ethan Fremen wrote: >I now have a job where I will be coding python again, and I was wondering >if I could help push this forward? the >http://wiki.list.org/display/DEV/Web+Interface+Status page says that a >basic UI is being set up. This is being driven forward in

Re: [Mailman-Developers] translation of mail templates

On Aug 21, 2012, at 02:08 AM, Patrick Ben Koetter wrote: >I am not the one to tell about the technical issues, but I can tell > works well for Modoboa . >They have free accounts for open source projects. It might be a nice way to >organize a trans

Re: [Mailman-Developers] translation of mail templates

On Aug 20, 2012, at 06:22 PM, Peter Holzer wrote: >I just took the english templates from MM3 and started to change them. Are >the templates the same as in MM2? Anyhow do i have to configure something in >MM3 to make these templates work? The i18n infrastructure is probably not complete in mm3,

Re: [Mailman-Developers] MM3 - preventing command summary by email

On Aug 20, 2012, at 08:29 AM, Robert Niederreiter wrote: >are tests passing right now in trunk? last time i tried running the tests >there were errors: This was just a section in testing.cfg that was left uncommented. I'd done a bunch of PostgreSQL clean up work and accidentally checked in the s

Re: [Mailman-Developers] MM3 - preventing command summary by email

On Aug 19, 2012, at 04:50 PM, Peter Holzer wrote: >In my opinion or at least for our usecase it doesn't make much sense to send >2 mails to the subscriber, one that tells the user "Confirmation email sent" >and sending a mail to the user that he should confirm his email address. If >the command i

Re: [Mailman-Developers] Implementing the IArchiver

Hi George. Sorry I was on vacation and mostly off-line. On Aug 06, 2012, at 08:28 PM, George Chatzisofroniou wrote: >I was wondering what is the best way to test an IArchive >implementation. Are there any built in test modes that will allow me >to send sample messages? I only care about the proc

Re: [Mailman-Developers] MM3 - preventing command summary by email

On Aug 03, 2012, at 04:55 PM, Robert Niederreiter wrote: >Is there a way to disable command summary sent by mail? e.g. after >subscription and subscription confirmation. Not currently. Why do you want to suppress the results? -Barry ___ Mailman-Devel

Re: [Mailman-Developers] Bug 971013 - schema migrations BLOCKED

On Jul 26, 2012, at 12:27 AM, Barry Warsaw wrote: >If you have beta1 deployed, please do give the upgrade a try. Make backups >first though! :) If you encounter bugs, please file them in Launchpad, >hopefully with a way to reproduce the problem, or at least let me know whether >

Re: [Mailman-Developers] Bug 971013 - schema migrations BLOCKED

On Jul 21, 2012, at 06:17 PM, Barry Warsaw wrote: >On Jul 06, 2012, at 10:00 PM, Barry Warsaw wrote: > >>This bug is about providing orderly schema migrations. I now admit that I'm >>blocked and I'm looking for suggestions. > >I actually think I've final

Re: [Mailman-Developers] Bug 971013 - schema migrations BLOCKED

On Jul 06, 2012, at 10:00 PM, Barry Warsaw wrote: >This bug is about providing orderly schema migrations. I now admit that I'm >blocked and I'm looking for suggestions. I actually think I've finally cracked this nut. I have it working for SQLite, and am now testing for

Re: [Mailman-Developers] Implementing the IArchiver

Hi George, On Jul 20, 2012, at 02:45 PM, George Chatzisofroniou wrote: >For my metrics app (GSoC project), I'm currently using a MM3 simulator >for testing purposes. Proceeding with the development, i think it's >time to implement a connection with a real MM3 environment. > >For the current versi

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 18, 2012, at 05:53 PM, Richard Wackerbarth wrote: >However, and this is the reason that I object to the bypassing of the service >level description, we also need to assure that each of these implementations >respect the requirement that ALL inter-service interactions be representable >stric

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 13, 2012, at 07:34 PM, Richard Wackerbarth wrote: >I think that you have missed a level of abstraction. I guess it's "turtles all the way down" :) >The service, per se, does not REQUIRE a REST interface in order to operate. >It only requires an implementation (in any language) and mutuall

Re: [Mailman-Developers] Exposing not advertised lists via nntp archiver

On Jul 17, 2012, at 01:34 PM, Richard Wackerbarth wrote: >But there probably should be a per-list configuration option for gateway-ing >a list to the news. There may well be lists for which I am willing to >advertise the existence without wanting their content to be spread far and >wide. Agreed.

Re: [Mailman-Developers] Exposing not advertised lists via nntp archiver

On Jul 15, 2012, at 12:26 AM, Alexander Sulfrian wrote: >There are mailinglists with a pubic archive but that not be advertised >by the server. The nntp archiver now have to supply a list of all >available archives. If this list does not contain a mailing list, in >most news clients you do not hav

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 13, 2012, at 05:43 PM, Richard Wackerbarth wrote: >> I would be happy enough with human readable documentation that >> described this user service in terms of resource locations and contents. > >I wouldn't even go that far. The service does not need to be DESCRIBED in >terms of locations a

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 13, 2012, at 11:56 AM, Richard Wackerbarth wrote: >Now, hopefully, we can agree that it is necessary to have a "user >service". Further it is reasonable to attempt to have this service distinct >from the "post routing service". The question is then "How will these >services interface to ea

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 13, 2012, at 12:03 PM, Stephen J. Turnbull wrote: >Barry Warsaw writes: > > > The question is whether we want to support running the core without > > having this user service available, i.e. in standalone mode. Are > > we going to require that this service be

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 13, 2012, at 11:57 AM, Stephen J. Turnbull wrote: >Barry Warsaw writes: > > > I don't see any reason why it couldn't be mapped to a REST API; it's just a > > lack of need, and nobody's written it yet. The question is whether > > IUserManager is

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 12, 2012, at 01:42 PM, Richard Wackerbarth wrote: >On Jul 11, 2012, at 9:53 PM, Barry Warsaw wrote: > >> Both implementations in fact can live side-by-side, and choosing one or the >> other is something you do when you install and configure the system. > >I'

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 12, 2012, at 11:39 AM, Richard Wackerbarth wrote: >If I understand you, we both envision a distributed database whereby any of >the components might actually provide the data storage for some specific >class of information. For example, without specifying where in the system it >will reside

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 12, 2012, at 12:25 AM, Richard Wackerbarth wrote: >On Jul 11, 2012, at 9:05 PM, Barry Warsaw wrote: >> There *should* be enough hooks in the system already for a system > >> administrator to say "I want to use Postorius, so I must enable the >> Postoriu

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 11, 2012, at 09:27 AM, Richard Wackerbarth wrote: >First, we should define all of the data storage in terms of the REST access >points to the data. (And not, as presently done, the other way around) Next, >we should access all of the REST interface URLs indirectly so that >functionality can

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 12, 2012, at 02:50 AM, Stephen J. Turnbull wrote: >Nevertheless, it would be preferable if that is wrapped in an API that >makes it look like it's all coming form one place, and which manages >the linkages so that data is not store redundantly in different >places, or inaccessible to certai

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 11, 2012, at 05:04 PM, Richard Wackerbarth wrote: >As an example, suppose that I want to have an "intelligent" ToDo indicator. >As a minimum, I need to be able to get from the data store a list of MLs that >have pending requests AND for which I am authorized to do that work. >Typically, thi

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 11, 2012, at 02:22 PM, Richard Wackerbarth wrote: >No! Although you are making available (some/most/all) of the data values, you >are not making available the ability to make arbitrary SQL-type queries to >view the data. Which frankly, I don't think we should do, in the core. The core is

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 12, 2012, at 02:50 AM, Stephen J. Turnbull wrote: >It's not the same argument. A mailing list needs a message >distribution agent; it doesn't *need* a webUI. +1 Or I might rephrase that as: it doesn't need *a* webUI :). Postorius rocks, and it is going to be a fantastic piece of the def

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 11, 2012, at 05:39 AM, Richard Wackerbarth wrote: >I am perfectly happy to have the user info handled by an independent >stand-alone module which is willing to take responsibility for ALL of the >user profile info. It should provide a REST interface that allows other >modules the ability pe

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 11, 2012, at 02:12 PM, Stephen J. Turnbull wrote: >But isn't that going to take us a long way down the road where we >anoint Postorius the one-and-only admin interface? If that really >needs to be, OK, but I don't much like it. I don't either; it's unacceptable. Many, maybe most, sites w

Re: [Mailman-Developers] Login / User Identification Issues in MM3

On Jul 10, 2012, at 10:51 PM, Richard Wackerbarth wrote: >Yes, it is a bug in Postorius. However, that does not negate the fact that >the present design, by forcing a split database, makes it difficult to >accomplish the desired behavior. Why exactly is it difficult? I'm not trolling, I really w

Re: [Mailman-Developers] Login / User Identification Issues in MM3

Thanks for starting this discussion. Since the thread's already long, I'm just going to answer randomly with my own thoughts. One thing I have a real problem with is defining the database query layer as the interface between components. To me that just unacceptably ties us to a specific database

[Mailman-Developers] Bug 971013 - schema migrations BLOCKED

I've been working on and off for quite some time on bug 971013 https://bugs.launchpad.net/mailman/+bug/971013 This bug is about providing orderly schema migrations. I now admit that I'm blocked and I'm looking for suggestions. As you know, I made a promise that after beta 1, we'd only change th

Re: [Mailman-Developers] Adding a new list attribute

On Jul 02, 2012, at 02:01 PM, Danci Emanuel wrote: >Indeed, I added these values to the tables, so now they should be fine. > >Still, now I am facing another problem. Although I suspected that in the >get_configuration() is the problem, now I cannot debug that because  >now I get a new error. Afte

Re: [Mailman-Developers] mailman3 instance for preview + exploration

On Jul 06, 2012, at 11:20 AM, Jeff Marshall wrote: >First, I restarted mailman3 and the error at >http://mailman3.jab.org:8000/persisted. Then I killed and restarted >postorius and the error cleared up. > The postorius instance is accessible again. Thanks Jeff; so it does look like a bug in Post

Re: [Mailman-Developers] URGENT: Google Summer of Code status report and code due

On Jul 06, 2012, at 02:36 PM, Stephen J. Turnbull wrote: >It's not clear to me how the MUA would know that. Many MUAs (well, at >least one, and you know which one I'm talking about! Reindeer and >mooses and Gnus, oh my!) can handle multiple feeds simultaneously. >Suppose you have multiple archiv

Re: [Mailman-Developers] [Bug 1020683] Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other).

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,

Re: [Mailman-Developers] URGENT: Google Summer of Code status report and code due

On Jul 05, 2012, at 09:24 AM, Stephen J. Turnbull wrote: >IMO, make that *three* things. It ought to be possible to fire up the >NNTP runner on an existing archive, and vend messages. +1 >I suppose this means a separate database for news properties like the message >to message number mapping, a

Re: [Mailman-Developers] mailman3 instance for preview + exploration

On Jul 03, 2012, at 10:15 PM, Jeff Breidenbach wrote: >That sure didn't take very long... If the core crashed, please take a look at the error log and file bugs! Thanks, -Barry ___ Mailman-Developers mailing list Mailman-Developers@python.org http://ma

Re: [Mailman-Developers] mailman3 instance for preview + exploration

On Jul 03, 2012, at 04:32 PM, Jeff Breidenbach wrote: >I suspect that there are folks who would like to see what Mailman 3 >and particularly Postorius without going through the effort of >software installation. Jeff Marshall was kind enough to set up a test >instance that people can look at and pl

Re: [Mailman-Developers] Twisted NNTP

On Jul 03, 2012, at 02:55 PM, Alexander Sulfrian wrote: >I working for gsoc creating NNTP access to the mailing list archives >for Mailman 3. Therefor I tried Twisted NNTP, during the last days. I >noticed, that it is not standard conform in any way. For example: it >missing required commands and

Re: [Mailman-Developers] Adding a new list attribute

On Jul 01, 2012, at 02:54 PM, Danci Emanuel wrote: >Secondly, I tried to modify the list attributes by adding the following:  > >dlists_enabled = Attribute("""Is the Dynamic sublist feature enabled?""") - >"IMailingList" interface (/interfaces/mailinglist.py) dlists_enabled = Bool() >-  "MailingLi

Re: [Mailman-Developers] Questions in regard to the database operations

On Jun 28, 2012, at 04:17 PM, Danci Emanuel wrote: >Yes, in terms of how the back-end works, it answers it. But, I am interested >also in the following aspect. Lets say that a users subscribes to a list with >his/her preferred  address. Afterwards, how can that user, who does not have >access to t

Re: [Mailman-Developers] Questions in regard to the database operations

On Jun 27, 2012, at 10:23 AM, Ian Eiloart wrote: >> There is an IPreferences interface which describes the kind of things that >> are "preferences". Members, users, and addresses all can have a pointer to >> a preferences record. There are also some system default preference >> values. When we

Re: [Mailman-Developers] Questions in regard to the database operations

Hi again Danci. Keep the great questions coming! :) On Jun 27, 2012, at 08:19 AM, Danci Emanuel wrote: >I am back with some questions in regard to the aliases. After a persons >becomes a member of a particular list, subscribing  with its primary email >address (the address at which he/she  will

Re: [Mailman-Developers] smtp error - [Errno 111] Connection refused - when trying to install MM 3.0

On Jun 27, 2012, at 11:07 AM, Danci Emanuel wrote: >This is the continuation of the topic started on the mailman-users mailing >list. Thanks for moving the discussion here. >Here is the original >post: http://mail.python.org/pipermail/mailman-users/2012-June/073632.html >And this is the post at

Re: [Mailman-Developers] Questions in regard to the database operations

On Jun 25, 2012, at 03:30 PM, Danci Emanuel wrote: >As for the latter problem, I still have something in mind. If we were to >choose the  second option (the one which implies setting the flag >"delivery_status" to the proper value) does this not mean that we will have >to keep the user`s preferenc

Re: [Mailman-Developers] Questions in regard to the database operations

On Jun 25, 2012, at 08:02 AM, Danci Emanuel wrote: >I still want to ask you something. As far as I am aware, I also have to >implement the aliases feature as Systers see it, meaning that a user, after >gets registered can post messages to a mailing list from more than one >address. Ah, so this is

Re: [Mailman-Developers] Questions in regard to the database operations

Hi Emanuel, On Jun 25, 2012, at 04:51 AM, Danci Emanuel wrote: >First of all, how is the aliases set populated in time? I'm guessing you mean the mailing list's "acceptable aliases", i.e. addresses which are not the list's posting address, but will still be accepted if it appears in a recipient

Re: [Mailman-Developers] Trying to install mm 3.0.0b1

On Jun 21, 2012, at 12:00 PM, Lindsay Haisley wrote: >I gave this some thought and decided that since any automated expunging >of subscribers probably should be done at a system level (although >theoretically a list admin could script an an automated mail command >exchange system, or automate an i

Re: [Mailman-Developers] Trying to install mm 3.0.0b1

On Jun 21, 2012, at 11:02 AM, Lindsay Haisley wrote: >The way I switched it on in 2.1.15 was by way of configuration variable >in mm_cfg.py containing a global AES secret key. This can be added to >mm_cfg.py by running a key generation script in the runtime mm bin >directory. Absent this variabl

Re: [Mailman-Developers] Trying to install mm 3.0.0b1

On Jun 21, 2012, at 10:32 AM, Lindsay Haisley wrote: >Barry, I don't know if you followed the discussion on the Users list >regarding placing an encrypted (AES) header into personalized, VERPed >list posts which would contain the subscriber recipient's address and >possibly also the list address.

Re: [Mailman-Developers] Trying to install mm 3.0.0b1

On Jun 21, 2012, at 09:25 AM, Lindsay Haisley wrote: >Jessy Kate Schingler said: >> FWIW, i found installing within a virtualenv to be a sanity-inducing >> operation for very similar reasons. >> >What's involved here? It's really pretty simple. I'm not sure what the default version of Python i

Re: [Mailman-Developers] Trying to install mm 3.0.0b1

On Jun 20, 2012, at 05:37 PM, Lindsay Haisley wrote: >I'm trying to install mm 3.0.0b1 as per the directions in START.rst. START.rst needs to be updated. In general, buildout is only needed to run the test suite, so I think it's more appropriate for development rather than deployment. In fact,

Re: [Mailman-Developers] MM3 - Using fqdn in the exposed URLs

On Jun 12, 2012, at 10:19 AM, Richard Wackerbarth wrote: >Perhaps you should consider a different strategy that does not couple so >tightly the SQL schema with the parameters. > >Rather that having an object which tries to keep everything directly on the >object, place many of those values in a di

Re: [Mailman-Developers] MM3 - Using fqdn in the exposed URLs

On Jun 12, 2012, at 08:01 AM, Richard Wackerbarth wrote: >Core will need to be provided a dictionary of items related to the >configuration of the list infrastructure. The URL for subscriber account >maintenance is one of those items. However, the contents of that field, or >any of the others, a

Re: [Mailman-Developers] MM3 - Using fqdn in the exposed URLs

On Jun 11, 2012, at 05:43 AM, Richard Wackerbarth wrote: >I think that we should rethink this decision and follow a "slug" approach to >the identification of the mailing lists in URLs. Those who choose to do so >can use the fqdn as their slug. But others would be able to readily change >the mappin

Re: [Mailman-Developers] Mailman 3.0 fresh install - problems from python interpreter

On Jun 07, 2012, at 09:31 AM, Jessy Kate Schingler wrote: >should the docs be updated perhaps? something either under "getting started >with GNU Maiman" or even a specific page on "interacting with mailman >through the python interpreter"? i am happy to add something or contribute >to that; i thin

Re: [Mailman-Developers] Speaking about kitties (or archivers)

On Jun 03, 2012, at 02:49 PM, Pierre-Yves Chibon wrote: >I can work on merging KittyStore and IMessageStore and providing the REST >interface for it. Should I provide also an implementation ? Using PostgreSQL >as backend ? It will be much easier to test with a SQLite backend, although as I'm fin

Re: [Mailman-Developers] Speaking about kitties (or archivers)

On Jun 03, 2012, at 11:21 PM, Patrick Ben Koetter wrote: >Maybe - and to pick up an idea Barry had mentioned to me a long time ago about >mailing list management directly from a mail client - we would gain the most >if we implemented an LMTP client as archiver (better: archive transport). > >This

Re: [Mailman-Developers] Speaking about kitties (or archivers)

On Jun 05, 2012, at 08:09 AM, Pierre-Yves Chibon wrote: >With the help of wacky on #mailman this week-end we came up with this >"patch". Attached is both the diff and the file itself. > >This way we can start discussing :) Point of order: it's much easier to deal with branches and merge proposal

Re: [Mailman-Developers] URGENT: Google Summer of Code status report and code due

On Jun 06, 2012, at 12:15 PM, Alexander Sulfrian wrote: >Currently I already created a blog[1] to present the recent development I >will do. I also created a personal branch on launchpad (you could find >it on[2]), but as I stated earlier, I have not pushed any new commits, >but I will start soon

Re: [Mailman-Developers] Mailman 3.0 fresh install - problems from python interpreter

Hi Jessy, You're doing everything right, but there's one conceptual step that you're missing, and which isn't evident from the docs. As Mark says, `mailman shell` is the best way to get a Python interactive interpreter shell to play with the internal Mailman API. Why is this better than just run

Re: [Mailman-Developers] Speaking about kitties (or archivers)

On Jun 02, 2012, at 07:19 AM, Patrick Ben Koetter wrote: >Maildir is robust but it doesn't scale under high load. You can add indexes, >but they are limited sooner or later too. > >Concerning mailbox formats Timo Sirainens current approach to collect a >limited number of messages in one file and

Re: [Mailman-Developers] Speaking about kitties (or archivers)

On May 31, 2012, at 10:28 AM, Toshio Kuratomi wrote: >Wacky looked at this today and asked if we should have the x-message-id-hash >as another key value to look up an email. That seems proper to me. +1 >Would we want a separate function or to overload get_email() so that it can >either take mes

Re: [Mailman-Developers] Speaking about kitties (or archivers)

On Apr 26, 2012, at 06:36 PM, Pierre-Yves Chibon wrote: >The current version of HK relies on mongodb for the storage, but I want >to test HK with a traditionnal SQL backend. So I have started to work on >this. > >The interface I defined is there: >https://github.com/pypingou/kittystore/blob/master

Re: [Mailman-Developers] Speaking about kitties (or archivers)

On Apr 24, 2012, at 11:12 AM, Toshio Kuratomi wrote: >Ive been thinking about this and I'm in mild disagreement. I think that >a mailing list system should give people an archive-store which is acessible >behind a generalized API. I'm warming up to this. The IArchiver interface is generic enoug

Re: [Mailman-Developers] Speaking about kitties (or archivers)

Jeebus, finally catching up on this thread. On Apr 24, 2012, at 01:41 PM, Stephen J. Turnbull wrote: >IMHO, premature optimization. Among other things, there isn't going >to be a "the" archiver-core. Mailman should provide "a" >archiver-core, and I think it should be based on maildir (which is

Re: [Mailman-Developers] HyperKitty MongoDB vs PostgreSQL.

On May 25, 2012, at 08:59 AM, Toshio Kuratomi wrote: >We're using SQLAlchemy i(a different ORM) to abstract the database layer. At one point the core used SA, but this was many years ago and I had lots of problems with it. IIRC it was mostly, when things went south, it was quite difficult to deb

Re: [Mailman-Developers] HyperKitty MongoDB vs PostgreSQL.

On May 25, 2012, at 11:18 AM, Pierre-Yves Chibon wrote: >Thus we will move forward with PostgreSQL as a back-end for HyperKitty. >The good news is that HyperKitty already works fine with PostgreSQL and >KittyStore (if you use the correct branch [4]). >However, we have to rebuild our test server, s

Re: [Mailman-Developers] Mailman 3 configuration questions and feedback

On May 24, 2012, at 01:53 PM, Florian Fuchs wrote: >+1 ...only I think the msg body currently isn't exposed by the MM API >(@Barry, can you confirm that?), in which case we would need two bug reports: >One for mailman (expose body of held messages) and one for Postorius (show >held msg body). The

Re: [Mailman-Developers] Mailman 3 configuration questions and feedback

On May 22, 2012, at 10:49 AM, Jeff Marshall wrote: >Hey everybody. I've been playing with 3.0.0b1 and Postorius. I have >some questions as well as some initial feedback. I am assuming many >of these are known issues or works-in-progress so I apologize ahead of >time. Glad you're taking a look

Re: [Mailman-Developers] [Merge] lp:~wacky/postorius/csrf into lp:postorius

On May 21, 2012, at 10:53 AM, Richard Wackerbarth wrote: >Again, I will comment that my preference for git is largely based on the lack >of support for bzr on Mac OSX. If we had the same GUI support that is >provided by, for example GitX, and we had integration with the Xcode IDE, >then I am sure

Re: [Mailman-Developers] [Merge] lp:~wacky/postorius/csrf into lp:postorius

Okay, you get the last word too. :) On May 21, 2012, at 06:32 AM, Richard Wackerbarth wrote: >On May 19, 2012, at 9:26 PM, Barry Warsaw wrote: >> While I really don't want to get into yet another religious VCS discussion >> on yet another unrelated list , Bazaar has on

Re: [Mailman-Developers] [Merge] lp:~wacky/postorius/csrf into lp:postorius

I don't want to side track too long into a vcs discussion, so I'll respond here and then you can have the last word. :) On May 21, 2012, at 12:21 PM, Stephen J. Turnbull wrote: >Barry Warsaw writes: > > > I personally think that rebase is an abomination generally re

Re: [Mailman-Developers] [Merge] lp:~wacky/postorius/csrf into lp:postorius

On May 20, 2012, at 09:22 AM, Richard Wackerbarth wrote: >My interest in deleting a branch is to clean the external namespace so that >users are not wasting their time examining branches which are not currently >useful. > >It appears that Launchpad handles this by setting the branch status to >"me

Re: [Mailman-Developers] [GSoC 2012] Metrics

On May 19, 2012, at 08:18 AM, Richard Wackerbarth wrote: >I think that we should remove ALL of the author information from the MM core >and create a separate service to collect and manage it. The mail handling >core can subscribe to this service for the little necessary information that >it requir

Re: [Mailman-Developers] subscription notification mail body

On May 14, 2012, at 08:42 AM, Stanisław Findeisen wrote: >On 2012-05-14 01:58, Mark Sapiro wrote: >> Stanislaw Findeisen wrote: >>> >>> Subscription notification mail body is also distorted sometimes: I just >>> received one for a new subscriber who used a diacritic in his name. >>> There is '?' (

Re: [Mailman-Developers] [GSoC 2012] Metrics

On May 03, 2012, at 02:04 AM, George Chatzisofroniou wrote: >Interface to the MM core > >The app needs to interact with the Mailman core. I think the best idea >is to implement a message bus that will send a notification every time >a message is sent (the same way an archiver works). Based on this

Re: [Mailman-Developers] need tutorial for setting up python development environment on Ubuntu please

On May 05, 2012, at 07:39 AM, Patrick Ben Koetter wrote: >* David : >> On Fri, May 4, 2012 at 4:22 PM, Barry Warsaw wrote: >> >> > On May 04, 2012, at 02:10 PM, David wrote: >> > >> > Now start up Mailman, your MTA >> >> >> Good up

Re: [Mailman-Developers] need tutorial for setting up python development environment on Ubuntu please

On May 04, 2012, at 02:10 PM, David wrote: >Next Questions: >1. what are the first tests I should perform after starting mailman? Try creating a mailing list from the command line: $ mailman create -d myl...@example.com Subscribe some addresses to mylist. Edit a file with a list of email a

Re: [Mailman-Developers] problem installing Mailman 3.0 beta1 - no var directory created during install

On May 03, 2012, at 02:49 PM, David wrote: >I installed it but I didn't get a var directory at all. (On the chance that >it is created only after starting Mailman the first time, I tried to start >it but that didn't work either.) The last line of the installation output Correct. The var director

Re: [Mailman-Developers] need tutorial for setting up python development environment on Ubuntu please

On May 03, 2012, at 09:20 PM, David wrote: >After a full day of stuff like this: >error: Installed distribution zope.interface 3.6.1 conflicts with >requirement zope.interface>=3.8.0 >... I need a good tutorial on setting up the development environment, >including whatever related tools are needed

Re: [Mailman-Developers] [Bug 985149] Add List-Post value to permalink hash input

On Apr 23, 2012, at 02:33 PM, Stephen J. Turnbull wrote: >What are you doing hanging out in e-mail circles, then? ;-) It has to >be the most prominent example of a computing field where smtplicity >has led to a disaster, and it has never been easy to understand! For some reason, I have Ren and S

Re: [Mailman-Developers] [Bug 985149] Add List-Post value to permalink hash input

On Apr 22, 2012, at 03:31 PM, Jeff Breidenbach wrote: >I find List-Id annoying because I like the world to be simple and easy to >understand. People who know nothing about RFCs natually consider the >posting address to be the canonical name of a mailing list. We should be >embracing that. In theo

Re: [Mailman-Developers] [Bug 985149] Add List-Post value to permalink hash input

On Apr 20, 2012, at 01:19 PM, Jeff Breidenbach wrote: >1) Terri is exactly right. The reason for including list identity as >part of the hash calculation is for cross-posted messages. An >archiving service shows context. Here's the message AND the thread it >fits into, AND information about the li

Re: [Mailman-Developers] [Bug 985149] [NEW] Add List-Post value to permalink hash input

On Apr 21, 2012, at 10:19 AM, Stephen J. Turnbull wrote: >On Sat, Apr 21, 2012 at 1:22 AM, Barry Warsaw wrote: > >> I think the hash value should be opaque.  Jeff can perhaps elaborate his >> use-case but I don't think the List-ID needs to be (or frankly *should* be) >&

Re: [Mailman-Developers] [Bug 985149] Add List-Post value to permalink hash input

I want to step back for a moment and look at some fundamentals. I'll reply to other messages in this thread later, but in the context of my own thoughts expressed here. TL;DR: I'm going to propose we keep the hash algorithm to include only the Message-ID as input. 0) Mailman core doesn't care wh

Re: [Mailman-Developers] Speaking about kitties (or archivers)

Thanks for posting this Pierre-Yves! On Apr 23, 2012, at 08:17 PM, Pierre-Yves Chibon wrote: > mm-core (handles the lists themselves) --send emails to archivers--> Note that the core doesn't *have* to send an email to the archiver. From the core's perspective, the `IArchiver` interface has thr

Re: [Mailman-Developers] [Bug 985149] Add List-Post value to permalink hash input

On Apr 20, 2012, at 11:12 AM, SM wrote: > 'While it is perfectly acceptable for a List Identifier to be >completely independent of the domain name of the host machine >servicing the mailing list, the owner of a mailing list MUST NOT >generate List Identifiers in any domain name space

Re: [Mailman-Developers] [Bug 985149] Add List-Post value to permalink hash input

On Apr 20, 2012, at 01:43 PM, Barry Warsaw wrote: >Note that RFC 5064 defines the Archived-At header. IMO, this would be the >appropriate place to add any list-specific namespace discriminator. Also, RFC >2369 defines the List-Archive header, which could contain the base URL to the

Re: [Mailman-Developers] [Bug 985149] Add List-Post value to permalink hash input

On Apr 20, 2012, at 11:33 AM, Terri Oda wrote: >A question, though: what if the list gets migrated to a new server and the >list id changes (e.g. because the domain or hostname changes)? I'm guessing >we can handle it, but we should make sure there's a path for that. I have to read RFC 2919 more

Re: [Mailman-Developers] [Bug 985149] Add List-Post value to permalink hash input

On Apr 20, 2012, at 12:09 PM, Richard Wackerbarth wrote: >As for the "opaque" hash, the order is not important. The order of the inputs >is arbitrary. It needs to be fixed and published so that multiple encoders >will derive the same hash as that generated by another encoder. Right. I've updated

<    2   3   4   5   6   7   8   9   10   11   >