[Mailman-Developers] Hi! I'll be your intern for the summer :)
Ian Eiloart
iane at sussex.ac.uk
Thu Jun 22 12:33:07 CEST 2006
--On 21 June 2006 13:37:36 -0400 emf <i at mindlace.net> wrote:
> Ian Eiloart wrote:
>
>> How about this for extra:
>>
>> 1) Display a list of ALL members - just their names and addresses.
>> 2) Delete ALL the list members with one click - OK, and maybe a confirm
>> dialog!
>
> Hm. This comes slightly in opposition to the desire to have a more
> user-centered mailman interface; what happens if a user changes their
> preferences and you re-build the entire list?
Well, for some of our lists it's simply inappropriate for users to set
preferences. Let me give you an instance. We're a University. People make
enquiries about studying here. We have to send an email to all of those
people because -say- there's been a change in the registration process.
> An associated problem is what happens to users that are subbed to >1 list?
>
> I recognize this may not be an issue in your specific case, I just think
> that issues like these will be more of a deal when we don't keep
> "members" in per-list silos.
>
> Perhaps something that might be more appropriate would be a "member
> differ", wherein you upload a list of email addresses, and it shows you
> the list of emails that were on the list but aren't now, and those that
> would be added, and gives you the option to either accept all the
> changes or selectively modify them.
>
> When you say you'd like these people to be able to take advantage of
> "other mailman features", which features do you mean?
Well, our MTA won't accept more than 250 recipients per email, so when
people need to email several thousand recipients, they have to split their
recipient lists into blocks. It would be much better to simply paste them
into a Mailman web UI, and let Mailman handle the details.
Why 250? Well, actually that's because our LDAP server barfs if you make
more than about 300 queries on one connection. Those queries might be
validating local email addresses.
So, I could implement this another way, but Mailman also offers me
authentication and authorisation, and allows me to ensure proper footers on
the emails, and probably some other useful stuff too.
> ~ethan fremen
>
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers at python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives:
> http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe:
> http://mail.python.org/mailman/options/mailman-developers/iane%40sussex.a
> c.uk
>
> Security Policy:
> http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
--
Ian Eiloart
IT Services, University of Sussex
More information about the Mailman-Developers
mailing list