You need an Outlook rule that applies only to emails sent by people inside your company. The built-in rule wizard does not offer an explicit condition for internal senders. This article explains how to use the From field combined with a custom condition to create a rule that triggers exclusively on internal messages. You will learn the exact steps to set up the rule and how to test it.
Key Takeaways: Building an Internal Sender Rule in Outlook
- Rules > Manage Rules & Alerts > New Rule > Apply rule on messages I receive > Next: Start the rule wizard and select the correct template for incoming messages.
- Condition: with specific words in the sender’s address > yourdomain.com: Use your company domain as the filter to target internal senders only.
- Action: move, flag, or forward: Choose the action that applies to internal emails, such as moving them to a specific folder.
How the Internal Sender Rule Works in Outlook
Outlook rules process incoming messages based on conditions you define. The rule wizard includes a condition for specific words in the sender’s address. To target internal senders, you use your company email domain as the word filter. For example, if your company uses contoso.com, you create a rule that looks for contoso.com in the sender’s email address. This method works for any domain that your organization uses, including subdomains.
No special permissions or administrator rights are required to create this rule. The rule runs on your Outlook client and applies only to messages delivered to your mailbox. It does not affect server-side rules unless you use a Microsoft 365 Exchange account with server-side rule support.
Prerequisites
You need an Outlook account that receives email from your organization. The rule works with Exchange, Microsoft 365, IMAP, and POP accounts. For Exchange and Microsoft 365 accounts, the rule runs on the server when Outlook is closed. For IMAP and POP accounts, the rule runs only when Outlook is open.
Know your company’s primary email domain. If your organization uses multiple domains, you need to add each domain as a separate condition or use a wildcard pattern if your Outlook version supports it.
Steps to Create the Internal Sender Rule
- Open the Rules Wizard
In Outlook, go to the Home tab. Click Rules in the Move group and select Manage Rules & Alerts. In the dialog that opens, click New Rule on the toolbar. - Select the Template
Under Start from a blank rule, select Apply rule on messages I receive. Click Next. - Add the Internal Sender Condition
In the Step 1 box, scroll down and check the box labeled with specific words in the sender’s address. In the Step 2 box, click the underlined link specific words. A dialog appears. Type your company domain, for example contoso.com, and click Add. If your company uses multiple domains, add each one. Click OK. - Define the Action
Click Next. In the Step 1 box, check the action you want the rule to perform. Common actions for internal emails include move it to the specified folder, flag the message for follow up, or forward it to a distribution list. In the Step 2 box, click the underlined link to configure the action. For example, if you choose move it to the specified folder, click specified and select the destination folder. Click OK. - Set Exceptions (Optional)
Click Next. In the Step 1 box, check any exceptions you want. For example, except if the sender is in the specified address book can exclude external contacts who email from your domain. Click Next. - Name and Finish the Rule
In the Step 1 box, type a name for the rule, such as Internal Sender Move. Check the box Turn on this rule. Click Finish. Click OK to close the Rules and Alerts dialog.
Testing the Rule
Send a test email from an internal account to your mailbox. Verify that the rule action applies correctly. For example, if you set the rule to move messages to a folder named Internal, the test email should appear in that folder. If the rule does not trigger, check the condition spelling and ensure the domain matches exactly.
Common Mistakes and Limitations
The rule does not trigger for internal senders
The most common cause is an incorrect domain spelling. Verify that the domain in the rule condition matches the sender’s domain exactly. If your company uses a subdomain like sub.contoso.com, add that subdomain as a separate condition. Outlook does not support wildcard domains in the rule wizard. You must list each subdomain explicitly.
The rule triggers for external senders who use the same domain
Some external organizations use email addresses that contain your company domain in the local part, for example externaluser@contoso.com. The rule treats this as an internal sender because the domain matches. To avoid this, add an exception for senders outside your address book. In the rule wizard, check except if the sender is not in the specified address book. Then select your company’s global address list.
The rule does not run when Outlook is closed
For IMAP and POP accounts, rules run only when Outlook is open. For Exchange and Microsoft 365 accounts, server-side rules run even when Outlook is closed. To convert the rule to a server-side rule, create the rule in Outlook with an Exchange or Microsoft 365 account. The rule automatically runs on the server.
Internal Sender Rule vs Manual Filtering
| Item | Internal Sender Rule | Manual Filtering |
|---|---|---|
| Setup time | 5 minutes once | Repeated each time |
| Automation | Runs automatically on arrival | Requires manual action |
| Domain support | Multiple domains added individually | Search any domain |
| Error risk | Low with correct domain | High due to human error |
| Server-side execution | Yes with Exchange or Microsoft 365 | N/A |
The internal sender rule saves time and reduces manual work. Manual filtering requires you to check the sender domain each time you process email. The rule automates this check and applies your chosen action instantly.
You can now create an Outlook rule that triggers only on internal senders using your company domain as the filter. Test the rule with a sample internal email to confirm it works. For advanced scenarios, consider adding exceptions for external senders who share your domain or using a server-side rule for always-on execution.