Andrew Stuart writes:
> Specifically if would be good if a Mailman admin could define in
> the Mailman config file a set of destination email addresses and
> POST urls that archive messages are sent to. This would meet many
> common archiving needs via configuration instead of code.
I think t
-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
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
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 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
Hello,
My name is David Udelson. I am a freshman Computer Science
undergraduate at Cornell University. I have 3 years of experience with
python under my belt, but I've never contributed to an open source project
because I've never known where to begin. I'm hoping GSoC will provide me
with that
