Inbound mail service association
This signal links public MX routing evidence to a documented service association where the Provider Catalogue supports a match.
Why it matters
Service associations make inbound routing easier to read
What it adds
A documented service association adds readable context to the observed MX targets while keeping those targets as the source evidence.
What a change may mean
A change may reflect migration, filtering, routing, reseller arrangements or routine maintenance.
Limits
An association is not a supplier relationship
A service association can be incomplete or ambiguous. It does not prove a customer relationship, ownership, responsibility, service quality or the mailbox backend.
How it is derived
Match visible MX targets to documented services
The observed MX exchanges remain the source evidence. Provider Resolution compares those targets with versioned Provider Catalogue rules and records any supported inbound mail associations. The Provider Resolution and Provider Catalogue versions used are retained as classification provenance.
Technical fields
Observed change
Inbound association movement
The retained email_provider_changed event requires both the MX target set and the resolved provider identity to change under the same classification context. A catalogue-only label change is classification context, not observed infrastructure movement.
Use this signal
See mail service associations in context
Use State for the full-panel association view and Cohorts for eligible grouped views.
Supporting concept
The MX evidence behind the association
Related signals