[Mailman-Developers] Re: [Mailman-Users] [RELEASED] Mailman 2.1 alpha 3

Chuq Von Rospach chuqui@plaidworks.com
Sun, 21 Oct 2001 23:37:02 -0700


On 10/21/01 11:17 PM, "Barry A. Warsaw" <barry@zope.com> wrote:


>   http://sourceforge.net/project/shownotes.php?release_id=58074

(clap clap clap clap)


>         and admins can change members' Real Names on the membership
>         pages.  Mass subscribing accepts "email@dom.ain (Real Name)"

You should also accept

    Real Name <email@dom.ain>

Since that's the other common (perhaps more common) format.

>       o The list admin can send an immediate urgent message to the
>         entire list membership, bypassing digest delivery.  This is
>         done by adding an Urgent: header with the list password.
>         Urgent messages with an invalid password are rejected.

Is the Urgent: header stripped as it passes through Mailman? What happens
when a regular user tries to put an Urgent: header on a message as a
non-admin? 

>       o There is now a `site list' which is a mailing list that must
>         be created first, and from which all password reminders
>         appear to come from.  It is recommended that this list be
>         called "mailman@your.site".

Is there a plan to set up a bounce returned to mailman@your.site to be
considered a global bounce and that user is unsubbed from all lists? Right
now, mailman effectively throws away bounces from the password reminders,
which can be used very effectively to keep stuff clean.

>   - Membership Adaptors
>       o Internally, mailing list memberships are accessed through a
>         MemberAdaptor interface.  This would allow for integrating
>         membership databases with external sources (e.g. Zope or
>         LDAP),


Given that, if someone wants to write a fully external authenticator, is it
possible to completely disable mailman's interface for a given list (or all
lists?) Including things like monthly password reminders?

I guess what I'm suggesting is Mailman as a slave to a non-attached
membership system -- can we really detach it cleanly so it's just a delivery
system without rough edges or hacking? Down to the external membership
system in headers and footers?

>         This work was sponsored by Control.com

(clap clap clap clap)