listservs, forums and Zope...
Hi... I'm wondering if anyone has done anything along the lines of creating an interface between an email list product such as listserv or majordomo and Zope... I'm setting up a small intranet site using Zope and trying to figure out if there's an easy way to integrate our existing majordomo lists with the new Zope site. If one of the Zope forum products had an option for email notification, that would go a long way towards solving the problem-- but it doesn't seem like any provide this function at present. Alternatively, if there were a product that could accept an email message and create a message archive (ala hypermail), that would be great too... I'm not yet familiar with Zope and python to create something like this myself easily, but it seems to be a fairly simple thing. any ideas would be appreciated... Larry + Larry J. Prikockis Web Applications Specialist Association for Biodiversity Information 703-908-1833 / larry_prikockis@abi.org / www.abi.org + All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can't get them together again, there must be a reason. By all means, do not use a hammer. -- IBM maintenance manual, 1925
On Thu, May 10, 2001 at 02:36:12PM -0400, Larry Prikockis wrote:
I'm wondering if anyone has done anything along the lines of creating an interface between an email list product such as listserv or majordomo and Zope...
Don't know what it'll do for you exactly, but check out http://www.zope.org/Members/NIP/ZMailIn -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu
On Thu, 10 May 2001, Larry Prikockis wrote:
Hi... I'm wondering if anyone has done anything along the lines of creating an interface between an email list product such as listserv or majordomo and Zope... I'm setting up a small intranet site using Zope and trying to figure out if there's an easy way to integrate our existing majordomo lists with the new Zope site.
If one of the Zope forum products had an option for email notification, that would go a long way towards solving the problem-- but it doesn't seem like any provide this function at present. Alternatively, if there were a product that could accept an email message and create a message archive (ala hypermail), that would be great too... I'm not yet familiar with Zope and python to create something like this myself easily, but it seems to be a fairly simple thing.
We use mailman, which is, IMHO, much easier to administer than majordomo, and much less expensive than Listserv. Mailman isn't a Zope product per se, but it is programmed in python, and it's stuff is stored in python marshalled data, so it's fairly easy to get at. If I can offer specific help on places you're stuck, let me know. -- Joel Burton <jburton@scw.org> Director of Information Systems, Support Center of Washington
Did you see the code Ken Manheimer posted last year? There might be very useful stuff in there... On July 6, 2000, Ken Manheimer wrote:
... One of the first things zope exercises i did when learning zope, not tool long after coming to digital creations, was create a product that hooked up with the Mailman installation on zope.org. (One of the last things i did at my prior job, at CNRI, was to resurrect and revitalize the prototype Mailman, for use as the maillist manager on python.org.)
I moved on to other things, and the MMRoster product may be way out of date - i don't even know if the mailman interfaces have changed from underneath, and i *know* that the zope ones have - but the product still may offer some useful clues about one way to hook up with mailman. I just uploaded a tarball of it to my members folder - see
http://www.zope.org/Members/klm/MailmanStuff/MMRoster.tar.gz
(I know ethan is interested in this topic, and barry warsaw, mailman's current maintainer and my old colleague/buddy, has also expressed interest, so i'm cc'ing them.)
All this said, i'm spread too thin at the moment to be able to *do* much more than watch, maybe chime in, if stuff happens...
...
hth a little, Danny
-----Ursprungliche Nachricht----- Von: zope-admin@zope.org [mailto:zope-admin@zope.org]Im Auftrag von Joel Burton Gesendet: Freitag, 11. Mai 2001 07.03 An: Larry Prikockis Cc: 'zope@zope.org' Betreff: Re: [Zope] listservs, forums and Zope...
On Thu, 10 May 2001, Larry Prikockis wrote:
Hi... I'm wondering if anyone has done anything along the lines of creating an interface between an email list product such as listserv or majordomo and Zope... I'm setting up a small intranet site using Zope and trying to figure out if there's an easy way to integrate our existing majordomo lists with the new Zope site.
If one of the Zope forum products had an option for email notification, that would go a long way towards solving the problem-- but it doesn't seem like any provide this function at present. Alternatively, if there were a product that could accept an email message and create a message archive (ala hypermail), that would be great too... I'm not yet familiar with Zope and python to create something like this myself easily, but it seems to be a fairly simple thing.
We use mailman, which is, IMHO, much easier to administer than majordomo, and much less expensive than Listserv.
Mailman isn't a Zope product per se, but it is programmed in python, and it's stuff is stored in python marshalled data, so it's fairly easy to get at.
If I can offer specific help on places you're stuck, let me know.
-- Joel Burton <jburton@scw.org> Director of Information Systems, Support Center of Washington
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
"JB" == Joel Burton <jburton@scw.org> writes:
JB> We use mailman, which is, IMHO, much easier to administer than JB> majordomo, and much less expensive than Listserv. That's great to hear! :) JB> Mailman isn't a Zope product per se, but it is programmed in JB> python, and it's stuff is stored in python marshalled data, so JB> it's fairly easy to get at. JB> If I can offer specific help on places you're stuck, let me JB> know. Given that a former and current Mailman developer both work for DC, there's a darn good chance that it will become easier and easier to integrate Mailman and Zope. I have plans for Mailman 3.0 to rewrite the underlying database code so that e.g. ZODB could be plugged in instead of the homegrown, hardwired marshaling approach. I also have plans for writing interfaces so that authentication and memberships can be handed off to external (to Mailman) processes, e.g. Zope and CMF. And it would be cool if the UI could be pluggable too so that things like Presentation Templates or other Zope UI mechanisms can be used. Really, the grand plan for Mailman 3.0 is to sort of turn it inside out, so that it's a package of functionality that can be plugged into all sorts of other frameworks. Then there'll probably be a "Mailman classic" framework so that you can continue run it standalone if you want. Don't ask me when that'll happen, I've no idea. First I need to get the current 2.1 code base out of alpha so that there's a solid internationalized Mailman release (with, of course, lots of other wizzy new features :). Cheers, -Barry
Just my $0.02 - the topic of wanting Mailman integrated with Zope seems to come up often in the demos and presentations I've been giving out here in Southern California... <sigh> On Thu, May 10, 2001 at 11:18:14PM -0400, Barry A. Warsaw wrote:
"JB" == Joel Burton <jburton@scw.org> writes:
JB> We use mailman, which is, IMHO, much easier to administer than JB> majordomo, and much less expensive than Listserv.
That's great to hear! :)
JB> Mailman isn't a Zope product per se, but it is programmed in JB> python, and it's stuff is stored in python marshalled data, so JB> it's fairly easy to get at.
JB> If I can offer specific help on places you're stuck, let me JB> know.
Given that a former and current Mailman developer both work for DC, there's a darn good chance that it will become easier and easier to integrate Mailman and Zope. I have plans for Mailman 3.0 to rewrite the underlying database code so that e.g. ZODB could be plugged in instead of the homegrown, hardwired marshaling approach. I also have plans for writing interfaces so that authentication and memberships can be handed off to external (to Mailman) processes, e.g. Zope and CMF. And it would be cool if the UI could be pluggable too so that things like Presentation Templates or other Zope UI mechanisms can be used.
Really, the grand plan for Mailman 3.0 is to sort of turn it inside out, so that it's a package of functionality that can be plugged into all sorts of other frameworks. Then there'll probably be a "Mailman classic" framework so that you can continue run it standalone if you want.
Don't ask me when that'll happen, I've no idea. First I need to get the current 2.1 code base out of alpha so that there's a solid internationalized Mailman release (with, of course, lots of other wizzy new features :).
Cheers, -Barry
-- charlie blanchard http://baldguru.com/ LosAngeles area Zope Users Group http://lazug.org
From: "Barry A. Warsaw" <barry@digicool.com
Really, the grand plan for Mailman 3.0 is to sort of turn it inside out, so that it's a package of functionality that can be plugged into all sorts of other frameworks. Then there'll probably be a "Mailman classic" framework so that you can continue run it standalone if you want.
Don't ask me when that'll happen, I've no idea. First I need to get the current 2.1 code base out of alpha so that there's a solid internationalized Mailman release (with, of course, lots of other wizzy new features :).
I'd be very interested in looking into this, but I need some hints on where to start looking. Is there a description of how mailman works internally or is it just a question of finding tiume to "user the source, Luke"? Specifically, I'd like to start by getting users from a SQL database, and being able to dynamically changes what lists a user belongs to. This I need to couple to users, groups and roles in zope. Any hints? /dario
"DL" == Dario Lopez-Kästen <dario@ita.chalmers.se> writes:
DL> I'd be very interested in looking into this, but I need some DL> hints on where to start looking. Is there a description of how DL> mailman works internally or is it just a question of finding DL> tiume to "user the source, Luke"? Yup. DL> Specifically, I'd like to start by getting users from a SQL DL> database, and being able to dynamically changes what lists a DL> user belongs to. The primary thing to realize with Mailman 2.x is that each mailing list maintains its own membership rosters. You might be a member of both zope@zope.org and zodb-dev@zope.org, but there's no sharing of your account information between those two lists. It's likely that Mailman 2.1 will contain hooks on a per-list basis so that an individual mailing list can get additional membership information out of an external source. Federating the user database in the way you want is a Project for Mailman 3.0. -Barry
"Barry A. Warsaw" wrote:
Given that a former and current Mailman developer both work for DC, there's a darn good chance that it will become easier and easier to integrate Mailman and Zope.
Cool :-)
I have plans for Mailman 3.0 to rewrite the underlying database code so that e.g. ZODB could be plugged in instead of the homegrown, hardwired marshaling approach. I also have plans for writing interfaces so that authentication and memberships can be handed off to external (to Mailman) processes, e.g. Zope and CMF. And it would be cool if the UI could be pluggable too so that things like Presentation Templates or other Zope UI mechanisms can be used.
Really, the grand plan for Mailman 3.0 is to sort of turn it inside out, so that it's a package of functionality that can be plugged into all sorts of other frameworks. Then there'll probably be a "Mailman classic" framework so that you can continue run it standalone if you want.
What are the chances of Mailman becoming a 'Zope App'? Incidentally, on of the things I'm hoping for with Swishdot is to make it more of a cross between a weblog and a mailing list so I wonder if there's an opportunity for collaboration here? cheers, Chris
"CW" == Chris Withers <chrisw@nipltd.com> writes:
CW> What are the chances of Mailman becoming a 'Zope App'?
From conversations with Jim, it sounds like he wants to return to the days when it was really easy to take an arbitrary Python app, write a bit of adapter code, and suddenly it becomes a Zope application. In that sense, and with some of the pluggable architecture I'm contemplating for the future, I think it should happen.
OTOH, I don't want Mailman to be `just' a Zope app. The balance is in making it much easier for Zope and Mailman to be integrated without raising the entry bar for Mailman too high for non-Zope sites. CW> Incidentally, on of the things I'm hoping for with Swishdot is CW> to make it more of a cross between a weblog and a mailing list CW> so I wonder if there's an opportunity for collaboration here? Definitely! We should probably have that conversation on mailman-developers@python.org, or at least crosspost it. Don't forget about the Mailman wiki: http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage -Barry
participants (8)
-
barry＠digicool.com -
Charlie Blanchard -
Chris Withers -
Danny William Adair -
Dario Lopez-K�sten -
Joel Burton -
Larry Prikockis -
Mike Renfro