Django logins for new subscribers
Hi all,
I'm moving our groups to mailman3 (http://we.lurk.org). Enjoying it so far!
I've mass-subscribed people via postorius. However the subscribers don't have django (postorius/hyperkitty) logins. It seems they only exist on the mailman side, not the django side.
If they go through the process of creating an account in postorius, they can configure their mailing list subscriptions, but this is a bit fiddly.
Is this expected behaviour? It would be great if they could be sent a temporary link to set a password and go.
Best wishes,
alex
On Fri, Jan 12, 2018, at 8:41 AM, Alex McLean wrote:
Hi all,
I'm moving our groups to mailman3 (http://we.lurk.org). Enjoying it so far!
I've mass-subscribed people via postorius. However the subscribers don't have django (postorius/hyperkitty) logins. It seems they only exist on the mailman side, not the django side.
If they go through the process of creating an account in postorius, they can configure their mailing list subscriptions, but this is a bit fiddly.
Is this expected behaviour? It would be great if they could be sent a temporary link to set a password and go.
Yes, that is the expected behavior. Postorius is just one of the front-end for Mailman (and only one, for now), so we didn't think it would make sense to create account for every Mailman User in Postorius as well.
So, basically everyone has to go through the sign-up process, which isn't really hard if you choose one of the social logins.
It wouldn't be very hard to write a script that "creates" User accounts for everyone and then users go through the "Forgot Password" workflow to set their passwords. You'd get the list of all users from Mailman's API and then do a get_or_create()
on each one of them (simplest of all approaches, you can ofcourse better ways to do the same).
-- Abhilash Raj maxking@asynchronous.in
On 12 January 2018 at 19:19, Abhilash Raj <maxking@asynchronous.in> wrote:
Yes, that is the expected behavior. Postorius is just one of the front-end for Mailman (and only one, for now), so we didn't think it would make sense to create account for every Mailman User in Postorius as well.
Ok thanks. From my perspective this is confusing behaviour though, especially for people new to the concept of mailing lists. There are three things to understand in the suite - mailman, postorius and hyperkitty. It seems that hyperkitty is trying hard to be a web forum and actually does a really good job (one reason why we're switching), but postorious links to it as an archive rather than a full interface to the discussion. The default welcome email didn't contain any web links to postorius or hyperkitty.
I realise I can change such texts and will spend some time on this. I'd be interested to hear advice from others who have done this sort of thing.
So, basically everyone has to go through the sign-up process, which isn't really hard if you choose one of the social logins.
Yes true.
It wouldn't be very hard to write a script that "creates" User accounts for everyone and then users go through the "Forgot Password" workflow to set their passwords. You'd get the list of all users from Mailman's API and then do a
get_or_create()
on each one of them (simplest of all approaches, you can ofcourse better ways to do the same).
Ok, I'll look into this.
Thanks for the https nudge also by the way, it is on my todo!
cheers
alex
On 01/12/2018 09:17 PM, Alex McLean wrote:
to the discussion. The default welcome email didn't contain any web links to postorius or hyperkitty. That's because neither are required to actually run Mailman. So I guess it's better to have the default not send anything, since the other way round would mean sending dead links.
Currently the core component of Mailman doesn't have a way to know under which url Postorius is reachable...
That's because neither are required to actually run Mailman.
They are part of the 'mailman suite' that I installed, as an integrated whole.
I subscribed everyone via postorius, I'd have thought it would make sense and presumably be straightforward for postorius to create django accounts for them at that point.
I can also set the welcome message via postorius. Again I think it would make sense to be able to tag the postorius URL at that point as a default (perhaps using a text box rather than URL via third party website).
So I guess it's better to have the default not send anything, since the other way round would mean sending dead links.
Not if you're subscribing people via Postorius in the first place.
Currently the core component of Mailman doesn't have a way to know under which url Postorius is reachable...
Perhaps the web interface url could be passed in from the web interface?
Cheers
alex
participants (3)
-
Abhilash Raj
-
Alex McLean
-
Simon Hanna