I'm reviving and expanding on this, because I think that this is something that needs some attention.
Whenever you receive an email through one of the available buckets listed on the Edit Email Settings page, there is an unsubscribe link at the bottom of the email. However, clicking on it will only unsubscribe you from that one email bucket through which the email was sent. If a user wants to unsubscribe from everything, for whatever reason, they have to login and visit that settings page and click Off for every single one.
I can understand this not being much of an issue in the past when we only had three email buckets and the unread inbox option. But then we added all the Jobs emails to that page. And then we created a research bucket. And then we added Teams will all their own buckets. And then we added The Overflow newsletter. And now in present day we have a really long page of email options including:
- Unread inboxes for public and all Teams
- Five different primary email buckets
- Links to community digests and question subscriptions
- All the jobs emails
- The job search status (under Job Preferences) that actually does control receiving recommend Jobs emails despite not being mentioned on the email settings page
That's a lot of stuff, and I don't think it makes sense anymore to not have an easy one-click button that would just turn all of it off swiftly for those who simply do not desire any of the emails anymore. Requiring all the manual click action and browsing around in different settings is annoying to the end-user, and more time consuming than should be necessary.
- Add a button to the email settings page to quickly wipe all of these preferences to the Off position.
- Add the same button to the landing page for the unsubscribe link, to both emphasize that their unsubscribe only affected one thing and make it easy for users to turn off everything else with minimal effort.
(Please note this is not a formal proposal actively being pursued by us. This is simply me voicing my opinions as a user on the need of such a feature.)