Symptoms
A filter for name@example.com ignores mail delivered to name+orders@example.com. This guide addresses that particular contrast, not every fault that can occur with the product or service.
- Observable failure: A filter for name@example.com ignores mail delivered to name+orders@example.com.
- Control test: Compare raw To and Delivered-To recipient values in a real message.
- A confirmed correction must meet this outcome: Only the intended plus-address messages trigger the label.
One successful test is a useful clue, but a reliable resolution should survive reopening the application or repeating the original workflow without extra workarounds.
Why It Happens
Email services may apply server rules, client rules, conversation grouping and mailbox policies at different stages. An old message moved manually is not proof that a newly arriving message will be treated the same way.
An apparent failure of the whole system can originate in one stage. In this case, investigate exact address mismatch before treating forwarder changes visible recipient or filter limited to a different account as facts.
Three competing explanations
- Exact address mismatch.
- Forwarder changes visible recipient.
- Filter limited to a different account.
These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports exact address mismatch does not automatically exclude forwarder changes visible recipient; the comparison needs to separate them.
Before Making Changes
Retain the original message and test with an ordinary non-sensitive email so filtering experiments cannot silently discard important correspondence. Do not create a broad rule that captures security or recovery emails.
Preserve the current state: note the affected product or account, current mode and time of the failed attempt. If settings will be changed, photograph or write down their original values. Keep copies of any unique files or evidence before overwriting anything.
Use a non-sensitive sample whenever possible. If the issue involves a shared device, building system, workplace account or regulated equipment, obtain the appropriate owner or administrator permission first. Stop if the test would compromise security, electrical protection, access or an animal's welfare.
Problem-Specific Diagnosis
Run this discriminating test before restarting or resetting the entire system: Compare raw To and Delivered-To recipient values in a real message. Compare the observed result against the three paths below.
| Observation or suspected layer | Interpretation | Next controlled check |
|---|---|---|
| Exact address mismatch | If the failing state changes under the comparison, exact address mismatch is plausible. This is not yet proof. | Repeat with that one factor changed, then return to baseline. |
| Forwarder changes visible recipient | If the first change has no effect but a supported configuration differs, forwarder changes visible recipient moves higher on the list. | Inspect the relevant option or documented behavior without clearing unrelated settings. |
| Filter limited to a different account | If both earlier paths are contradicted, investigate whether filter limited to a different account accounts for the timing or device-specific result. | Collect an event timestamp or status report for qualified support. |
Now apply the least-disruptive change that corresponds to the evidence: Use an appropriate supported recipient pattern and test an isolated message. Avoid treating all three hypotheses at once; simultaneous changes erase the diagnostic value of the test.
Step-by-Step Troubleshooting
Begin with reversible comparisons. Use Advanced only if the evidence points to a deeper problem.
Verify the affected workflow
A filter for name@example.com ignores mail delivered to name+orders@example.com. Write down where it happens, its most recent time and the state displayed by the product. Do not treat a nearby working feature as proof the whole path is healthy.
Run the safe comparison
Compare raw To and Delivered-To recipient values in a real message. Use the same device, account and operating conditions where practical. Note what remains unchanged so the comparison is meaningful.
Try the smallest safe intervention
Use an appropriate supported recipient pattern and test an isolated message. Make one adjustment at a time and preserve the previous value so it can be restored if the result becomes worse.
Confirm the real outcome
Only the intended plus-address messages trigger the label. Repeat the complete user-facing operation and then make sure unrelated protections and functions still work. If the result is inconsistent, restore the previous setting and continue diagnosis.
Separate the three suspected layers
Assess evidence for exact address mismatch, forwarder changes visible recipient and filter limited to a different account separately. A positive result for one path is not evidence for every path. Preserve before-and-after observations, including timestamps.
Check the responsible subsystem
Inspect original message headers and any forwarding aliases before widening the match. Gather only logs and supported diagnostic views that apply to this exact scenario; do not change service-wide policy or hardware wiring.
Validate the unaffected path
Revisit the comparison: Compare raw To and Delivered-To recipient values in a real message. If the first suspected cause is not supported, compare the behavior predicted by forwarder changes visible recipient with the behavior predicted by filter limited to a different account. Keep the first correction reversible.
Commit or escalate with evidence
Confirm: Only the intended plus-address messages trigger the label. If that cannot be reproduced, restore the original safe configuration and send sanitized observations to the mailbox provider or authorized workspace administrator. Safety boundary: Do not create a broad rule that captures security or recovery emails.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Assuming exact address mismatch is proven simply because the visible symptom matches this page.
- Changing multiple accounts, rules, connections or device settings before running the control: Compare raw To and Delivered-To recipient values in a real message.
- Skipping this safety boundary: Do not create a broad rule that captures security or recovery emails.
- Resetting, formatting, deleting credentials or replacing hardware without a confirmed backup, a supported recovery path and evidence that the step is necessary.
A setting that makes one symptom disappear is not always the correct permanent configuration. If it disables another essential function, revert it and investigate the underlying dependency rather than leaving an unsafe workaround in place.
How to Verify the Fix
The primary pass condition is specific: Only the intended plus-address messages trigger the label. Repeat the original workflow, not a loosely related shortcut, and confirm both the previously failing behavior and an unaffected comparison still work.
- Record the before-and-after state in the same location, account and operating mode.
- Repeat the original comparison: Compare raw To and Delivered-To recipient values in a real message.
- Check the stated pass result: Only the intended plus-address messages trigger the label.
- Confirm that normal security, notification, storage or physical safety protections remain enabled.
If the result works only once or disappears after reopening the app, reconnecting the accessory or waiting for the next scheduled event, treat the issue as intermittent instead of fixed. Keep the event time and what changed between attempts.
If the Problem Continues
If the safe correction does not work, move to a focused deeper investigation: Inspect original message headers and any forwarding aliases before widening the match. This is a different path from the first settings check; use it only if the device or service supports the required diagnostics.
When escalating to the mailbox provider or authorized workspace administrator, provide the exact symptom, result of the control test, changes already tried, time of occurrence and any non-sensitive error or status data. Explain whether exact address mismatch, forwarder changes visible recipient and filter limited to a different account were supported or contradicted by evidence.
Do not share account recovery codes, private documents, live access tokens, sensitive location histories or full recordings merely to prove the problem. Redact or summarize identifiers before opening a public support request.
Prevent Recurrence
Keep a short reference note with the working configuration and the successful check: Only the intended plus-address messages trigger the label. After an app update, firmware change, network migration or scheduled clock change, run the same short test before depending on the function again.
Watch for the condition that originally made the failure visible: A filter for name@example.com ignores mail delivered to name+orders@example.com. Where practical, retain an alternative approved way to perform the essential task so that one device, cloud service or interface does not become a single point of failure.
FAQ
How can I tell whether exact address mismatch is responsible?
Run the controlled comparison: Compare raw To and Delivered-To recipient values in a real message. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.
What if the real cause is forwarder changes visible recipient rather than exact address mismatch?
Do not repeat the initial correction blindly. Check the supported diagnostic path: Inspect original message headers and any forwarding aliases before widening the match. Keep the earlier working configuration recorded so you can reverse the test.
When is this particular issue resolved?
The decisive result is: Only the intended plus-address messages trigger the label. If it fails after the normal workflow is repeated, document whether filter limited to a different account still explains the remaining behavior and escalate with non-sensitive observations.