Suppress email notification for cc'ed users of emailed-in messages

(updated to hopefully make more clear… sorry if I’m not making sense)

Steps to replicate:

  1. on discourse, create test user account ONE with email ONE@one.com and leave at default notification settings
  2. configure a discourse group inbox with an email-in email address TWO@two.com
  3. send an email from a 3rd email address THREE@three.com, not on discourse, to TWO@two.com with a cc to ONE@one.com
  4. check ONE@one.com email: you will see two emails:

What I would expect and hope for is that at step 4 the test user would only get the email from THREE@three.com. They would not get an email from discourse at all, though the notification can and should still appear on the notification menu when next they log in.

This issue is not a major one for staff, but it can and will get confusing and annoying for members who will get an extra email and not know where to go to reply.

5 Likes

Do you mean “suppress the discourse notification” in bold above, because I am really quite unclear how we would “suppress” the fact that you just mailed someone from your mail client. Do you expect us to to contact google, who sent the mail, and remove that email you just sent, somehow?

Yes, I mean the email notification from discourse. will update to clarify. :slight_smile:

Totally aware that you can’t stop me from emailing somebody else. It’s the second email from discourse that I’m concerned about.

I am still unclear what you mean. The notification, or the actual PM? Can you edit your post to clarify? I’m very very confused.

This is part of another email related problem I’m currently working on. So, you can expect this to be resolved quite soon.

7 Likes

cool! I’m curious to hear about that. :rocket:

FYI, I think the behavior I am expecting is used in the discobot functionality. The tutorial PMs are not delivered by email but do appear on the notification menu to be discovered next time the user logs in.

Yeah, I reused the same functionality that discobot uses for skipping emails. :wink:
https://github.com/discourse/discourse/commit/31e2385316422a9d91ec118e73504143f3e4542e

And this is what I was working on:
https://github.com/discourse/discourse/commit/5210e3e744995ba94ba69fdf9a64adcb571be58d

Up until now if ONE replied to TWO and THREE, it would have been rejected by Discourse because the reply key didn’t belong to ONE. It belongs to THREE. But since Discourse knows that ONE was CC’d in step 3, it will now allow the incoming email from ONE.

7 Likes