On 04/10/2016 11:06 PM, Terri Oda wrote: > On 2016-04-06 4:29 PM, 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 addresses in Mailman. >> >> I think we have to decide how and where addresses will be verified. >> Are they >> going to be via confirmations emailed by core or via Postorius? >> >> I think the core has to support emailed confirmation messages because >> Postorius is technically an optional component. So if a site were to >> build >> their own REST front-end, they'd at least want to allow the core to >> handle >> email verifications without having to build that into their front-end. > > I'd prefer core to do it, so that it's consistent regardless of > front-end and there isn't duplicated work in every single web component > for Mailman, which is one of the reasons I haven't reviewed any of the > proposed Postorius code to do this. (The other big one being that I > need to do some research on auth libraries, because past experience has > told me that I rarely agree with Simon. ;) ) >From time to time I search for such projects, and I currently prefer allauth. That doesn't mean that I know it's the best solution, it's just the best one (in my eyes) I currently know of.
Postorius is currently confirming emails on it's own. And Hyperkitty doesn't at all (the registration process doesn't attempt to confirm emails). _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://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: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
