[Mailman-Developers] Mailman headers (was Re: New RFC on using DKIM with MLMs)

Barry Warsaw writes: > >> X-Mailman-Version > > > >I think this should be replaced with X-Mailer, or even User-Agent. That's > >not > >currently an SMTP header, but I think it should be. And it is in quite > >widespread use. > > This is just the version of Mailman that sent the message.

Re: [Mailman-Developers] Mailman headers (was Re: New RFC on using DKIM with MLMs)

Murray S. Kucherawy writes: > I think having a message with User-Agent and List-Agent is less > confusing than one with two User-Agents. Who's going to be confused? Not end users.[1] I would think the real application is for an administrator or software to look at them and go, "Uh-oh, it's an

Re: [Mailman-Developers] Mailman headers (was Re: New RFC on using DKIM with MLMs)

Murray S. Kucherawy writes: > So your perspective is "why bother [distinguishing List-Agent from > User-Agent]", basically? If you put it that way, yes. There sure does need to be a reason to bother. > That's fair, I guess, but at the same time, what's the harm in > making the distinction?

[Mailman-Developers] Mailman headers roundup

Patrick Ben Koetter writes: > X-Mailman-Approved-At > lose the X-prefix > Modify to: List-Approved-Date > Next Step: Create RFC or Extend RFC 2369? New RFC. Once you get to the RFC stage, you don't modify them (even for typos, they publish errata). > X-Topics > This co

Re: [Mailman-Developers] New RFC on using DKIM with MLMs

Ian Eiloart writes: > Good point. I'd argue that the list manager, and the archiver > should simply do that: put a received header into the message at > the appropriate point. That would make it much easier to track the > message progress. I don't have a strong opinion on whether or not that'

Re: [Mailman-Developers] Mailman headers roundup

Barry Warsaw writes: > On Nov 10, 2011, at 02:17 PM, C Nulk wrote: > > >I understand what you are saying. To me "Mediator" doesn't describe the > >same information specifically because it is too general in meaning. > >"List-Agent" as the header makes sense to me. Mediator generalizes across

Re: [Mailman-Developers] New RFC on using DKIM with MLMs

Barry Warsaw writes: > On Oct 29, 2011, at 06:39 AM, Patrick Ben Koetter wrote: > > >I suggest we use the term 'Mediator' as introduced by D. Crocker in RFC 5598 > > instead: [...] > > That makes a good case for Mediator. +1, but only for the

Re: [Mailman-Developers] Mailman headers roundup

Murray S. Kucherawy writes: > However, the IETF might want to change it to the opposite name from > the one you pick, or even something else. So you're quite possibly > going to repeat this debate in their forum, so save (some of) your > strength. Or the posts. ;-) _

[Mailman-Developers] building/running alpha 8 on MacOS

Felipe Gasper writes: > Does buildout not work on MacOS? It worked for me in the past, so if it doesn't work for you there's a bug somewhere that needs fixing. ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/ma

Re: [Mailman-Developers] feature request: one-click setting to preserve DKIM

Barry Warsaw writes: > My own personal feeling is that having lists re-sign messages is the best > expectation to put forward. You're subscribed to a mailing list, so you > trust > that list much more than you trust the senders on that list. But as Monica points out, sometimes you need to e

Re: [Mailman-Developers] Mailman gone social ?

Barry Warsaw writes: > On Jan 07, 2012, at 03:25 PM, Marc Manthey (macbroadcast ) wrote: > > >Most of us are subscribted to several mailinglists, forums , irc andusing > >socialmedia sites like facebook and/ or twitter. > > I've long thought that there are enough overlaps with mailing > l

Re: [Mailman-Developers] Browser ID integration with Mailman

Florian Fuchs writes: > Agreed. Django's User model most definitely covers all our > needs. What version of Django's User model are you using? The vanilla User is actually rather limited. Or do you mean as augmented by UserProfiles? If the latter, do you have a specific schema for the Profil

Re: [Mailman-Developers] Pycon 2012 and Mailman 3 plans

Toshio Kuratomi writes: > On Mon, Mar 05, 2012 at 02:23:04PM -0500, Barry Warsaw wrote: > > - Possibly, make progress on the next-gen archiver. > > > Greetings, I'l be there and looking to talk with some people about this. I'll be there, and I'm definitely interested in the archiver. While

Re: [Mailman-Developers] Pycon 2012 sprint start time

rchive.com/mailman-developers%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-developers/stephen%40xemacs.org > > Security Policy: http://wiki.list.org/x/QIA9 > ___ Mailman-Developers mailing list Mailman-Develope

Re: [Mailman-Developers] bugs on launchpad

On Sat, Mar 17, 2012 at 3:05 AM, Andrea Crotti wrote: > Hi everyone, > I filed in two bugs today: > https://bugs.launchpad.net/mailman/+bug/956889 > https://bugs.launchpad.net/mailman/+bug/956384 These are both policy issues, I think they should be posted to the list as well as filed on Launchpad

Re: [Mailman-Developers] Grackle archive framework

On Sun, Mar 18, 2012 at 2:25 PM, Aamir Khan wrote: > As for searching the archive, there are solutions like Elastic Search, > Solr, lucene. Can we use one of them to search directly through the maildir. Not quickly. Many archives will have thousands of messages, some will have hundreds of thous

Re: [Mailman-Developers] Thoughts on processing for pre-approved messages

On Sat, Mar 17, 2012 at 2:41 AM, Mark Sapiro wrote: > I've gone around a bit on this and I've concluded this is analogous to > the list poster password I implemented for 2.1. Presumably we don't > want to allow this password to be used to authenticate to the web ui. Right. > We may want to allo

Re: [Mailman-Developers] Thoughts on processing for pre-approved messages

On Mon, Mar 19, 2012 at 2:59 AM, Mark Sapiro wrote: > If that were all that was required, that would be fine. The problem is > that we allow approval via a pseudo-header as the first non-blank body > line in the first text/plain part of the message, and we have to look > for it there and if found

Re: [Mailman-Developers] bugs on launchpad

On Fri, Mar 23, 2012 at 1:09 AM, Barry Warsaw wrote: > If we add something like $archive_url to the decoration interpolation > dictionary, what happens when we have multiple archivers that support > permalink() enabled?  Do we chose one at random (these are unordered)? -1 > Do we add a configur

Re: [Mailman-Developers] bugs on launchpad

man/listinfo/mailman-developers > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: > http://www.mail-archive.com/mailman-developers%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-developers/stephen%40xemacs.org > > Security Policy

Re: [Mailman-Developers] python 3

On Sat, Mar 24, 2012 at 12:15 AM, Barry Warsaw wrote: > Not all of that will be needed.  For example, I do want to eventually get rid > of zc.buildout, zope.testing, and zope.testrunner, so some of those > dependencies will go away as a result of that. But presumably new dependencies will be adde

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1

On Sat, Mar 24, 2012 at 3:00 AM, Barry Warsaw wrote: > Hello Mailman enthusiasts! > I'm also ecstatic to announce the first alpha release of Postorius, our new > official name for the Django-based Mailman 3 web user interface.  The name was > suggested by core developer Florian Fuchs in honor of

Re: [Mailman-Developers] any interest in a new built-in web-archive? (i.e. pipermail replacement)

On Tue, Mar 27, 2012 at 7:20 AM, David Jeske wrote: > I'm writing to find out the state of and philosophy surrounding pipermail > in mailman, There's been a lot of discussion of this over the years; you should spend some time in the mailman-developers and mailman-users archives looking for it, be

Re: [Mailman-Developers] any interest in a new built-in web-archive? (i.e. pipermail replacement)

On Tue, Mar 27, 2012 at 9:11 AM, Toshio Kuratomi wrote: > On Mon, Mar 26, 2012 at 03:20:05PM -0700, David Jeske wrote: > As I was talking about hyperkitty we touched briefly on > what I think is one of the central conundrums about having only unofficial > third party archivers:  how to have a con

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1

ting of the docs for the beta. I haven't merged with the release code yet, so maybe there will be conflicts, but the work is at lp:~stephen-xemacs/mailman/beta1-docs Highlights: - s/alpha/beta/ as appropriate A few of the instructions have changed slightly, eg, docs are now built wit

Re: [Mailman-Developers] Need guidance to start contributing to Mailman

On Mon, Mar 26, 2012 at 6:45 AM, Sidharth Bansal wrote: > Hello Mailman Developers, >  Sorry in advance if this is not the right place for my query. > I wanted to start contributing to Mailman-Development, and wanted a little > head start for that. I would love to get any sort of guidance in this

Re: [Mailman-Developers] any interest in a new built-in web-archive? (i.e. pipermail replacement)

On Tue, Mar 27, 2012 at 2:37 PM, David Jeske wrote: > Can you share something about dependency philosophy (besides licensing) in > Mailman? Well, for the official poop you'll have to wait for Barry, but AFAICS archivers aren't restricted to Storm + RESTish (which is what Mailman itself uses) bec

Re: [Mailman-Developers] Google Summer of Code: Integration of Search Code

On Wed, Mar 28, 2012 at 4:21 AM, Terri Oda wrote: >> Looks like archiver for mm3 is still in development stage. As far as I >> understand searcher depends on the srchiver, right? Not completely but it >> somewhat depends on archiver. I am not sure if searcher can be implemented >> without archive

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 andPostorius 1.0 alpha 1

On Wed, Mar 28, 2012 at 9:20 AM, Jeff Breidenbach wrote: >> archivers are configured site-wide, so there's almost nothing >> to expose in the web-ui. > > I'm worried about confusion. Indeed. I think Barry misspoke here. But remember, we're barely out of alpha test, and we don't actually have a

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1

On Thu, Mar 29, 2012 at 1:40 AM, Odhiambo Washington wrote: > However, I am lost as to why the argument to this procedure was named > "syncdb" and not "createdb", which is what it's doing. Can you explain that > please? Sorry, I am a noob in this. It's called "syncdb" because it synchronizes the

Re: [Mailman-Developers] GSoC

On Thu, Mar 29, 2012 at 4:59 AM, Florian Fuchs wrote: > Hi Ana, > > Am 26.03.12 19:03, schrieb Ana Cutillas: >> Hi, >> >> my name is Ana Cutillas and I am a senior Computer Science student from >> Spain. I am really interested in working on the Mailman project either with >> you directly or with S

Re: [Mailman-Developers] Google Summer of Code: Integration of Search Code

On Thu, Mar 29, 2012 at 8:07 AM, Barry Warsaw wrote: > Mailman 3 itself requires unique Message-IDs. So? FWIW, I don't think I agree with that requirement (even RFC 5322 doesn't make it a "MUST"), but I'm not going to argue with you about Mailman 3 design, that's your pidgin. But there's nothi

Re: [Mailman-Developers] mailman / archive-ui / licensing questions

On Thu, Mar 29, 2012 at 1:00 PM, David Jeske wrote: > I started to talk to one of them about installing CSLA (or MHonArc, or > anything really), and realized I should see if you folks are interested in > a great bundled archiver, I'm personally interested, but that's not going to be the main foc

Re: [Mailman-Developers] any interest in a new built-in web-archive? (i.e. pipermail replacement)

On Thu, Mar 29, 2012 at 4:04 PM, David Jeske wrote: >> - Merging of forums, archives, newsgroups, and IMAP. > > You like to bite off the big ones eh? NNTP, then IMAP. > > Does anyone even use fat-mail-clients anymore? Yes, and yes. But I don't think anybody has really thought carefully about the

Re: [Mailman-Developers] Google Summer of Code: Integration of Search Code

Barry writes: > I suspect that there will be plenty of mailing lists that get fed > messages from programs, e.g. think vcs -commit diff lists.  Those programs can > also be buggy, but again I'd prefer that Mailman not compromise on this issue > for their sake. I predict you will eventually l

Re: [Mailman-Developers] Google Summer of Code: Integration of Search Code

On Fri, Mar 30, 2012 at 3:55 AM, Shayan Md wrote: > Assuming that we have something like this(object-ID-addressable, If I am > not wrong, mailman3 made it possible but not yet implemented as it's part > of archiver), is it over ambitious to plan to implement indexer/searcher > for mailman3 and a

Re: [Mailman-Developers] Google Summer of Code: Integration of Search Code

On Fri, Mar 30, 2012 at 12:24 PM, Shayan Md wrote: > On Fri, Mar 30, 2012 at 5:05 AM, Stephen J. Turnbull > wrote: >> And (2) search and retrieval may >> do a *lot* of message access, for example if you want to do data >> mining (see Ana from Spain's thread). &g

Re: [Mailman-Developers] GSoC

On Thu, Mar 29, 2012 at 5:48 PM, Pierre-Yves Chibon wrote: > For the record, the current version of HyperKitty has moved from a > notmuch backend to a mongo database allowing a much more flexible data > storage scheme. Good to know! Is the source available? _

Re: [Mailman-Developers] mailman / archive-ui / licensing questions

On Wed, Apr 4, 2012 at 1:16 PM, David Jeske wrote: > On Apr 3, 2012 8:14 PM, "Bob Puff" wrote: >> I think the majority of MM users will be simply using the RPM that comes with >> their distro, and there is a real benefit to stuff working right "out of the >> box".  This includes the Archiving fu

Re: [Mailman-Developers] mailman / archive-ui / licensing questions

On Wed, Apr 4, 2012 at 3:58 AM, Toshio Kuratomi wrote: > From the talk about what it means to be a FSF project at the mailman sprint > at pycon I don't think a non-FSF copyright assigned archiver would be > bundled into mailman (Core). AFAIK there are no "FSF projects", although the FSF does sup

Re: [Mailman-Developers] mailman / archive-ui / licensing questions

On Wed, Apr 4, 2012 at 3:56 PM, David Jeske wrote: > ...this discussion is all just about whether mailman wants to bundle (or > reference) near-future updates to this stuff. I was hoping that rather than > create my own separate OSS-y website and such for it, I could just hang out > here and roll

Re: [Mailman-Developers] From the creation of a ThreadID

On Thu, Apr 5, 2012 at 10:41 PM, Pierre-Yves Chibon wrote: > In HyperKitty to be able to easily retrieve from the database all the > threads of a given month or just all the emails of a thread, I created a > Field in the database called ThreadID. > When I load the archives from mailman into mongo

Re: [Mailman-Developers] From the creation of a ThreadID

On Fri, Apr 6, 2012 at 3:42 AM, Pierre-Yves Chibon wrote: > So when it parses the email, it checks for 'References' or > 'In-Reply-To'. > - If it finds them, it looks for the preceding email >    - if it finds the preceding email, then the current email gets the > ThreadID from the preceding emai

Re: [Mailman-Developers] From the creation of a ThreadID

Bill Janssen has one too, I forget it it's based on amk's or not, but it's current. See thread in email-sig: http://mail.python.org/pipermail/email-sig/2012-January/000882.html On Sat, Apr 7, 2012 at 2:54 AM, Toshio Kuratomi wrote: > On Fri, Apr 06, 2012 at 12:10:22A

Re: [Mailman-Developers] From the creation of a ThreadID

On Sun, Apr 8, 2012 at 2:53 PM, David Jeske wrote: > Perhaps I misunderstood. If you are going to have a record of the deletion > (i.e. you can keep a deleted message around in some form), this problem > becomes much easier. In practice, complete deletion is occasionally necessary. The archives

Re: [Mailman-Developers] mailman / archive-ui / licensing questions

On Mon, Apr 9, 2012 at 8:27 AM, Blake Winton wrote: > On 08-04-12 19:24 , Mark Sapiro wrote: >> >> On 04/08/2012 04:14 PM, Blake Winton wrote: >>> >>> Would it work for everyone if David licensed the archiver to Mailman >>> under the GPLv3+? >> >> It won't work for David. > > Well, that's not exac

Re: [Mailman-Developers] mailman / archive-ui / licensing questions

On Mon, Apr 9, 2012 at 6:48 AM, Barry Warsaw wrote: > On Apr 02, 2012, at 08:04 PM, David Jeske wrote: > Probably the only way I'd change my mind about that is if RMS personally told > us that we could still treat the non-copyleft donation the same way we treat > all the other code, i.e. we can us

Re: [Mailman-Developers] From the creation of a ThreadID

On Mon, Apr 9, 2012 at 7:29 AM, Barry Warsaw wrote: > On Apr 08, 2012, at 01:11 PM, Richard Wackerbarth wrote: > >>I would propose a slightly different scheme for converting messages to stable >>URIs.. >> >>If we create our ID by concatenation of some hash and a part of the date, >>then the mail s

Re: [Mailman-Developers] From the creation of a ThreadID

On Tue, Apr 10, 2012 at 12:28 AM, Barry Warsaw wrote: > On Apr 09, 2012, at 07:10 AM, Richard Wackerbarth wrote: > >>I support the concept of Stable URI. > > Should we attempt to push the stable URI concept as an RFC?  Does anybody > (Murray perhaps) have the interest and time to do that?  I think

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

On Thu, Apr 19, 2012 at 5:03 AM, Barry Warsaw wrote: >  - Proposal is to append the List-Post value as input to the hash, after >   the Message-ID value (sans angle brackets). First, List-POST, not List-ID? List-Post is not permanent! Second, that order is wrong IMHO; the idea of the hash is t

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

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) > extractable from the hash, but instead just needs to inform the hash value. > IOW, if you

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

On Sat, Apr 21, 2012 at 5:19 AM, Jeff Breidenbach wrote: > 2) The reason mail-archive.com uses List-Post and not List-Id in the > calculation is because every list, RFC2369 compliant or not, has a > concept of a posting address. That would be fine, except that in my personal practice for some li

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

On Mon, Apr 23, 2012 at 7:31 AM, Jeff Breidenbach wrote: > I find List-Id annoying because I like the world to be simple and easy to > understand. 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

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

On Tue, Apr 24, 2012 at 7:20 AM, Barry Warsaw wrote: > 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.

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

velopers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: > http://www.mail-archive.com/mailman-developers%40python.org/ > Unsubscribe: > http://mail.pyt

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

Thanks! On Wed, Apr 25, 2012 at 2:50 AM, Jeff Breidenbach wrote: >> 0. Assume a 10 million message archive. >> 1. What percentage of permalinks need another click? >> 2. What percentage of permalinks will result in a list of more than 10 >> matches? > > Ignoring cross posts, for a 4 character ha

Re: [Mailman-Developers] no documentation for Mailman 3.0

This procedure has changed since the alphas but I guess the install doc hasn't been patched yet. python setup.py build_sphinx On Thu, May 3, 2012 at 12:00 PM, David wrote: > Build the online docs by running:: > >    % bin/docs ___ Mailman-Developers ma

Re: [Mailman-Developers] Error: Couldn't install: storm 0.19

On Thu, May 3, 2012 at 11:57 AM, David wrote: > Is this the right place for a suggestion on minor documentation changes? > I actually needed build-essential and python-dev packages in addition to > the python package that came with the default Ubuntu install on Linode. Ubuntu is popular, but no

Re: [Mailman-Developers] where to install Mailman?

On Thu, May 3, 2012 at 12:37 PM, David wrote: > I know this is possibly both a stupid question and one that is subject to > endless debate in the larger scope... but strictly from a Mailman point of > view, where should I install Mailman 3.0? The short answer is "Anywhere, as long as the relativ

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

Hi George, Thanks for the report! A couple of quick comments: On Thu, May 3, 2012 at 8:04 AM, George Chatzisofroniou wrote: > I’m also thinking to rearrange the GSoC schedule a bit. I’ll start > writing code on the bonding period, It's up to your coding mentors, but it's generally not a good

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

Richard Wackerbarth writes: > I will take the blame for any misunderstanding in this area. There's no blame to be assigned, really, unless to me for being a busybody. :-) If George is making these plans while consulting his mentor, that's what this is all about (but he didn't say that, so I stu

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

Richard Wackerbarth writes: > Usually, a few people, who think that they understand the whole > problem, make early design decisions that often become obstacles in > the future. It is only after the prototype has been developed that > others are able to point out weaknesses in the initial desi

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

George Chatzisofroniou writes: > > It's not clear to me why year views can't be generated as an aggregate > > of monthly data?  This would allow years to start with arbitrary > > months without too much redundancy. > > Generating the year views from monthly data is some more calculations >

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

Terri Oda writes: > So... If AJAX is the fastest way to get some initial prototypes going, > that's a good place to start. As the author of the original suggestion about AJAXing the charts, I don't actually think it is the easiest way. I think it's easier to just generate a fixed-size chart a

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

George Chatzisofroniou writes: > Author > > This model represents an author of the mailing list. It mostly keeps > track of the number of postings and number of threads started. It has > the following fields: > > - authorid – IntegerField AFAIK every Django object has an internal ID. W

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

George Chatzisofroniou writes: > Hello Patrick, > > On Fri, May 18, 2012 at 12:09 AM, Patrick Ben Koetter > wrote: > > Like with most statistical data I mostly see the figures being > > used to give statements on quantity - top poster, number of > > threads etc. Do you think it would be po

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

Barry Warsaw writes: > I personally think that rebase is an abomination generally required > by workflow policies that try to overcome tool deficiencies. By > not *requiring* rebase (it is of course possible), it means that > all your intermediate commits are preserved No VCS "requires" reba

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

Richard Wackerbarth writes: > Having a main branch implies that the organization is imposing its > idea of "the right way". In some sense true, but few organizations have either the resources or inclination to maintain and support more than one "right way" at a time. > History shows that part

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

Barry Warsaw writes: > 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: > >No VCS "requires" rebase, or removing co

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

Richard Wackerbarth writes: > I believe that it may be your intention to have kept "postorius" > hidden. But I don't think that the actual implementation has > accomplished that. > > Please see ~mailman-coders/postorius/trunk : > /src/postorius/templates/postorius/base.html (revision 65) at

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

Richard Wackerbarth writes: > Yes, but one of the design points of Django is that, without a > great deal of effort, the user can customize his site URLs in any > manner. Further, doing so follows the DRY principle. Embedding the > actual text stream "/postorius/" in templates, particularly >

[Mailman-Developers] HyperKitty login

Aamir Khan writes: > Hi everybody! > > First task I am going to do for my GSoC project is to have login > authentication mechanism for HyperKitty users. I have had discussion with > few mailman developers about it. I am planning to wrap up social_auth into > mm_ui_auth django application. Bo

Re: [Mailman-Developers] HyperKitty login

Richard Wackerbarth writes: > Stephen, > > "social_auth" is a django "app" (Think library) that handles > OpenID, BrowserID, Google, Twitter, etc. authentication. Yeah, I think all the mentors and most of the other subscribers here can figure that out. The

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

Richard Wackerbarth writes: > The current design of the Postorius and Hyperkitty web interfaces > to the mailing list and its archives uses the fully qualified list > submission email address as a component of the URLs presented to > the public. > > I fear that doing this will create an eve

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

Barry Warsaw writes: > hashing the mlist fqdn and taking a substring would probably be good enough. Eww! -1 ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FA

[Mailman-Developers] Trying to install mm 3.0.0b1

Lindsay Haisley writes: > pkg_resources.DistributionNotFound: zc.buildout==1.5.2 Butbutbutbutbut: > ii python-zc.buildout 1.5.2-1 > system for managing development buildouts Hm. I suspect that Debian has installed zc.buildout for a different vers

Re: [Mailman-Developers] Twisted NNTP

Alexander Sulfrian writes: > RFC 3977 explicit requires the CAPABILITIES command to work for > conformance. It should not be hard to implement it, so in my opinion > it should be listed as required. Sure, but please remember that *you* have a deadline. When you write up requirements, make sur

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

Note: CC'ing Mailman Developers. I think this was private, so not trimming. At the bottom there's a discussion of the newsgroup naming scheme, which is an important bikeshed to paint. If you're not interested in a bunch of "me too" comments, skipp right on down there! Barry Warsaw writes: > Hi

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

Ian Eiloart writes: > OK. Where do these two email addresses sit? Addresses aren't relevant. I proposed using List-Ids, which have to be unique (RFC 2919). If an administrator specifies List-Ids that collide, that's not our problem. (The author of RFC 2919 was aware of similar problems, thoug

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

I don't think Terri needs a cc, if she's not on mm-d. Barry Warsaw writes: > >The top-level maybe shouldn't be "mailman", but rather something like > >"list-archive". > > Why is the prefix needed at all, especially since you qualified this as "not > gatewayed to Usenet"? If all the message

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

Barry Warsaw writes: > Should the prefix [for the "archived news hierarchy"] be > configurable then? Yes, but once we figure out what it "should" be, admins should be strongly advised not to change the prefix if they allow mirrors. ___ Mailman-Develo

[Mailman-Developers] Bug 971013 - schema migrations BLOCKED

Barry Warsaw writes: > What's blocking progress is SQLite, [which] has a very limited > ALTER TABLE command, and specifically does not support column > renaming or deleting. This really sucks for implementing any kind > of schema migration, regardless of the framework. So it's the renaming t

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

Danci Emanuel writes: > After all I managed to fix this one also. The problem was that mailman was  > trying to access  /var/data/mailman.db, which did not contain > the dlists_enabled column, so it was seeing it as a "corrupt" file. > I just deleted it, restarted mailman and it`s working grea

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

Richard Wackerbarth writes: > I am encountering a problem with login on Postorius. There is no > mechanism to keep the MM user database synchronized to the one > which django creates. Since Postorius is the facility by which admins will expect to access the user database, I have to consider th

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

Richard Wackerbarth writes: > Since by far the most complicated, and most used, logins will be > made from the web interface, it is much more logical to allow > Postorius to be responsible for all of the user profile information > and have the core, on those rare occasions where it requires it

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

Richard Wackerbarth writes: > What I am advocating is that the "core" message handler NOT be the > keeper of ONLY PART of it. What I'm advocating (mildly, because somebody else is going to have to do the work) is that the core be the keeper of ALL of it. The core is not just a "message handler

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

Florian Fuchs writes: > But I also agree with Terri that there might be a good amount of user > data used by Postorius, Hyperkitty or any other web ui/client that just > doesn't have anything to do with mailman's core tasks. And I don't see > why something like "preferred ui theme" or profile-

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

Richard Wackerbarth writes: > Pretty soon, you will find that what you need approaches something > that already exists -- a relational database. Rather than > "reinventing the wheel", we should just use an already existing > database system and make all of the data directly accessible. We're

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

Richard Wackerbarth writes: > 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. AFAIK the plan is to do that via the REST interface. I don't see why they need to be "arbit

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

Richard Wackerbarth writes: > 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, this would be some kin

Re: [Mailman-Developers] USE_ENVELOPE_SENDER is not flexible enough

> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes: BAW> BAW> Mailman shall rule THE WORLD! BAW> Take a number, man. (See .sig.) -- University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (29

Re: [Mailman-Developers] Interesting study -- spam onpostedaddresses...

> "Chuq" == Chuq Von Rospach <[EMAIL PROTECTED]> writes: Chuq> Are there any other benefits to being googled than being a Chuq> walking billboard to the list? Yes. I do see a fair number of "non-subscriber" posts that go "we need to do job X, and according to a post I dug up googlin

Re: [Mailman-Developers] Interesting study -- spam onpostedaddresses...

> "Chuq" == Chuq Von Rospach <[EMAIL PROTECTED]> writes: Chuq> But -- I hate to be bullheaded about this, but I will be -- Chuq> how does this benefit YOUR LIST? Yes, it benefits others, Chuq> and there's some value to that, but does it actually add Chuq> value to your list? E

Re: [Mailman-Developers] Interesting study -- spam onpostedaddresses...

> "Chuq" == Chuq Von Rospach <[EMAIL PROTECTED]> writes: Chuq> On 2/20/02 1:37 PM, "Damien Morton" Chuq> <[EMAIL PROTECTED]> wrote: >> As far as I can see thay are using url/cgi encoding in the >> email address. This is trivial to circumvent, as is using html >> entities,

Re: [Mailman-Developers] Save the world from spam

> "Chuq" == Chuq Von Rospach <[EMAIL PROTECTED]> writes: Chuq> You know, now that I think of it, there's another approach: Chuq> you don't get the admin's email address until you Chuq> authenticate. Then you get it. [...] Chuq> Thoughts? You've just reinvented TMDA, basicall

Re: [Mailman-Developers] Interesting study -- spam on postedaddresses...

I repeat myself, but only Chuq seems to have noticed the other post. > "John" == John Morton <[EMAIL PROTECTED]> writes: John> This depends on just how temporary your 'solution' turns out John> to be, and it's level of complexity and usability. I don't John> think anyone has real

Re: [Mailman-Developers] Interesting study -- spam on postedaddresses...

> "Damien" == Damien Morton <[EMAIL PROTECTED]> writes: Damien> So obfuscation is imperfect, and the more effective it is, Damien> the more value there is in cracking it. That's true, but that's not what I said. What I said is it is weak enough that a small amount of effort brings s

Re: [Mailman-Developers] Protecting email addresses from spam harvesters

> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes: BAW> I /think/ I've caught up on this thread, Like JRA I think your synopsis is accurate, with respect to the issues that can be addressed by code. BAW> I claim that the guessability [of list-related addresses] is BAW> a feat

Re: [Mailman-Developers] Protecting email addresses from spam harvesters

> "John" == John Morton <[EMAIL PROTECTED]> writes: John> I find this feature is handy for small, private lists. Sure. I have a couple that could be handled that way, but we just defaulted them all off. We post the names and addresses (they're basically lists of project staff) on the h

Re: [Mailman-Developers] Protecting email addresses from spam harvesters

> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes: BAW> Yeah, it's just that I generally hate cookies too. So call them [Kerberos] "tickets". (Me like cookies, one, two, I put them away now. Tickets have no flavor and are hard to chew.) You aren't going to make cookies go away, bec

<    6   7   8   9   10   11   12   >