On Mar 21, 2015, at 09:32 PM, Barry Warsaw wrote:
>I want to make some minor backward incompatible changes to the JSON
>representation for pending mailing lists requests, e.g. subscription holds.
>
>The first change is that `type: subscription` requests will change their
>`address` key to `email`
On Mar 23, 2015, at 08:39 PM, Andrew Stuart wrote:
>Any thoughts on how we could integrate with LDAP?
The intent is that the user database could be backed by, or augmented by LDAP,
although that is currently a goal, not reality.
>Maybe of Mailman had some sort of event notification hook system f
> As for the `password` key: It's recognized by mailman.client and
> exposed within the mlist instance's `requests` property. But it's used
> nowhere in postorius and I would be surprised if it's used anywhere in
> hyperkitty (Aurélien...?). I guess it can go away.
No problem, I don't use pending
Andrew Stuart writes:
> LDAP seems like a pretty configuration heavy thing to put in to a
> standlone Mailman system. I’m currently researching to find some
> sort of minimla/lightweight LDAP integration approach.
IMHO, what we really want (besides a pony, do you raise ponies?) is
"enterprise
Any thoughts on how we could integrate with LDAP?
I’d be happy to authenticate against LDAP but that leaves the open question of
how to synchronize the Mailman user database with the LDAP server.
Maybe of Mailman had some sort of event notification hook system for when users
add/edit/delete. O
On Mar 23, 2015, at 09:34 AM, Andrew Stuart wrote:
>How would user passwords work if not stored in the core?
>
>When someone logs in currently I just ask the core if the password is valid
>and off we go.
WFM. As I said, the core doesn't (currently) use it, but certainly it's
available through th
How would user passwords work if not stored in the core?
When someone logs in currently I just ask the core if the password is valid and
off we go.
as
On 23 Mar 2015, at 8:19 am, Barry Warsaw wrote:
On Mar 22, 2015, at 09:55 PM, Florian Fuchs wrote:
> As for the `password` key: It's recogni
On Mar 22, 2015, at 09:55 PM, Florian Fuchs wrote:
>As for the `password` key: It's recognized by mailman.client and
>exposed within the mlist instance's `requests` property. But it's used
>nowhere in postorius and I would be surprised if it's used anywhere in
>hyperkitty (Aurélien...?). I guess i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 22.03.2015 um 02:32 schrieb Barry Warsaw:
> I want to make some minor backward incompatible changes to the
> JSON representation for pending mailing lists requests, e.g.
> subscription holds. You'll see these for example in urls like:
>
dump
Fine with me.
as
On 22 Mar 2015, at 12:32 pm, Barry Warsaw wrote:
I want to make some minor backward incompatible changes to the JSON
representation for pending mailing lists requests, e.g. subscription holds.
You'll see these for example in urls like:
>>> dump_json('http://localhost:9001/3.0
I want to make some minor backward incompatible changes to the JSON
representation for pending mailing lists requests, e.g. subscription holds.
You'll see these for example in urls like:
>>> dump_json('http://localhost:9001/3.0/lists/a...@example.com/requests')
entry 0:
delivery_mo
11 matches
Mail list logo
