Outlook rules are one of the oldest and most reliable features in the inbox: tell Outlook "if a message looks like this, do that", and it obliges, message after message. For many people they are enough. But once you try to keep an inbox organised by the organisation a message comes from, native rules show their structural limits. This article looks fairly at what rules do well, where they fall short, and how continuous, domain-grouped filing differs.
What Outlook rules actually are
A rule is a stored instruction made of three parts: a trigger (a message arrives), one or more conditions (from a sender, containing certain words, sent only to you), and one or more actions (move, flag, categorise, forward, delete). Outlook evaluates your rules in order whenever mail arrives.
Two flavours are worth knowing:
- Server-side rules run on the Exchange/Microsoft 365 server, so they apply even when Outlook is closed and across all your devices.
- Client-side rules run only inside the desktop app while it is open — usually because the action (play a sound, move to a local PST) can't happen on the server.
This split matters: a rule that looks set up correctly may simply not fire when you're on your phone or the app is shut.
Where rules shine is narrow, stable, high-value automation — "move anything from my accountant into Finance", "flag messages where I'm the only recipient". These are precise, long-lived intentions, and rules handle them dependably.
Where native rules fall short for organising by sender
The trouble begins when your goal shifts from "handle these few cases" to "keep my whole inbox tidy by who sent each message." That is an organisational job, and rules weren't designed for it.
One condition, one rule, by hand
Each rule encodes a decision you made manually. To file by sender you create a rule per sender or address pattern. Ten suppliers means ten rules; a busy inbox, dozens. Every new contact is another rule to remember to create — and every supplier who changes their sending address is a rule to remember to fix.
No awareness of organisation domains
This is the big one. A single organisation rarely sends from a single address: Stripe might email from news@stripe.com and notifications.stripe.com; a UK company uses .co.uk, a utility .energy. To a human these are obviously the same company; to a rule they are unrelated strings unless you enumerate each one. Native rules have no concept of the Public Suffix List, so they cannot reliably tell that notifications.stripe.com and stripe.com belong together while stripe.example.co.uk does not. You end up maintaining brittle lists of subdomains by hand.
They don't adapt to new senders
A rule only acts on what it already knows. The first email from a brand-new supplier lands unfiled and stays there until you notice, decide, and write a rule. Rules are reactive to messages, not to the changing shape of who emails you.
Quantity and size limits
Rules are not unlimited. Each mailbox has a finite quota for the total size of its rules (the well-known figure is around 256KB, though the exact ceiling varies by configuration), plus limits on number and complexity. As you scale per-sender rules to cover an organisation, you can quietly hit these ceilings — at which point new rules silently fail to save, or older ones stop running.
Maintenance never ends
Taken together, native rules carry a permanent admin cost. They work beautifully for a handful of deliberate cases and degrade into a chore the moment you use them as a general filing system.
A different approach: continuous, domain-grouped filing
Automatic filing inverts the model. Instead of you encoding every sender in advance, the system reads each message's routing metadata as it arrives and files it by the sender's organisation domain, resolved with the Public Suffix List — so news@stripe.com and notifications.stripe.com land in one "Stripe" folder automatically, and .co.uk or .energy domains group correctly without you listing anything.
Sortfully is the worked example. It connects to Microsoft Outlook and Microsoft 365 — work, school, and personal Outlook.com — through Microsoft Graph, and organises continuously rather than from a fixed rule set:
- It adapts to new senders. A first-time supplier is grouped by domain without you authoring anything.
- You choose move or tag, per mapping. Move a sender's mail to a subfolder, or tag it with a coloured category and leave it in the Inbox. Mix the two freely.
- It's gentle by default. Messages move only after you've read them (you can switch to file-on-delivery), the action is reversible with undo, and messages are moved, never deleted.
- It cooperates with what you have. During setup it detects your existing folders and inbox rules — metadata only — and lets you keep, reuse, or reconcile them. If a native rule has already moved a message, Sortfully leaves it alone.
- It's content-blind. It reads only routing metadata behind a hard-coded allow-list, never bodies or attachments, and uses no AI — filing is content-blind by design and deterministic. See how it works.
Overrides keep you in control: group several domains into one folder, pin a domain to an existing folder, or exclude senders entirely.
Outlook rules vs automatic domain-based filing
| Outlook rules | Automatic domain-based filing | |
|---|---|---|
| Setup effort | Manual: one rule per sender or pattern | One-off mapping; groups by domain automatically |
| Handles new senders | No — unfiled until you add a rule | Yes — grouped by domain on arrival |
| Subdomains and aliases | Only those you enumerate by hand | Resolved together via the Public Suffix List |
| Move or tag | Move, flag, or categorise per rule | Move to subfolder or tag with a coloured category, per mapping |
| Reversibility | Manual: re-file or rewrite the rule | Reversible with undo; messages moved, never deleted |
| Privacy / content access | Can match on body text and subject | Content-blind — routing metadata only, no bodies |
Which should you use?
Both have a place. If you have a few precise, durable intentions — route one critical sender, flag mail addressed only to you — Outlook rules are simple, free, and rock-solid. Keep them. The case for automatic filing is when your real goal is whole-inbox organisation by who emailed you, where the manual, per-sender, no-domain-awareness model turns into ongoing upkeep. For a closer look at the sender-based approach, see organise your Outlook inbox by sender.
If keeping your inbox sorted by organisation has become a task you keep putting off, automatic domain-grouped filing is built for exactly that. Sortfully is in a private, invite-only beta — join the waitlist and we'll email you when it opens.