Email Security

MSP Toolkit
Practical troubleshooting paths for MSP technicians dealing with real-world support failures.

What This Category Covers

Email security tickets should follow one message through authentication, policy verdict, quarantine, release, and downstream delivery. Avoid global bypasses for single-message problems.

First Layer to Isolate

Message sample first, then headers/authentication/policy/downstream trace.

Useful Tools, Logs, and Portals

  • Message trace
  • Gateway quarantine/search
  • SPF/DKIM/DMARC checks
  • Headers
  • Allow/block lists
  • Admin audit logs

Before You Escalate

  • Sender/recipient/timestamp/message ID captured
  • Header/auth checked
  • Policy verdict reviewed
  • Downstream delivery checked

Articles in This Path

Pick the closest symptom and work from there.

Avanan admin sees malicious file verdict but user mailbox still shows clean bannerAvanan alerts indicate success while end-user experience never changesAvanan and Microsoft Defender both act on the same message causing duplicate alertsAvanan and SIEM alert mapping duplicates one phishing incident into many ticketsAvanan anti-bec policy protects executives but not AP invoice aliasAvanan API connection healthy but remediation actions delay by several minutesAvanan configuration survives testing but resets after restart or syncAvanan connector remains healthy but newly licensed users absent from policy scopeAvanan credential or certificate rotation breaks an existing integrationAvanan detects impossible travel compromise but account already reauthenticated safelyAvanan DLP policy sees credit card patterns but exempts wrong finance groupAvanan encrypted message policy collides with external DLP gateway actionAvanan end-user banner localization wrong for bilingual tenantAvanan feature works in web app but fails in desktop clientAvanan flags phishing correctly but user remediation notifications never sendAvanan healthy dashboard status masks a failing production workflowAvanan logging shows delivery yet the target workflow never completesAvanan mailbox scan finds historical phish but bulk remediation stalls halfwayAvanan new deployment works for pilot group but not for production rolloutAvanan policy change applies in admin console but target users never receive itAvanan policy change hits test tenant but production tenant remains unchangedAvanan quarantine action removes message but Outlook search still shows itAvanan quarantine or protection action triggers but recovery workflow failsAvanan quarantines user-reported phish but ticket workflow never updatesAvanan remediation removes message from inbox but leaves mobile notification intactAvanan remediation succeeds in Gmail but fails on shared Microsoft 365 mailboxAvanan service health green but Teams malicious-file remediation delayedAvanan user digest lists remediated mail long after item was removedAvanan vendor impersonation policy catches executives but misses shared mailbox abuseAvanan workflow succeeds for one account but fails for shared or delegated accessBarracuda Email Security admin portal shows healthy status but end-user action still failsBarracuda Email Security alerts indicate success while end-user experience never changesBarracuda Email Security alerts or logs indicate action succeeded but user experience never changesBarracuda Email Security authentication succeeds but downstream authorization still blocks accessBarracuda Email Security background job runs on demand but fails unattended overnightBarracuda Email Security branding or template change deploys but old content persists in user viewBarracuda Email Security client can reach the service but one dependency times outBarracuda Email Security configuration survives testing but resets after restart or syncBarracuda Email Security connector health looks normal but data stops syncingBarracuda Email Security credential or certificate rotation breaks an existing integrationBarracuda Email Security failover or backup path tests cleanly but live cutover still failsBarracuda Email Security feature works in web app but fails in desktop clientBarracuda Email Security healthy dashboard status masks a failing production workflowBarracuda Email Security integration duplicates actions and creates conflicting alertsBarracuda Email Security integration with Microsoft 365 or identity provider breaks after secret rotationBarracuda Email Security logging shows delivery yet the target workflow never completesBarracuda Email Security new configuration applies in test group but not production usersBarracuda Email Security new deployment works for pilot group but not for production rolloutBarracuda Email Security newly created users or devices stay outside intended scopeBarracuda Email Security policy change applies in admin console but target users never receive itBarracuda Email Security policy exception fixes one case but similar workflows still failBarracuda Email Security quarantine or protection action triggers but recovery workflow failsBarracuda Email Security remediation removes the symptom temporarily but issue returns after policy refreshBarracuda Email Security reporting totals diverge from trace or log evidence after changesBarracuda Email Security role assignment looks correct but permission denial continuesBarracuda Email Security search or indexing shows stale results after remediationBarracuda Email Security service recovers after outage but cached state never normalizesBarracuda Email Security sign-in or launch works but policy or license enforcement fails afterwardBarracuda Email Security update installs cleanly but one business-critical function disappearsBarracuda Email Security workflow succeeds for one account but fails for shared or delegated access

FortiMail quarantine or protection action triggers but recovery workflow fails

Submitted by Anonymous (not verified) on

Field Summary

FortiMail quarantine or protection action triggers but recovery workflow fails is a Email Security ticket where the visible symptom can be misleading. Email-security tickets should follow a message sample through policy verdict, quarantine, authentication, release, and downstream delivery. Healthy dashboard status is not the same as a delivered message. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.

FortiMail configuration survives testing but resets after restart or sync

Submitted by Anonymous (not verified) on

Field Summary

FortiMail configuration survives testing but resets after restart or sync is a Email Security ticket where the visible symptom can be misleading. Email-security tickets should follow a message sample through policy verdict, quarantine, authentication, release, and downstream delivery. Healthy dashboard status is not the same as a delivered message. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.

FortiMail workflow succeeds for one account but fails for shared or delegated access

Submitted by Anonymous (not verified) on

Field Summary

FortiMail workflow succeeds for one account but fails for shared or delegated access is a Email Security ticket where the visible symptom can be misleading. Email-security tickets should follow a message sample through policy verdict, quarantine, authentication, release, and downstream delivery. Healthy dashboard status is not the same as a delivered message. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.

FortiMail feature works in web app but fails in desktop client

Submitted by Anonymous (not verified) on

Field Summary

FortiMail feature works in web app but fails in desktop client is a Email Security ticket where the visible symptom can be misleading. Email-security tickets should follow a message sample through policy verdict, quarantine, authentication, release, and downstream delivery. Healthy dashboard status is not the same as a delivered message. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.

FortiMail alerts indicate success while end-user experience never changes

Submitted by Anonymous (not verified) on

Field Summary

FortiMail alerts indicate success while end-user experience never changes is a Email Security ticket where the visible symptom can be misleading. Email-security tickets should follow a message sample through policy verdict, quarantine, authentication, release, and downstream delivery. Healthy dashboard status is not the same as a delivered message. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.

FortiMail credential or certificate rotation breaks an existing integration

Submitted by Anonymous (not verified) on

Field Summary

FortiMail credential or certificate rotation breaks an existing integration is a Email Security ticket where the visible symptom can be misleading. Email-security tickets should follow a message sample through policy verdict, quarantine, authentication, release, and downstream delivery. Healthy dashboard status is not the same as a delivered message. Record subject, issuer, SAN, expiration, binding, and trust chain before replacing certificates.

FortiMail new deployment works for pilot group but not for production rollout

Submitted by Anonymous (not verified) on

Field Summary

FortiMail new deployment works for pilot group but not for production rollout is a Email Security ticket where the visible symptom can be misleading. Email-security tickets should follow a message sample through policy verdict, quarantine, authentication, release, and downstream delivery. Healthy dashboard status is not the same as a delivered message. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.

FortiMail healthy dashboard status masks a failing production workflow

Submitted by Anonymous (not verified) on

Field Summary

FortiMail healthy dashboard status masks a failing production workflow is a Email Security ticket where the visible symptom can be misleading. Email-security tickets should follow a message sample through policy verdict, quarantine, authentication, release, and downstream delivery. Healthy dashboard status is not the same as a delivered message. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.

FortiMail policy change applies in admin console but target users never receive it

Submitted by Anonymous (not verified) on

Field Summary

FortiMail policy change applies in admin console but target users never receive it is a Email Security ticket where the visible symptom can be misleading. Email-security tickets should follow a message sample through policy verdict, quarantine, authentication, release, and downstream delivery. Healthy dashboard status is not the same as a delivered message. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.

Exchange Online Protection branding or template change deploys but old content persists in user view

Submitted by Anonymous (not verified) on

Field Summary

Exchange Online Protection branding or template change deploys but old content persists in user view is a Email Security ticket where the visible symptom can be misleading. Email-security tickets should follow a message sample through policy verdict, quarantine, authentication, release, and downstream delivery. Healthy dashboard status is not the same as a delivered message. The fastest path is to identify which layer changed and prove it with logs or a repeatable test.

Subscribe to Email Security