Email Security

Minimal guidance for messy support realities.

FortiMail service recovers after outage but cached state never normalizes

Issue Summary

This article covers a FortiMail within Email Security issue where FortiMail service recovers after outage but cached state never normalizes. Use the path below to confirm scope, identify whether the break is policy, configuration, sync, identity, routing, or client related, and work through repair in a controlled Tier I / II / III path.

FortiMail background job runs on demand but fails unattended overnight

Issue Summary

This article covers a FortiMail within Email Security issue where FortiMail background job runs on demand but fails unattended overnight. Use the path below to confirm scope, identify whether the break is policy, configuration, sync, identity, routing, or client related, and work through repair in a controlled Tier I / II / III path.

FortiMail update installs cleanly but one business-critical function disappears

Issue Summary

This article covers a FortiMail within Email Security issue where FortiMail update installs cleanly but one business-critical function disappears. Use the path below to confirm scope, identify whether the break is policy, configuration, sync, identity, routing, or client related, and work through repair in a controlled Tier I / II / III path.

FortiMail authentication succeeds but downstream authorization still blocks access

Issue Summary

This article covers a FortiMail within Email Security issue where FortiMail authentication succeeds but downstream authorization still blocks access. Use the path below to confirm scope, identify whether the break is policy, configuration, sync, identity, routing, or client related, and work through repair in a controlled Tier I / II / III path.

FortiMail search or indexing shows stale results after remediation

Issue Summary

This article covers a FortiMail within Email Security issue where FortiMail search or indexing shows stale results after remediation. Use the path below to confirm scope, identify whether the break is policy, configuration, sync, identity, routing, or client related, and work through repair in a controlled Tier I / II / III path.

FortiMail role assignment looks correct but permission denial continues

Issue Summary

This article covers a FortiMail within Email Security issue where FortiMail role assignment looks correct but permission denial continues. Use the path below to confirm scope, identify whether the break is policy, configuration, sync, identity, routing, or client related, and work through repair in a controlled Tier I / II / III path.

FortiMail newly created users or devices stay outside intended scope

Issue Summary

This article covers a FortiMail within Email Security issue where FortiMail newly created users or devices stay outside intended scope. Use the path below to confirm scope, identify whether the break is policy, configuration, sync, identity, routing, or client related, and work through repair in a controlled Tier I / II / III path.

FortiMail policy exception fixes one case but similar workflows still fail

Issue Summary

This article covers a FortiMail within Email Security issue where FortiMail policy exception fixes one case but similar workflows still fail. Use the path below to confirm scope, identify whether the break is policy, configuration, sync, identity, routing, or client related, and work through repair in a controlled Tier I / II / III path.

FortiMail connector health looks normal but data stops syncing

Issue Summary

This article covers a FortiMail within Email Security issue where FortiMail connector health looks normal but data stops syncing. Use the path below to confirm scope, identify whether the break is policy, configuration, sync, identity, routing, or client related, and work through repair in a controlled Tier I / II / III path.

FortiMail logging shows delivery yet the target workflow never completes

Issue Summary

This article covers a FortiMail within Email Security issue where FortiMail logging shows delivery yet the target workflow never completes. Use the path below to confirm scope, identify whether the break is policy, configuration, sync, identity, routing, or client related, and work through repair in a controlled Tier I / II / III path.