Shared vs dedicated sending IP: establish who controls the decision

Define the decision

When sending through a hosted business mailbox, the provider normally manages outbound infrastructure. Buying a separate IP does not make that mailbox use it. First identify whether your actual sending service offers a meaningful IP choice.

Work through the procedure

1. Record the service that submits and transports the mail.
2. Ask who owns routing, reverse DNS and reputation investigation.
3. For an available dedicated option, assess operational capacity and consistent legitimate traffic.
4. Compare the maintenance obligations with the current managed route.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Current path: hosted mailbox → provider-managed outbound servers
Proposed purchase: unrelated dedicated server IP
Missing link: no supported routing change in the mailbox service
Decision: investigate the existing path before purchasing infrastructure

Read the result

A dedicated IP changes responsibility as well as control. It does not repair irrelevant targeting, missing authentication or a broken unsubscribe process.

Check before moving on

1. Confirm the option applies to the service actually used.
2. Keep observed rejection evidence before changing infrastructure.

Limits and next action

This guide does not recommend an IP purchase or a guaranteed volume threshold. Use the provider’s current supported architecture and your own traffic evidence.

Source: Zintara sending and deliverability context