Why Automatic Forwarding May Not Deliver Every Message

First separate the original from the forwarded copy

Seeing a message in the source mailbox confirms that it reached that mailbox. It does not establish that a separate copy was sent onward, accepted by the destination provider, or placed somewhere visible to the recipient. Treat those as separate stages when you investigate.

Start with one specific message that you expected to be forwarded. Note its sender, subject, and approximate arrival time, then check whether it is present in the source mailbox. If it is not there, investigate delivery to the source mailbox first; forwarding settings cannot explain a message that never arrived there.

If the original is present, continue with the forwarding configuration and destination. Avoid assuming that a delay or missing copy means the source message was lost.

Check whether the intended forwarding rule is active

Open the mail settings or rule controls available for the account and check that forwarding is enabled. The exact controls vary by provider and account. If you cannot find a forwarding option, or it is unavailable to your account, ask the relevant support contact or administrator rather than assuming the mailbox forwards automatically.

Look for conditions that may limit which messages are forwarded. A rule might apply only to selected senders, subjects, or other criteria, depending on the provider. Compare the message that failed with those conditions. Also check whether another rule or setting could change how the message is handled.

If you change a setting, record what you changed and save it. Rechecking one controlled change at a time makes it easier to identify what mattered.

Verify the destination character by character

Check the entire destination address, not just the name displayed beside it. A misspelled mailbox, an extra character, or the wrong domain can send a copy elsewhere or cause it to be rejected. If the address was pasted, compare it with the address supplied by its owner instead of relying on memory.

Make sure the destination mailbox still exists and can receive mail. If it belongs to another person or organization, ask them to confirm the exact address and check their own mailbox. A sender-side setting cannot confirm that the destination is active or that its owner can see the forwarded copy.

When more than one forwarding destination is configured, identify which one should receive this message. Do not assume that adding an address changed an existing destination or applied to every message.

Expected destination: [person]@example.com
Configured destination: [person]@exmaple.com
The letters in the domain differ. Correct the address only after confirming the intended destination with its owner.

Look for the copy where the destination provider may have placed it

Ask the destination recipient to search for the sender or subject, not just to check the inbox. The forwarded copy may be in a spam, junk, quarantine, archive, or other folder, depending on that provider's controls. A search across available folders can distinguish a misplaced message from one they cannot find.

The destination provider may also filter or reject a forwarded message. If the recipient sees a rejection notice or receives a delivery failure report, keep it and share its relevant details with the administrator. Do not treat an absence from the inbox alone as proof of rejection; the copy might be filtered or delayed, or the forwarding rule might not have applied.

Check with the destination recipient before repeatedly resending or changing the rule. That can help avoid duplicate messages and preserve useful clues about what happened to the original copy.

Use a small, controlled check

After confirming the rule and destination, send a new, ordinary test message from an address you control, if that is appropriate for your account. Choose a clear subject, note when it was sent, and check both the source mailbox and the destination's available folders. A successful test is useful evidence for that message and configuration, but it does not prove every future message will be delivered.

If the test does not arrive, capture what you can before changing anything else: whether the original reached the source, the destination address as configured, the rule's conditions, and any notice from the destination. Never include passwords or one-time codes in a support request.

• Is forwarding enabled for the relevant mailbox or rule?
• Does the full destination address match the confirmed address?
• Could a condition exclude this message?
• Has the destination recipient checked search and filtered folders?
• Is there a rejection or delivery notice to share?

When the administrator should inspect the route

If the source message arrived, the forwarding setting appears active, the destination address is confirmed, and the recipient cannot find the copy, ask an administrator to inspect the relevant mail route. Include the message details and the checks you completed so the investigation can focus on the path between the source mailbox and destination.

For a BITTU Mail workspace, authorised workspace or domain administrators can inspect their own domains in /workspace, subject to their role, plan, and provisioning state. Ask an administrator with the appropriate access to review the relevant route; do not assume every user can see or change domain-level controls.

Until the destination confirms receipt, treat forwarding as unconfirmed. An original message in the source mailbox is helpful evidence about the first delivery stage, not proof that the forwarded copy reached its destination.