Email Routing Service

No. Any team with user-critical email benefits from continuity and fallback behavior.

Yes. Controlled fallback and route visibility help teams react faster and reduce user-facing impact.

No. Routing and deliverability complement each other: one handles path resilience, the other sender quality.

Failover sends traffic to a backup path when the primary fails. Load splitting spreads traffic deliberately for capacity or reputation isolation. Your policy should match risk and architecture.

Use low-risk streams first, monitor bounce and deferral rates, and keep a rollback path. Document who approves changes and how incidents are declared.

Often yes. Teams route transactional mail on high-trust paths and marketing on separate infrastructure so issues in one stream do not block critical notifications.

Well-designed routing adds minimal overhead compared to network and recipient acceptance time. Measure end-to-end if latency-sensitive flows are involved.

Typically platform or infrastructure engineering with input from deliverability and security. Clear ownership prevents conflicting changes during incidents.

Routing can point to different Sendarix relay paths or regions. During migration, gradual traffic shifts and mirrored monitoring reduce cutover risk.

IP rotation distributes sending volume across multiple IP addresses to prevent any single IP from triggering rate limits or reputation penalties. Sendarix manages IP pools automatically, cycling traffic based on warming status and real-time reputation metrics.

When a primary relay path becomes unreachable or returns persistent errors, Sendarix automatically redirects traffic to the next available path in your configured pool. This happens within seconds, without requiring manual intervention or developer involvement.

A routing pool is a collection of configured sending paths (IP addresses, SMTP endpoints, or regional relays) grouped by purpose or reputation tier. Sendarix evaluates each message against pool policies to select the optimal path at send time.

Messages queue locally on Sendarix infrastructure during a total relay outage. The queue is durable and messages are not lost. Once any path recovers, queued messages are delivered in priority order. You receive alerts when queue depth exceeds configurable thresholds.

Yes. Configure sending domain-to-pool mappings in your routing policy. Each sending domain can have its own primary pool, fallback pool, and failover order. This is the recommended approach for multi-product or multi-tenant deployments.

Messages to domains with no MX records fail at DNS resolution. Sendarix returns a permanent bounce with code 555 (No MX record). These are not retried, as they represent invalid destinations rather than transient failures.

Standard plans support up to 5 routing pools. Enterprise plans support up to 25 pools with cross-pool failover chains. Each pool can contain up to 20 sending IPs with independent reputation tracking.