[Mailman-Developers] PHP Wrappers?

Ian Eiloart iane at sussex.ac.uk
Tue Nov 22 18:15:07 CET 2005

On 22 Nov 2005, at 16:36, Stephen J. Turnbull wrote:

>>>>>> "Ian" == Ian Eiloart <iane at sussex.ac.uk> writes:
>     Ian> No, you've evidently completely misunderstood me. All I do
>     Ian> want is for Mailman to use *exactly* the same mechanisms for
>     Ian> sender ACLs that it does for rosters. If that's LDAP, that's
>     Ian> fine. If it's SQL, that's fine. If it's flat files, that's
>     Ian> fine.
> As Brad says, that's easier said than done.  As it happens, Mailman
> does (by default) use exactly the same method---it's called a "Python
> pickle".
> But a Python pickle is an _object_ database.  LDAP is about
> tree-structured databases, SQL about relational databases.  It's
> non-trivial to put most of the stuff in Mailman into those formats.
> The problem isn't really that pickles are Python-specific, that's what
> Fred Brooks would call an "accidental" obstacle.  You're right, we
> could, at a fairly predictable amount of effort, convert from a
> Python-specific data store to a standard one accessible by a
> well-defined protocol such as LDAP or SQL.  The problem is that the
> data used by Mailman doesn't necessarily fit those models, and we
> won't know how hard the conversion is (ie, what effects there will be
> on various parts of Mailman) until we do it.  It's a good bet that it
> will be harder than it looks.

Yes, I know all this. However, we're talking about Mailman 3, and I  
understood that Mailman 3 *is* going to support LDAP, SQL, etc  
rosters. All I'm asking is that these include the sender ACLs for the  
lists. Now, sender ACL's already are *just* lists of regular  
expressions. So, what's so hard?

Ian Eiloart
IT Services
University of Sussex

Warning: The Surgeon General Has Determined That Windows Can Be  
Dangerous To Your Health

More information about the Mailman-Developers mailing list