This note is intended to summarize my Admin UX as I silence some users. I’m not asking for changes necessarily, just citing the challenges which may translate to requests on review. When I need to silence a user due to bouncing emails, I don’t want an email to go out to them to notify them of the event. :slight_smile: I don’t see an admin option to add a custom silence reason to the existing list. I’d like to add “Bouncing emails”. I’d like to set one of the available silence period options to be the default. I don’t want to have to set the time period from the dropdown for every event. I do want to advise the user about why they have been silenced, with more information than the one-line “reason”. The box is there to email the user with a note, but again, that emails the user. I just want to message them because I know email doesn’t work. Are other Discourse emails sent to a user after they have been blocked, or silenced? For this specific scenario and possibly others, I do not want any more mail going out to this user, especially if they have subscribed to many notifications. About deleting a user in this same scenario: We can simply delete the user, and we can also “delete and ban both the email address and the IP address”. Why are these linked? I like the idea of banning an email address. I might rarely want to ban an IP address. But banning an IPv4 is awkward for a number of reasons - maybe it’s OK with IPv6 but we’re not there yet. Until these concepts are separated can we not simply ban an email address? If I knew more about Discourse internals I’d be happy to script a process that clears specific items out of the ban lists, but I don’t know where to find that data. We have MaxMind active for this site and I would like to use the IP address to get a location to help determine if the user should be just silenced or deleted. For example, if the last-used address is distant from the registration address (plus other metrics) then I would delete the account for simply smelling bad. But the popup that shows IP info doesn’t show a location. Is that a bug or should I check MaxMind again? I get bounce notices to my postmaster@ address - this is how I know mail from the forum is bouncing. Someone might suggest I look into Bounce Score for auto-cutoffs to avoid emailing someone who already has recorded bounces. We have no bounce data for scoring, I haven’t setup Discourse to poll POP3 (IMAP??) for such data. All I see in meta are forum anecdotes about setting it up. Is there a real dedicated doc on this topic? Again, this is all just to share the (not so great) UX in this specific area, for whomever might be interested. HTH - and Thanks!!!

[image] Tony G: When I need to silence a user due to bouncing emails, I don’t want an email to go out to them to notify them of the event [as far as i believe] I’m guessing if you leave the silence reason empty, it won’t send an email to them. [image] Tony G: I don’t see an admin option to add a custom silence reason to the existing list. I’d like to add “Bouncing emails”. As for that, refer to Custom Predefined Suspension Reasons This is based on what I know about Discourse (it won’t be accurate, but I’m trying to help!)

2468 - we do appreciate! :slight_smile:

[image] Tony G: When I need to silence a user due to bouncing emails, I don’t want an email to go out to them to notify them of the event. How did you configure the bounce score site settings especially bounce score threshold? [This image features a white rectangle labeled "bounce score" with a number 4 inside, followed by the word "threshold" and below that, a message that reads "Max bounce score before we will stop emailing a user." (Captioned by AI)]

I haven’t yet configured the bounce score threshold because I don’t have Discourse checking email for bounce notifications. The information in this meta thread is the best I’ve found on the topic of configuring to process bounces. Over the next several days I’m on a quest to find more complete documentation. But yes, today I am setting a very low bounce threshold.

[image] twofoursixeight: I’m guessing if you leave the silence reason empty, it won’t send an email to them. No, that’s false. There has to be a reason chosen or written in before it is even possible to silence account.

[image] Architect: There has to be a reason chosen or written in before it is even possible to silence account. This makes sense because there is a site message sent to the user to tell them about the event. That site message is not clear about what exactly we want the user to do. So After the message is sent I post a reply to that message to the user, to ask them to reply back when they have corrected the email situation. So the noob challenges I face now include: I do want that message to the user, but I’d prefer to modify the text. Changing admin/customize/email_templates/system_messages.email_revoked for English doesn’t change it for all other languages. Or is there a feature to run an auto translate on one or all system_messages? Without a Search on admin/customize/email_templates/ it’s hard to find the right text system_messages or user_notifications to edit, and to know which processes trigger them. I do not want to send an email when the problem by-definition is that they aren’t getting emails. When I post that reply to the system message on their user profile, another email goes out. If we can effectively block outbound mail to the address that won’t happen. That is, do outbound mail functions all go through a central process that first checks to see if the bounce threshold has been exceeded? Or am I missing a feature around Silence that blocks outbound mail without having to bind that decision to the bounce threshold? Ideally when the user replaces the email address with something valid, or clicks a check for “my address is OK now” it would be cool to have the server send a test mail and on success clear the bounce flag / count. (Random) There are a fixed number of admin_js.admin.user.suspend_reasons and they are “hard” identified to preclude customization for another purpose. That is, we can change the text for admin_js.admin.user.suspend_reasons.combative and there is a single admin_js.admin.user.suspend_reasons.custom but it doesn’t look like we can create a new admin_js.admin.user.suspend_reasons.bouncing_email. This scenario doesn’t just apply to bounces. I can think of other scenarios where we would want to notify the user with a local message that we can’t send them mail and give them a stored custom message that tells them what to do. I suspect this all describes some very fine-tuned behavior that probably doesn’t bubble up the list of priorities, but I dunno yet if or how other folks deal with this. Thanks for patience…

Just keeping this thread updated with progress… I just found this documentation to setup bounce handling: [image] Configure direct-delivery incoming email for self-hosted sites with Mail-Receiver Self-Hosting Discourse is all about enabling civilized discussion. While plenty of people like a web interface, e-mail is still the “hub” of many people’s online lives. That’s why sending e-mail is so important, and when you’re sending e-mail, you really want to be able to receive it, too. There are several reasons why: If e-mails “bounce” (they can’t be delivered for some reason), you need to know about that. Repeatedly sending e-mails that bounce will get your e-mails flagged as spam. Receiving e-ma… [image] Configure VERP to handle bouncing e-mails Self-Hosting Setting up bounces handling Discourse uses the Variable envelope return path (VERP) technique to handle bouncing e-mails. To enable VERP, set the “reply by email address” site setting with an email address template that uses the + sign. The default of replies+%{reply_key}@discourse.example.com … works fine. If you are using your own or your company’s email server, then, that’s it tada Your discourse instance must be able to receive email sent to this address. This should work via POP, bu… The images here are also extremely helpful: [image] Bounced emails not being detected Support the reply_by_email_address is not used as the from address but the envelope-from, specifically so bounces work Here’s an image that demonstrates how each address is used. The addresses themselves are specific to our hosting, but should be sufficient for an example. notification_email: notifications@hs1.discoursemail.com reply_by_email_address: incoming+%{reply_key}@hs1.discoursemail.com A notification: [image] A replyable message: [image] Implementing this functionality should address enough of the challenges here to handle bounced email effectively. I still need to work out exactly how we will notify a multi-lingual user base effectively and get them back on track quickly when they’ve fixed email problems. That is, when they’ve made an effective change they need to notify us or the system so that the blocks on them can be lifted.

[image] Tony G: This scenario doesn’t just apply to bounces. I can think of other scenarios where we would want to notify the user with a local message that we can’t send them mail and give them a stored custom message that tells them what to do. When an e-mail address is bouncing back the automated discourse e-mails, this seems like you wouldn’t necessarily need/want to silence or delete their account for that unless you suspect it is a spoof account or something without valid e-mail. Guess that is probably the reason why you would want to put account on hold temporarily to validate they have working e-mail, do you have a high volume of cases like that or is it practical to deal with those one on one manually? There are some other options like manually changing e-mail notification settings, or changing the not-working e-mail address to other working address controlled by admin or something temporarily. That may not be the best idea just some random ideas here. When an account is deleted that doesn’t send e-mail notification about that last time I checked. Simple but kind of brutal policy is to delete accounts if they don’t have working e-mail.

We’re on the same page. There are different scenarios that different managers will want to handle differently. I’m feeling my way around this software to understand what it does, how it’s intended to be used, and how others use it. The underlying goal of this initiative/inquiry is two-fold: First, pro-actively avoid abuse. Second avoid sending out emails that will bounce which might result in our site getting flagged as a source of non-deliverable email. This can result in temporary listings in RBLs and I want to avoid such nonsense. We do not have a high volume for this site but there are user groups, similar to but different from TL0-4. Users in one group shouldn’t be silenced if something goes wrong with their email. Users in another group with a few recent on-topic posts shouldn’t be silenced. Accounts with no activity or no recent valid activity might be silenced to get their attention if they ever come back. The concept of silencing people to get their attention is awkward. And I don’t really care about email addresses. The real intent there is that if we have a bogus email address I feel an account is more likely to be a source of abuse than not. So I’ll pre-emptively silence them, seek some response, and if we don’t hear from them for a long period just delete the account. A participating user (TL1?) that we just haven’t heard from in a long time might just be put on long-term silence/review. Since we’re here, all of this also implies that people are creating accounts without a valid email, or changing their addresses to something invalid. I’m going through the #documentation and will want to create an automation to: Silence new TL0 users until after they have viewed a couple threads, then email them. If we get a bounce from these specific messages, put them into review status. So no welcome email until after we’re sure they’re a human moving around the site, and no permissons until we’re sure they verify their email.

FWIW It’s not possible to activate your account without first verifying your email (unless manually activated by an admin, or you’re using SSO and not verifying with your idp).

Notes on Silencing or Deleting users

Product Support

Architect August 24, 2024, 7:23pm 6

No, that’s false.

There has to be a reason chosen or written in before it is even possible to silence account.

Topic		Replies	Views
Silence staged users silently? Product Support	4	734	January 24, 2019
Option to notify users if they are block, silenced or banned Feature	6	1361	November 22, 2025
Isn't the silence message a bit misleading? UX moderation	7	869	May 8, 2024
How to unsilence a user who innocently tried to copy & paste and got silenced Product Support	10	1111	March 11, 2026
Silence and suspend reason messages should be PMs Feature moderation , personal-messages	13	837	August 14, 2024

Notes on Silencing or Deleting users

Related topics