Upstream Provider

Tell INKY which security filter sits upstream so it can track the correct mail hop. INKY scans after the MX record, so it needs to know where mail came from to check that specific hop accurately.

Written By Matt Sywulak

Last updated 4 months ago

Admin Center > Analysis > Upstream Provider

Analysis - INKY or found in Routing - INKY

Select Your Provider

Common Providers:

  • AppRiver

  • Avanan

  • Barracuda Cloud

  • Barracuda On Premises

  • DuoCircle / Mailhop

  • FireEye

  • Fortinet FortiMail

  • FuseMail / VIPRE

  • Hornetsecurity

  • Intermedia

  • IronPort

  • Mail Assure

  • Mailprotector

  • MessageLabs

  • Mimecast

  • Paubox

  • Proofpoint

  • Proofpoint Essentials

  • Reflexion

  • SilverSky by BAE Systems

  • Sophos Central Email

  • Sophos Email Appliance (On Premises)

  • Spamh / SpamStopsHere

  • SpamHero / MX Thunder

  • SpamTitan

  • Trend Micro Email Security (TMEMS)

  • Trend Micro Hosted Email Security (HES)

  • ZeroSpam / Cumulus

  • Zix

No Upstream Filter:

  • Office 365 only (no other upstream provider)

  • None (no upstream provider)

Special Cases:

  • Smarthost with Office 365 as MX (rare - do NOT select if using O365 connector)

  • Google Forwarding to Non-Google Account (rare - do NOT select if on G Suite)

  • Custom (contact INKY support to configure)

  • Unspecified

Why It Matters

INKY needs to identify which hop to check for authentication and threat analysis. Incorrect configuration causes INKY to check the wrong mail server, breaking SPF validation and threat detection.

Contact INKY if your platform isn’t listed.