Two emails for one user


(Dave McClure) #30

See here:


(Vinayak Agarwal) #31

Hello,
I’m new to discourse.
The idea seems pretty useful. I didn’t understand this:
It would also be useful if this merging function could be easily called from a plugin, since for us the addition of secondary emails is going to be done automatically through our auth system.


(Leo McArdle) #32

The system we use (and just for clarity here, when I say ‘we’, I don’t mean Meta Discourse, but Mozilla’s Discourse instance) for logging users in will soon return multiple email addresses for each user to Discourse, and so there might be a need to merge users after a user logs in, if we’re trying to add a secondary email which already exists as a primary email for another user. This merge would have to be called from the code of the login plugin we use, and so programming the code which merges users in a way which can be easily executed from that plugin would be useful.


(Jeff Atwood) #33

Longer term I am defninitely interested in supporting more than 1 validated email for each user account. Just not sure when we can get to it. How much work do you think this would be @sam as a baseline?


(Sam Saffron) #34

A couple of days for the server side of things, a couple more days for UI


(Jeff Atwood) #35

Are we supporting 2 or {n} emails per user for that amount of work?


Allow for email re-writing to solve the additional email address?
(Sam Saffron) #36

There are just lots of flows, reset password, social logins and user page and admin user page

I would only recommend adding backup email support, not N email support


(Leo McArdle) #37

Our requirement would be N email support. I’m interested in why you recommend adding only backup email support - N would be more work, but not a ridiculous amount more, no?

So if I get there first, would this be #pr-welcome?


(Sam Saffron) #38

My issue with N email support is that this is done pretty much nowhere and is not something that is easy to explain to users

Gmail, yahoo and Github only support a single backup email.

Also, conceptually, backup is about having a “just in case” email. All notifications and so on go to primary


(Leo McArdle) #39

The reason I see for N email support, in addition to being a backup, would be to support additional from addresses for email-in.


(Felix Freiberger) #40

For Github, that doesn’t appear to be true:


(Erlend Sogge Heggen) #41

I think we’re all generally in favour of N email support, but the implications of supporting more than a single backup email are not immediately clear.

This is one of those arguments that is best resolved with code. Simply:

  1. Do a PR for 1 backup email, which you know will get accepted without much ado (and with much :heart: )

  2. then we can resume the topic of N emails. If need be, do some basic mockups of how this’d work in Discourse (GitHub seems to provide a good frame of reference) before submitting a PR that adds N emails support.


Do not auto-create users when reply by mail
(Leo McArdle) #42

Sounds good to me! I should note, I can’t commit to coding that initial PR yet, so don’t let me stop anyone else in the community having a crack or, of course, the team developing it.


(Sam Saffron) #43

Note, if you only need this change for your auth provider, you can code a custom auth provider with support for multiple emails today without having the full fledged support in core. (which requires changes to user, admin user, reset password flow and so on)


(Leo McArdle) #44

We’d want to do ‘useful’ things with the additional emails in Discourse (like allow emails-in from them, which will be a pain from a plugin), and the changes to our auth system which make this useful won’t be happening for a few months, so it makes sense to go for the solution which benefits everyone, rather than a short term fix we won’t even end up using.


(Robert Hudson) #45

This is very common in mailing lists (mailman did it very well). Users could send list emails from multiple email addresses, but the list software only output list emails to their primary account.

When we imported our data from mailmain archives into Discourse, the system created multiple accounts for many of our users (there were four or five for me as an example).

It would be great to have N (even if N was a single-digit integer) email address support, plus an ability to merge accounts (and posts) in under that primary account (something for admins to do on a case-by-case basis). I’d be happy for Discourse to only send the “you’ve posted from a secondary address, we’ll only send list traffic to your primary address” email only once to each of the non-primary accounts.


(Jakub Macina) #46

I understand this concept well, but after reading whole thread I am uncertain about logging in. Does this feature allows user to log in with alternate email address? Or the only use case is start a post or reply from alternate email address?


(Allen - Watchman Monitoring) #47

This topic started when @cregox was looking for a way to log in with either of two addresses, the rest of the conversation has been about emails (or maybe backup email addresses for password resets)

I don’t know that there’s any real need for logging in as either user… I mean, sure, that’d be nice :slight_smile: The pain point I hear most is regarding when an authorized user gets an email on AddressA and send their reply on AddressB. People can’t always send from the same address anymore, and password managers (for login) are much easier to train to use a single username.

Taking it a step further, if the additional address(es) WERE going to be allowed for log in, I’d bet that some would want an option to disallow that.

To me, the draw here is as pressure relief on forum administrators who don’t want to keep telling people to reply from the right address.


(caue rego) #48

the draw here is as pressure relief on forum administrators who don’t
want to keep telling people to reply from the right address.

here’s a little story about what’s “right”:

yesterday I just accidentally formatted a oneplus 2.

it’s hard enough to do it on purpose, but not really bullet proof at all.

(it was a screen very similar to this, but instead of “reboot” there was
only “exit”, along with much weirder options)

you’ve got to power off, wait, turn it back on holding volume down, and
enter within 3 items through the following menu. there’s just 1 big wait
there, the rest can be done rather quickly.

the volume button is too close from the power button, my wife managed to
use them without looking at the screen, just by holding the phone with her
right hand and pressing a bit too hard.

then she entered the english option (there were 2 other chinese options),
saw that screen and gave it to me, asking what was it, which I suspected to
be a fastboot but wasn’t sure.

so, as any good geek who is used to deal with all this and try to gather
information before doing anything stupid, as someone who actually enjoy
exploring computers a lot, and as a former somewhat good programmer who
have worked with this for over 15 years, I didn’t exit immediately.

and I didn’t know what she had done so far. I continued on trying to see
what were the other options. entered one, couldn’t find a button back,
pressed power button hoping it would go back but tripped over and ended up
pressing it twice.

(I haven’t even seen that screen)

it all happened too fast, in less than 1 minute, while walking down the
subway.

so what? everything is backed up on the cloud right? even photos!

in fact, yeah. I always set up as much backup as possible. as an obvious
evidence on starting this thread. from having at least a few important
emails.

but I’ve been using a new camera app, camera mx, which does have a quick
photo - video feature and save a few moments before each photo, called live
shots. people love it when I show it. and she have been enjoying it for a
while. she had just came out of a trip, filled with those.

problem is, those videos are only saved within a hidden folder, and so out
of any automated backup tool. the only way around it, right now, is
manually saving every live photo, and through a quite cryptic and hidden
option called “copy video”. and, even then, it will save it as a video.
most of us will never set an automated backup for videos over mobile
network, due to data restrictions most of carriers around the world still
have.

this lack of proper backup, like most of it, have always annoyed me, but I
never could find a solution to this.

I did manage to stop the formatting when it was less than 1/3 of the way.
that thing goes really fast! but seems like it had wiped it all already
and, on top of it all, I could find no way to recover those files. I’m
positive there is a way, and it would probably cost at least $100. looks
like android 6 already have pretty reliable deleting and formatting
features.

so, we lost every one of her video moments. all in just under a minute.
thanks to a chain of meticulous circumstances.

tl;dr;

probably all of you already know this, but… users, a.k.a. those people
you talk about @watchmanmonitor, will screw it up.
and at least 95% of any user interface is about preventing that.
just like, in science, the same percentage is all about preventing
ourselves from committing mistakes with data and analysis.
there is no “right” address.


(Christoph) #49

It’s probably a question of how organized you expect users to be in terms of the emails they’re using. Here is a scenario where it would help to have more than one “backup” emails: At my university, every user has at least two email addresses by default first_name.last_name@university.tld and first_name.last_name@department.university.tld. In addition, if you are affiliated to multiple departments or research centers, you might have additional ones. Plus, when a department is renamed the old aliases remain functional.

For whatever reason (I suspect it has to do with how you setup your email an a new device) people are sending emails with different sender email addresses, probably without even noticing it. I have one user who already has two staged users because of that…

I agree that it’s a good idea to start with one backup email, but I just wanted to mention this as an example where more than one makes sense.

Of course, multiple emails won’t entirely solve this either because these people obviously won’t bother inputting all their aliases, but at least it would allow admins to do so to avoid having to deal with the messages from staged users.

Another related scenario is obviously going to exist when it becomes possible to merge users.