Re: [Mailman-Developers] Set cookies for global authentication

[Mark Sapiro]

Hopkins, Justin wrote:
>
>I manage approx 50 discussion lists using the mailman system. The nature
>of our organization is that one member is more than likely subscribed to
>more than just 1 list. One issue that has come up among the membership
>is the desire to authenticate only once and then be permitted to access
>the private archives for all lists that they are subscribed to without
>logging in again.
>
>I've noticed that using administrative credentials created a cookie
>named 'site' whereas a normal login creates a cookie identifying the
>users email address and the individual list.
>
>Has anyone worked on changing this functionality, or is it planned for
>Mailman 3? I've scoured list archives and the internet in general and
>haven't found even a hint that anyone is working on this or even feels
>like it's worth complaining about.


Did you look at ? The very first paragraph
says in part "Many things that people have been wanting for years will
be addressed, most notably a unified user database ...".

The unified user database will address this and several other issues
involving user email addresses, roles, authentication, etc.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] Set cookies for global authentication

[Adam McGreggor]

On Fri, May 15, 2009 at 08:10:54PM -0500, Hopkins, Justin wrote:
> One issue that has come up among the membership
> is the desire to authenticate only once and then be permitted to access
> the private archives for all lists that they are subscribed to without
> logging in again.
> 
> Has anyone worked on changing this functionality, or is it planned for

Hum, we're sort of doing something like that, at least for
lists-admin.



()

might be a starting point for you.

(and also


())


(In our case authentication works via Apache Basic Auth, unix groups, 
and password-generation scripts


()

it should be quite trivial to implement using LDAP, too.)

-- 
``What lawyers call intellectual property is
  no more than theft from the public domain.''  (Andy Mueller-Maguhn)
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

[Mailman-Developers] Set cookies for global authentication

[Hopkins, Justin]

Hey all,

I manage approx 50 discussion lists using the mailman system. The nature
of our organization is that one member is more than likely subscribed to
more than just 1 list. One issue that has come up among the membership
is the desire to authenticate only once and then be permitted to access
the private archives for all lists that they are subscribed to without
logging in again.

I've noticed that using administrative credentials created a cookie
named 'site' whereas a normal login creates a cookie identifying the
users email address and the individual list.

Has anyone worked on changing this functionality, or is it planned for
Mailman 3? I've scoured list archives and the internet in general and
haven't found even a hint that anyone is working on this or even feels
like it's worth complaining about.

Thoughts?

Cheers,
Justin J. Hopkins
MOBIUS, Internet Applications Specialist
hopkin...@umsystem.edu
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] Proposal: option for UTF-8 emails without base64 encoding

[Petr Hroudný]

2009/5/15 Barry Warsaw :
>> The fix is quite simple and is already widely used by other projects.
>> All that needs to be done is
>> to redefine Python's UTF-8 charset properties, i.e. in every place
>> where you have
>>
>> from email.Charset import Charset
>>
>> you need to add:
>>
>> email.Charset.add_charset('utf-8',email.Charset.SHORTEST, None, None)
>>
>> With such setting, mailman will keep the 8bit encoding also when it's
>> adding header/footer and won't downconvert to 7bit+base64. So I'd like
>> to propose the above addition, at least as a configurable option
>> if there's any fear that enabling it by default could cause some problems.
>
> I'll note that you don't need to change Mailman at all do to this.  You
> simply need to add this to your mm_cfg.py file and I'll bet it will just
> work for you.

It works indeed! Just a slightly different syntax needs to be used:

import email.Charset
email.Charset.add_charset('utf-8',email.Charset.SHORTEST, None, None)

It might probably make sense to document this somewhere, or perhaps introduce
a new config option for MM2.2 which will do this. Almost all MTAs today are 8bit
clean, so having an option to work in 8bit mode will surely be
attractive for many.

Thanks, Petr

P.S. I responded to your other comments into bug #373083 notes.
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9