Re: [Mailman-Developers] PHP Wrappers?

Brad Knowles wrote: > If you look at the Mailman FAQ Wizard entries related to this > subject (and the threads that they link to), most of the useful > information regarding integration with CMSes, web board discussion > systems, etc... has come from Tobias Eigen at Kabissa and various > t

Re: [Mailman-Developers] Informal "MEP" process, anyone?

Stephen J. Turnbull wrote: >Kevin> Rather than look at what has been done in the way of >Kevin> patches I'd be more inclined to contribute toward a design >Kevin> for MM3. I have actually worked on the specs for a >Kevin> SQL-enabled MLM system, based on user and admin >Kevin>

Re: [Mailman-Developers] PHP Wrappers?

This is my last response to Brad's messages (actually *these* are diatribes if anything), and I only do so to make a few things clear: - I'm not begging for anything; I'd like to see some things come to fruition for the greater good. I have no personal stake in this, financial or otherwise. - I

Re: [Mailman-Developers] PHP Wrappers?

Ian Eiloart wrote: > Seems to me the big misunderstanding in this debate lies around the > differences between Mailman 2 and Mailman 3. As far as I can see, > they are big differences - of the sort that Kevin is looking for. > Unfortunately, they're not highly visible - probably due to the f

Re: [Mailman-Developers] PHP Wrappers?

Brad Knowles wrote: > > Mailman is not, and never will be, the be-all and end-all of > community collaboration tools. By necessity, those tools must be > all-encompassing, and mailing list management is just a small part of > the much greater picture. You can't just take a bunch of indepe

Re: [Mailman-Developers] Informal "MEP" process, anyone? [was: PHP Wrappers?]

Stephen J. Turnbull wrote: >On the other hand, the ad hoc DB integration ideas I've seen discussed >to date all have a very strong "works for me" flavor to them. Ie, "if >you want something generalizable, then MM people will have to do >that, but here's a proof of concept." > >Kevin> despite

Re: [Mailman-Developers] MM3?

Barry Warsaw wrote: >>I have been watching with anticipation, but it's been a while since I >>have heard anything on MM3. Any noteworthy updates? >> >> > >Sadly, no. My job has been incredible time consuming so I just haven't >had much time to work on MM3. If things go well, I have some pla

Re: [Mailman-Developers] PHP Wrappers?

Brad Knowles wrote: > The better integration with MySQL? No, that's definitely going to > happen. It may not happen as early as you (or Barry) would like, but > it will happen. > I'll believe that when I see it. > They're begging for this kind of stuff in the wrong places. There > a

Re: [Mailman-Developers] PHP Wrappers?

[EMAIL PROTECTED] wrote: >>Hello. How might one configure Mailman (version 2.1.6) list settings >>using PHP scripts? >> >> > >The quick answer would be to not bother and wait until version 3 of Mailman >which will use a MySQL backend and instead manipulate that directly (if I have >been r

Re: making Mailman CAN-SPAM compliant (was Re: [Mailman-Developers] Hashing member passwords in config.pck)

Tobias Eigen wrote: What I envision having in my Mailman/Mambo system is a single user database with one password per username for all services. Users can then go to a simple preferences page on Mambo and do basic things like change their email address or password, tick a box to opt in/out of

Re: [RETRANSMIT] Re: [Mailman-Developers] Debate about Mailman on BytesForAll

Brad Knowles wrote: At 4:10 PM -0400 2004-08-26, Dale Newfield wrote: The biggest problem with BerkeleyDB is that it REQUIRES that the file system support memory mapping the files. This means that you cannot guarantee correctness if these files are located on an NFS mount. True enough. Th

Re: [Mailman-Developers] Debate about Mailman on BytesForAll

Barry Warsaw wrote: On Thu, 2004-08-26 at 15:00, Kevin McCann wrote: That's great news, Barry. As you know, we're completely behind you and will do whatever we can from our end (people and money) to help a SQL-able MM3 become a reality. We'll be in touch. While we&#

Re: [Mailman-Developers] Debate about Mailman on BytesForAll

Barry Warsaw wrote: On Thu, 2004-08-26 at 14:38, Kevin McCann wrote: Of course, from my point of view, the discussion is really about Mailman 3.0 and future plans. ;-) And I must apologize for being so totally incommunicado these last few weeks. We have a very major release due at the

Re: [Mailman-Developers] Debate about Mailman on BytesForAll

Frederick Noronha (FN) wrote: Hello from India: I am a Free Software enthusiast and co-founder of BytesForAll.org Recently, there was an interesting debate taking place on our discussion list, about Mailman 2.0 and future plans. Many are users of Mailman, and I would request those developers with

Re: [Mailman-Developers] SF.net March 2004 POTM

Barry Warsaw wrote: Hey folks, quick note. Mailman's the March 2004 SourceForge.net project of the month. http://sourceforge.net/potm/potm-2004-03.php -Barry Congratulations, Barry (and to everyone else who has made Mailman possible). You have made a difference and the Sourceforge recognitio

[Mailman-Developers] SQL in MM3 issues

For those who are interested in working on a MySQL and/or Postgres backend end for Mailman 3, I'd like to get some feedback on *very basic* notions. First, for me, the whole reason I want to see this SQL thing happen is so that I can have the three primary data tables at my "SQL select" disposa

Re: [Mailman-Developers] AOL's requirements for spam complaints

Brad Knowles wrote: I've been looking at the requirements and potential performance you can get with Lyris ListManager, MailEngine, etc See and for the respe

Re: [Mailman-Developers] A bit of perspective ....

Chuq Von Rospach wrote: I've got a bit of MySQL background. My time is still limited, so I won't commit to coding I can't depend on myself to finish -- but if you want someone to help out on DB design and stuff, I'm in. I'll do what I can and maybe help avoid some of the potholes. I'd like to s

Re: [Mailman-Developers] A bit of perspective ....

I'll continue to look forward for solutions. there are always solutions. Not all of them are already packaged up and waiting to be found, or easily created through talk. I understand this, Chuq. For me, the most pressing thing is the SQL activity. And as I have mentioned, we're ready to contr

Re: [Mailman-Developers] AOL's requirements for spam complaints

Barry Warsaw wrote: So Kevin, you coming to PyconII? I still don't have (m)any volunteers joining me in a Mailman 3 sprint. :( -Barry Hi Barry, Thanks for you cordial and helpful response. If I can get up-to-speed with Python in order to work on the MySQL side of things, or if you think I

[Mailman-Developers] A bit of perspective ....

Maybe I ought to explain what I'm up against. At work I'm running Lyris. I have hundreds of lists and many, many members. I also have Mailman running a handful of small-ish lists (and at home I run a server with Mailman for a personal interest discussion list of nearly 1,000 members). My organ

Re: [Mailman-Developers] AOL's requirements for spam complaints

Brad Knowles wrote: There are some things that Barry has already ruled out. Writing a custom MTA for Mailman is one of those things. Don't even bother barking up this tree. Perhaps, for Mailman 3, Barry could talk to people like Eric Allman, Wietse Venema, and other solid MTA author

Re: [Mailman-Developers] AOL's requirements for spam complaints

Carson Gaspar wrote: If you'd read your own thread, you'd know the answer already. Lyris is its own MTA - it speaks SMTP directly to the recipients' mail servers. This allows it to do on-the-fly customization at SMTP transmit time instead of having to queue each unique message. Fair dues. I'll

[Mailman-Developers] Any SQL people going to Barry's sprint?

A while ago Barry posted a message about a Mailman 3 sprint which is to occur in March. I was wondering if any SQL (especially MySQL) people are planning to go. If you have strong Python and MySQL skills, please drop me a note. I'm trying to identify a candidate from among a few organizations

Re: [Mailman-Developers] AOL's requirements for spam complaints

Brad Knowles wrote: At 10:44 PM -0800 2004/01/29, Chuq Von Rospach wrote: Sorry, I don't buy this argument. If you have two choices: use more CPU time and network, or improve the end-user experience, choosing "less work for the computer" is almost always the wrong answer. You know damn

Re: [Mailman-Developers] Mysql MemberAdaptor update.

Hey K., Thanks for continuing this effort. I was wondering if you've given any more thought to my suggestion of adding the listname as a field in the table. That way you could have one larger table for members of all lists, not one table per list. Yes, people can take what you've done and crea

Re: [Mailman-Developers] SMART Archiver

> A week ago PieterB told me that there might be an interest in a replacement > archiver for pipermail that we created during a software engineering course. > That is why i put together a small demo and a homepage for the SMART > Archiver project. Fantastic work! I'd be very interested in helping

Re: [Mailman-Developers] Requirements for a new archiver

On Wed, 2003-10-29 at 10:13, Brad Knowles wrote: > At 3:06 PM -0500 2003/10/27, Kevin McCann wrote: > > > I was thinking about using MHonarc to enhance the archive experience but > > it doesn't work with MySQL directly so Mail::Box just might be what the > >

Re: [Mailman-Developers] Re: Requirements for a new archiver

> That's pretty much the ideological basis for what I have done. We have > message-delivery protocols, and tools that know about messages; why keep > trying to reinvent them over HTTP? There is a huge demand for web applications that use mailing list data. Mailing list archives in easily accessi

Re: [Mailman-Developers] Re: Requirements for a new archiver

On Tue, 2003-10-28 at 08:48, [EMAIL PROTECTED] wrote: > It's certainly possible to assemble a set of packages that provide a > featureful search, but does this raise the bar for installing Mailman too > much? SMARTarchiver would require that you have PostgreSQL; is adding that > dependency OK? B

Re: [Mailman-Developers] Requirements for a new archiver

Chuq said: > very unlikely for archives. And with mySQL 4, you can use one of the > newer formats with row locking and transactions. they do intermingle > nicely. Yes. MySQL can handle transactions just fine. For more info: http://www.mysql.com/doc/en/ANSI_diff_Transactions.html - Kevin ___

Re: [Mailman-Developers] Requirements for a new archiver

On Mon, 2003-10-27 at 15:12, Barry Warsaw wrote: > On Mon, 2003-10-27 at 15:06, Kevin McCann wrote: > > > To me, this is the single most important part. How do you intend to > > store the messages? > > > > Maybe others don't give a fig but I think that if arch

Re: [Mailman-Developers] Requirements for a new archiver

Iain said: >1. store email discussions. Iain, To me, this is the single most important part. How do you intend to store the messages? Maybe others don't give a fig but I think that if archived messages were to be stored in an easy-to-access database then life would be good. All of the wond

Re: [Mailman-Developers] "@" in mail **text** gets replaced inarchives

> This is seriously weird. Back before pipermail was integrated > into mailman, my understanding is that the then-current version was > the best available MLM archive tool, heads and shoulders above > everything else -- especially mhonarc. Moreover, my understanding > was that pipermail had only

Re: [Mailman-Developers] "@" in mail **text** gets replaced inarchives

> Dump pipermail completely and include (or point to) MHonARC, it does a great > job and is easily integrated (UTF-8 support and all). I agree. Earl Hood has been doing a marvelous job with MHonarc for years now. The guy is meticulous, keeps his software current and well documented, and understa

Re: [Mailman-Developers] Trivial mm wording nit

> "was" connotes that an action happened in the past and is over and done > with. "has been" connotes that the action was started, but might not have > completed. I disagree. To me, the sentence with "was" gives the impression that it just simply happened. The sentence with "has been" seems more

Re: [Mailman-Developers] Interfacing to Mailman data

On Wed, 2003-07-30 at 13:38, Chris Boulter wrote: > On Mon 2003-07-28 11:29:52 -0400, Kevin McCann wrote: > > A while ago I mentioned that I was interfacing with Mailman (via PHP) by > > issuing the /bin commands and parsing the results. > > I get the feeling a lot of

[Mailman-Developers] Interfacing to Mailman data

'm not a Python programmer yet but I'm willing to become one to get these kinds of things to happen. Could you help me get started by indicating what files I would need to copy and then modify to, say, create an interface-friendly version of list_li

Re: [Mailman-Developers] Storing additional user data

Chuq's right on the money here. I'd be happy to do stuff on the PHP interface side. This would allow connectivity with PHP-Nuke, Postnuke, Xaraya, and any other PHP-based CMS. Barry, continuing our recent conversation, I'd be happy to try to do something on the PHP side but I'll need to get some p

[Mailman-Developers] MySQL Support? Do tell!

Barry, you mentioned that Mailman can work with MySQL, just not "out of the box." Can you expound on this? Or can anyone else? I'm about to do a lot of R&D in this area and would like to tap into what other people know so far. Are we talking about data synching here, or is there a way to get M