On 04/07/2016 01:29 AM, Barry Warsaw wrote:
> On Apr 07, 2016, at 12:26 AM, Simon Hanna wrote:
>
>> Short version: it supports both external (social) and internal (django) auth
>> systems and offers options to combine/switch between them . Allauth provides
>> Signals that I used to verify the addr
On Apr 07, 2016, at 12:26 AM, Simon Hanna wrote:
>Short version: it supports both external (social) and internal (django) auth
>systems and offers options to combine/switch between them . Allauth provides
>Signals that I used to verify the addresses in Mailman.
I think we have to decide how and w
>In that case, how should this address be validated? Should Postorius
>consider that the login system always validates addresses and set them
>as
>verified in Mailman? Should it ask mailman to verify the email
>addresses
>when it encounters a user's un-verified address? This does not seem
>possible
On Apr 06, 2016, at 06:08 PM, Aurelien Bompard wrote:
>In that case, how should this address be validated? Should Postorius
>consider that the login system always validates addresses and set them as
>verified in Mailman? Should it ask mailman to verify the email addresses
>when it encounters a use
Hey people,
Mailman has the notion of "verified" email addresses. When a user is
created / registered in Postorius, a Mailman user can be created. It's off
by default but it seems like a logical thing to do.
This user will be created when the client visits the user profile or
preferences pages any
