[Mailman-Developers] Storing additional user data

[David Birnbaum]

On Thu, 10 Jul 2003, Barry Warsaw wrote:

> > It's easy enough to add members to the list and remove them from an
> > external source, but it would be really nice if we could have Mailman call
> > a program of our choice, with some arguments/environment variable/STDIN
> > whenver it reacts to a bounce or something similar like that, passing in
> > the relevant information about which email address is being affected and
> > what's being done to it.
>
> Ug.  I think forking is too expensive.  What I could imagine would be an
> XMLRPC backend against which you could write a server in your language
> of choice.  Now, whether XMLRPC is more efficient than fork/popen/and
> friends, I don't know, but at least you won't have to worry about funny
> shell escapes and other nonsense.

Somewhat expensive, perhaps...BUT it has the advantage of being pretty
quick to write and very simple for those who don't have the time,
knowledge, or resources (#1 and #3, in my case) to build something more
complicated.  And, how many requests per second are really going to hit
the server, in any case?

Just a thought....

David.