Phone: 0850 346 41 09  |  Weekdays 10:00–18:00 · Technical support 24/7

🇹🇷 TR

Digital Bridge Blog

Business Email & Documents

Email Quarantine Policy: Who Reviews Suspicious Mail, Who Can Release It, and How Every Decision Is Logged

An email quarantine policy sets which messages are held, who may release them and how each decision is logged. Use our decision table to set one up in 7 steps.

11 min read  · Digital Bridge Engineering Team
Email Quarantine Policy: Who Reviews Suspicious Mail, Who Can Release It, and How Every Decision Is Logged

An email quarantine policy is the set of written rules that decides which inbound messages are held back, at what risk threshold, who may review and release them, how long they are kept and how each decision is recorded. Email quarantine itself is the restricted holding area; the policy is what makes it a control rather than a dumping ground.

Key takeaways

  • Email quarantine is a decision queue, not a bin; bulk marketing mail belongs in a separate folder, not in quarantine.
  • A good quarantine policy answers five questions: what is held, at what threshold, who releases it, for how long, and where decisions are logged.
  • Spoofed senders, risky attachments and payment detail changes should be released only by named people, with a written reason.
  • According to the Verizon 2026 DBIR, 80% of attacks blocked by email gateways were plain phishing; releasing without a reason undoes the filter's work.
  • Tune the quarantine threshold on evidence, not the calendar: a monthly review of false positives and suspicious mail that got through.

Why does email quarantine so often fail?

In many companies email quarantine is either a black hole, where customer orders, e-invoice notifications and tender replies pile up unseen, or a formality that lets almost everything through. Once staff discover the black hole, they ask IT to "just release everything addressed to me", and the control quietly disappears.

Where the threshold is set too loosely, almost everything reaches the inbox and only crude spam is held. A targeted phishing email or a supplier impersonation goes straight to the finance team.

Both failures share a root cause: a technical setting with no policy or owner behind it. Nobody has defined who reviews quarantine, who answers "is this email genuine?" and who is accountable if a released message later proves malicious. If every user can release their own quarantined mail, the attacker only ever has to convince the recipient.

Is DMARC quarantine the same as inbound quarantine?

No; the two are easily confused. The p=quarantine tag in your DMARC (Domain-based Message Authentication, Reporting and Conformance) record tells other people's mail servers what to do with messages that claim to come from your domain but fail authentication; it protects your reputation and your contacts. We cover that side in our SPF, DKIM and DMARC guide. This article is about the opposite direction: which messages arriving at your organisation you hold back, on what grounds and under whose control.

What does running email quarantine without a policy cost?

Quarantine is often where email-borne attacks are first stopped, and what filters hold back is far more than nuisance spam. According to the Verizon 2026 Data Breach Investigations Report, of the attacks blocked by email security gateways, 80% were plain phishing, 10% carried malware, 5% tried to get the victim to phone the attacker and 3% were business email compromise (BEC)-style attempts to get a bank account updated before a wire transfer. Releasing one of those without a reason undoes the filter's work in a single click.

How widespread the threat is gives another reason quarantine cannot be managed ad hoc:

According to ENISA's Threat Landscape 2025, phishing, including vishing, malspam and malvertising, was the leading initial intrusion vector in the incidents analysed in Europe, at about 60%. (ENISA Threat Landscape 2025)

Smaller businesses are not spared. The UK government's Cyber Security Breaches Survey 2025/2026 found that 43% of businesses had experienced a breach or attack in the previous 12 months, with phishing by far the most common type at 38%. In the US, the FBI IC3 2025 Internet Crime Report shows phishing and spoofing as the most-reported crime type in 2025, with 191,561 complaints.

The other cost is quieter: legitimate mail wrongly held, in other words a false positive. A lost tender reply or a late-seen order triggers no alarm, but it is lost revenue all the same; a good quarantine policy manages both risks together. Do not confuse false positives with your own outgoing mail landing in other people's junk folders; that is a deliverability problem, covered in our guide to emails going to spam.

What should an email quarantine policy cover?

The policy does not need to be long, but it must answer five questions clearly: what we hold, at what threshold, who can see and release it, how long it stays, and where decisions are recorded. The email quarantine decision table below is a sensible starting point for most organisations.

Message typeTypical signalRecommended actionWho may release it
Spoofing your own domainSPF/DKIM/DMARC fail, looks like an internal senderQuarantineSecurity lead only, with a written reason
Sender made to look like a known contactLookalike domain, international characters, display-name impersonationQuarantineSecurity lead, after out-of-band confirmation
Risky attachmentMacro-enabled document, executable, password-protected archiveQuarantineIT only; end users cannot release
Payment or bank detail changeReply-To mismatch, urgency, new account detailsQuarantine or deliver with warningLine manager, after a callback
Bulk marketing and newslettersBulk sending, unsubscribe linkDeliver to a separate folderNot needed
Known contact, all checks cleanAuthentication passes, prior correspondenceDeliverNot needed

The critical distinction in the decision table is that quarantine is a decision queue, not a bin. Marketing mail clogs the queue and hides real threats; it belongs in a separate folder via classification, and the difference between classification and a security decision is explained in our piece on AI email classification and triage.

The lookalike-sender and payment-change rows deserve particular care, because such messages often pass authentication. How attackers choose their domains is covered in lookalike domain attacks, and the payment diversion scenario in bank detail change email fraud.

How do you set up an email quarantine policy? 7 steps

  1. Take stock. Count what has landed in quarantine and junk over the past few weeks, by type. List who released what, and which legitimate senders are most often caught by mistake.
  2. Define categories and a threshold. Adapt the decision table to your own suppliers and customers. Before changing a threshold, check how many messages it would affect; blind tuning is how you end up with a black hole or a formality.
  3. Separate the roles. Grant viewing, releasing and deleting as distinct permissions. On shared mailboxes, quarantine rights should sit with named people only; the permission model for team addresses is set out in our guide to shared mailbox management, and delegated access to personal mailboxes in mailbox permissions and delegation.
  4. Write a release rule. No message is released without a recorded reason. Where the sender is a business contact, confirm through a channel independent of the email, such as a phone number already on file, and make adding someone to a "trusted sender" list a separate approval.
  5. Set retention and notifications. Decide how long quarantined mail is kept and what happens at the end of that period, in line with your archiving and personal data retention rules. Tell users in plain language which message was held and why.
  6. Link it to incident response. If a released message later proves malicious, it should already be clear who is told, how other mail from the same sender is found and, where personal data is involved, how the 72-hour breach notification under Turkey's KVKK is assessed. KVKK is Turkey's personal data protection law, broadly comparable in spirit to the GDPR.
  7. Review monthly. Look at the number of legitimate messages wrongly held, the suspicious ones that reached inboxes, and the reasons given for releases. Adjust thresholds and categories on that evidence; a policy is not written once and shelved.

The seven steps work best alongside user training: add real quarantine examples to your security awareness training programme so staff learn to read "why is this held?". To see how quarantine fits with controls beyond email, see our SME cyber security checklist.

Should quarantine decisions use rules or scores?

There are two basic ways to make a quarantine decision: fixed rules (for example, "executable attachments are always held"; which attachments are risky and why is covered in malicious email attachments) and a confidence score built from several signals. Rules are predictable and easy to explain; a score catches signals that are weak on their own but telling in combination. A sound policy uses both, a balance we discuss more generally in AI versus rule-based automation.

How does Digital Bridge set up an email quarantine policy?

At Digital Bridge, we treat a quarantine policy as a business process, not a product setting:

  • Discovery and needs analysis. As part of our cyber security consultancy, we review your current email platform, domain records, quarantine and junk behaviour, and the permission structure of shared mailboxes. We identify, with real examples, which legitimate senders are being caught and which risky messages are getting through.
  • Writing the policy. We build the decision table with you around your own contacts, departments and approval chain. Retention and record-keeping rules are aligned with the work done under our data protection compliance service.
  • Pilot. We trial the policy in a single department first, usually finance or purchasing, measure false positives and misses, and tune the threshold accordingly.
  • Migration and integration. If you are moving to a new email platform, we plan the migration, DNS changes and cut-over through our cloud migration and infrastructure consultancy.

We do not recommend an approach that ties you to a single provider; the policy can be applied on your existing platform. If you are reviewing your provider anyway, add quarantine management to your business email selection criteria.

How does quarantine work in SmartMail?

SmartMail, our business email product, part of our own Smart360 family, provides the technical side of an email quarantine policy out of the box. Every inbound message goes through three groups of checks: identity (SPF, DKIM, DMARC and PTR, which SmartMail computes itself), structure (lookalike domains and international-character spoofing, display-name and brand impersonation, Reply-To and link mismatches) and content (the full text assessed with AI). The outcome is a report with written reasons, so whoever reviews a held message does not have to guess why it is there.

The company administrator sets the quarantine threshold, and before a new threshold is saved SmartMail lists the messages it would affect. A quarantined message is never deleted; it waits with its reasons. That is step two's "no blind tuning" principle built into the product. Authentication and domain checks run in software and keep working even when the AI usage allowance is used up.

For role separation, each SmartMail mailbox has nine separate permissions; quarantine management is one of them and, like delete, is off by default on new assignments. Access to a shared mailbox therefore does not mean the right to release its quarantine. Every message carries an activity history showing who did what, and an audit log records administrative actions; where a mailbox is assigned to a department, removing someone from that department revokes their access automatically. Remote images are also blocked by default.

A concrete scenario: purchasing receives a "latest price list" with a macro-enabled attachment from a domain one letter away from a regular supplier's. The message is held, and the report cites the lookalike domain. The purchasing lead, who holds quarantine rights, rings the supplier on the number on file; if the attachment is not genuine, the message is not released and the incident response process from step six begins.

Next step

The first step needs no software: list the messages released from quarantine in the past month, who released them and why. That list will show the gaps in your policy straight away. Then get in touch; we will draft your decision table with you and demonstrate SmartMail's quarantine report in an environment set up with your own domain. If you would rather start using SmartMail.com.tr straight away, you can choose your number of mailboxes on the Buy SmartMail page. For more on email security, browse our Business Email & Documents hub.

Let us look at your case

Tell us about your process; after a needs analysis we send a written proposal with scope, phases and cost.

Request a Quote 0850 346 41 09
Questions we hear most often

Frequently Asked Questions

What is the difference between email quarantine and the junk folder?

The junk folder holds unwanted but usually harmless messages inside the user's own mailbox, and the user can open it freely. Quarantine holds messages judged to carry a security risk before they are delivered, with restricted access and restricted release rights. The quarantine policy decides which messages go where and who is responsible for reviewing the quarantine.

Should staff be able to release their own quarantined email?

For low-risk categories such as bulk marketing, that can be reasonable. For spoofed senders, risky attachments or messages about changing payment details, release rights should stay with named people. Otherwise the attacker only has to persuade the recipient, and quarantine effectively stops working as a control.

How long should quarantined messages be kept?

There is no single correct period. It should give reviewers a reasonable window and must not conflict with your archiving and personal data retention rules. What matters is that the period is written down, everyone knows what happens when it expires, and messages linked to an ongoing incident investigation are preserved rather than deleted automatically.

How often should the quarantine threshold be changed?

Adjust it based on measurement, not the calendar. A monthly review looks at how many legitimate messages were wrongly held and how many suspicious ones reached inboxes. Checking how many messages a change would affect before applying it avoids surprises such as a suddenly empty inbox or a wave of threats getting through.

Does a DMARC p=quarantine setting protect my inbound email?

Not directly. A DMARC policy tells receiving servers how to treat forged messages sent in your domain's name, so it protects your reputation and your contacts. Whether mail arriving at your organisation is quarantined depends on your own email platform's assessment and your internal quarantine policy. The two complement each other; neither replaces the other.

What should be checked before releasing a quarantined email?

Start with why the message was held: an authentication failure, a lookalike domain, a risky attachment or a payment detail change. If the sender is a known contact, confirm by calling the phone number already on file, not one given in the email. Record the release with its reason, and make adding the sender to a trusted list a separate approval.

How can false positive emails be reduced?

Legitimate mail wrongly held is reduced through measurement. First list the senders caught by mistake in recent weeks, then route bulk marketing mail to a separate folder instead of quarantine. Before changing the threshold, check how many messages it would affect, and assess the result in the monthly review alongside suspicious mail that reached inboxes.

Have a different question? Ask Us

Talk to an Engineer

Tell us what you need to solve. We'll come back with a written proposal.