As far as I know that’s a pretty good summary. I should say however I really
don’t know much except about Mailmania. You’d get better information on
Postorius from Aurelien and Barry is the authority on the Mailman core.
It’s important to understand that Mailman core defines the resources and
I believe I have a better understanding of the puzzle pieces, now. In a
nutshell:
* Mailman 3 allows you to assign administrative privileges to individual users
who may log in with their own credentials.
* Mailman 3 is composed of several separate projects that work together to form
a coheren
Postorius is a Django app that talks directly to the Mailman 3 REST API and
integrates everything needed to get the job done including user interface,
authentication and authorization.
Mailmania is an authenticating reverse proxy server. Effectively it would
allow someone to write a purely Jav
I am currently using Mailman 2.
If Mailman 3 provides the features I am interested in, that would be great,
provided there is some kind of well-defined upgrade path.
I am a bit confused as to what the various components in Mailman 3 are. Is the
web interface to Mailman 3 based on Django? Is t
On Tue, Sep 01, 2015 at 11:15:47AM -0400, Waldbieser, Carl wrote:
> I know that currently, mailman roles are set up such that the roles
> themselves have a shared password per role. I want to be able to move away
> from that model and have roles assigned to individual user accounts that
> would
On 09/01/2015 08:15 AM, Waldbieser, Carl wrote:
> I know that currently, mailman roles are set up such that the roles
> themselves have a shared password per role.
This is true for MM 2.1. It is not true for MM 3.
> I want to be able to move away from that model and have roles assigned
to indi
It might be helpful if I explain what Mailmania does.
login - an anonymous HTTP request can be sent to the server asking to log in
and POSTing Mailman username and password. Success results in a response with a
JWT in the HTTP headers.
authentication - when an HTTP request arrives, it is examine
Waldbieser, Carl writes:
> I would like to actually move the authentication and role
> management *outside* of mailman and have the administrative
> interface consume the role based information from external sources
> (e.g. LDAP, CAS or SAML2 attribute release), so I am looking for a
> more "
Sorry I should say - I don’t think roles exist in Mailman 3? Someone else will
know but I don’t recall offhand.
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: htt
If users still sign in directly, what do you see the functionality of roles
being from a Mailman perspective? I don’t see how they relate Mailman resources
specifically.
The authenticating proxy server (which is still awaiting a better name - Barry?
:-)) currently gives individuals control over
I know that currently, mailman roles are set up such that the roles themselves
have a shared password per role. I want to be able to move away from that
model and have roles assigned to individual user accounts that would allow
access to the admin interfaces for individual lists.
For example,
11 matches
Mail list logo
