Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Email notification pushers removed on signout #3696

Open
turt2live opened this issue Aug 15, 2018 · 3 comments
Open

Email notification pushers removed on signout #3696

turt2live opened this issue Aug 15, 2018 · 3 comments
Labels
A-Email-Push Email notifications A-Push Issues related to push/notifications A-User-Experience O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Blocks non-critical functionality, workarounds exist. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues.

Comments

@turt2live
Copy link
Member

There are two ways to set up email notifications for your account:

  • Upon registration (via configuration options)
  • By setting up an m.email pusher (clicking the checkbox in Riot)

Both of these are tied to the access token that was used to create them. For registration, this is the first access token for the user. If the user logs out to invalidate the access token, the email pusher goes away. This decision makes sense for HTTP pushers, given logging out of an app should surely stop sending data to it, however for email it feels a bit awkward. It seems like a valid use case to not want to be logged in to your matrix account anywhere, and instead receive an email when someone needs you - but this cannot be done without leaving a device logged in somewhere.

@rettichschnidi
Copy link
Contributor

rettichschnidi commented Nov 18, 2019

If anyone else like me is wondering how to work around this: Simply do not log out. You can close the browser/app, but you should not log out. It is not needed anyway.

Might be obvious, but it took me quite a while to understand the semantic of "logging out" in the Matrix world.

@richvdh
Copy link
Member

richvdh commented Jan 23, 2020

this is, frankly, mental.

@richvdh richvdh added z-bug (Deprecated Label) and removed z-minor (Deprecated Label) labels Jan 23, 2020
@devjeff
Copy link

devjeff commented May 8, 2021

I've stumbled upon the same issue. I've also thought about just not logging out, but I think the decision whether to remove the email pusher should be up to the user. They can still login to their client and remove the email pusher explicitly if they get annoyed by notifications or use the unsubscribe link in the email.

@erikjohnston erikjohnston added S-Minor Blocks non-critical functionality, workarounds exist. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. and removed z-bug (Deprecated Label) z-p2 (Deprecated Label) labels May 13, 2021
@richvdh richvdh added the A-Push Issues related to push/notifications label May 13, 2021
@callahad callahad added the P3 (OBSOLETE: use S- labels.) Approved backlog: not yet scheduled, will accept patches label May 13, 2021
@MadLittleMods MadLittleMods added the A-Email-Push Email notifications label Aug 17, 2021
@DMRobertson DMRobertson added O-Uncommon Most users are unlikely to come across this or unexpected workflow and removed P3 (OBSOLETE: use S- labels.) Approved backlog: not yet scheduled, will accept patches labels Oct 19, 2022
@clokep clokep added O-Occasional Affects or can be seen by some users regularly or most users rarely and removed O-Uncommon Most users are unlikely to come across this or unexpected workflow labels Mar 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Email-Push Email notifications A-Push Issues related to push/notifications A-User-Experience O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Blocks non-critical functionality, workarounds exist. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Projects
None yet
Development

No branches or pull requests