The Spam List
Part of the MountDev Ops Helpdesk documentation. Updated November 18, 2026
MountDev Ops Helpdesk documentation | Updated November 18, 2026
Our Commitment
MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.
Every Email Lands in Helpdesk
Marking a ticket as spam, or moving it back with Not Spam, from an Inbox row or its bulk bar frosts the row while it works and fades it out when it is done (Progress on a Row).
Helpdesk never throws mail away. Email from a sender on your spam list still becomes a ticket, in full (its formatting, pictures, and attachments), but it goes to the Spam tab of the Inbox instead of Open:
- No receipt goes to the sender, and nobody on your team is emailed about it.
- No webhook or automation runs for it, the same as when a person marks a ticket as spam.
- Only owners and admins see Spam.
- The ticket says why it is in Spam, in its conversation.
More mail from the same sender joins its ticket the usual way (by its email headers, the ticket number, or the same subject), and stays in Spam.
When a sender on the spam list replies to a ticket that is not spam (one that started before they were added to the list), the message joins that ticket, so nothing is lost. The ticket is not opened again and nobody is told, and the ticket says so in its conversation. If that sender is not spam, take them off the list (below).
Helpdesk's own replies, receipts, and follow-ups coming back to one of your support addresses (a loop) are the only mail Helpdesk never files. Every other email from your own addresses is filed: a Meetings confirmation link or a booking notice sent from help@ to help@ becomes a ticket, marked automatic, with no receipt, and Helpdesk's own notices to your team are filed closed, telling nobody. Each email Helpdesk sends says it is from Helpdesk, which is how it knows the difference. An email that only claims to be from one of your addresses, and fails the sender checks, is filed like anyone's and marked as not verified.
Marking a Ticket as Spam
Owners and admins select Mark as Spam on a ticket (action helpdesk.spam.mark):
- The sender goes on the spam list: their whole domain, or, at free email providers such as Gmail, only their address. Your own addresses' domains can never go on it.
- The ticket moves to Spam, and only owners and admins see it from then on. Its waiting receipt and follow-ups are cancelled.
- From then on, mail from that sender goes to Spam as described above.
Not Spam
Open a ticket in Spam and select Not Spam (action helpdesk.spam.unmark, owners and admins). The ticket moves to the Inbox, under Open, Waiting on Customer, Waiting on Us, or Closed by its status, where your whole team can see it. When its sender is on the spam list, Also take them off the spam list is checked at first, so their next email comes to the Inbox too. Nothing is emailed to the sender: no receipt goes out late.
The List
Spam List in Helpdesk Settings (action helpdesk.spam.list) shows each address or domain on the list, who added it and when (entries brought in from another system say Brought in), and, under Mail Set Aside Earlier, the last 50 messages that were set aside before spam went to the Spam tab.
Take Off (action helpdesk.spam.clear) takes a sender off the list, so their next email goes to the Inbox again. Tickets already in Spam stay there; select Not Spam on a ticket to move it.
Bringing in a Spam List
A spam list kept in the system you used before can be brought in once, when your support email moves to Helpdesk. An entry already on your list, or one a person here took off the list, is left as it is, so bringing the list in again changes nothing and never undoes a choice made here. Your own addresses' domains are never added. After that, your Helpdesk spam list is the only one that counts.
Spam Deletes Itself
Spam cleans itself (Joshua, 2026-11-15: "anything in there after 30 days gets deleted automatically"). A ticket that has been in Spam for the days set in Helpdesk Settings, Delete Spam After, is deleted for good by a job that runs every night, with its messages, files, and follow-ups. The choices are 7, 14, 30 (the start), 60, or 90 days, or Never (Until a Person Decides). The days count from when the ticket was marked spam, which Helpdesk records. Deleting is your company's own choice about its own data: the setting is yours, and the Spam view always says the real number of days.
- The Spam view (owners and admins) opens with a note, Spam Is Deleted After 30 Days, and each row says how many days are left ("27 Days Left", amber at 3 or fewer, Deleted Tonight on the last day). Not Spam moves a ticket back to the Inbox, as before.
- The job works in small batches a night so it never holds up a person, and it writes one line in the Activity Log a night with a count only ("Deleted 12 spam tickets older than 30 days"), never a subject, sender, or any content.
- It never deletes a real client's mail. A ticket whose sender, or anyone who wrote on it, is a known contact of a CRM company (closed or not) is skipped. Its row says Kept: Known Contact and Stays until a person decides, with no countdown. It stays until a person clicks Not Spam or Delete; Delete asks once, and is only for these kept tickets (action
helpdesk.spam.delete, people only, never an AI assistant or a key). - Spam that was already there when this shipped gets its clock on the first night the job runs, never backdated, so the first deletion is 30 days later. No notice is posted to anyone, and the days are set with the Delete Spam After button on Helpdesk Settings.
- Mark as Spam puts the sender on the spam list and the ticket in Spam, and its clock starts (action
helpdesk.spam.mark).
