Dedicated vs Shared Sending IP: Which to Pick

AcelleMail sends through whatever sending server you connect, so the dedicated-vs-shared IP choice is really a choice about your sending provider. Here's how to decide, and where it lives in AcelleMail.

What this is for

A common question when setting up AcelleMail: should I send from a dedicated IP (one that's only mine) or a shared IP (a pool used by many senders)? The honest answer is that AcelleMail itself doesn't own the IP — it sends through whatever sending server you connect (your own SMTP, Amazon SES, SendGrid, Mailgun, and so on). So the dedicated-vs-shared choice is really a choice about your sending provider, and you act on it where you configure that provider.

This article helps you make the call and shows where it lives in the app.

The short version

  • Shared IP — your mail goes out over a pool of IPs the provider also uses for other senders. The pool already has an established reputation, so a low-volume or inconsistent sender often benefits from it. You don't warm it up, you don't babysit it. The downside: another sender's bad behaviour can affect the pool, and you have less individual control.
  • Dedicated IP — an IP that's only yours. Its reputation reflects only your sending, which is exactly what you want once you send enough to maintain a reputation. The catch: a brand-new dedicated IP has no reputation and must be warmed up gradually, and if you send too little or too sporadically, mailbox providers never build enough signal to trust it.

How to decide

Use volume and consistency, not a magic number:

  • Send a lot, regularly? A dedicated IP gives you control and isolates your reputation from other senders. Worth it.
  • Send modestly, or in irregular bursts? A shared pool's established reputation usually serves you better than a cold dedicated IP you can't keep warm.
  • Just starting out? Begin on shared. Move to dedicated once your volume is steady enough to justify warming and maintaining it.

These are rules of thumb — your provider's own guidance on minimum volume for a dedicated IP is the figure to follow, since it's their pool and their thresholds.

Where this lives in AcelleMail

You don't toggle "dedicated vs shared" inside AcelleMail — you choose it at the provider and then connect that provider as a sending server:

  1. Decide at your provider (e.g. lease a dedicated IP in your Amazon SES / SendGrid account, or stay on their shared pool).
  2. In AcelleMail, go to Sending → Sending servers and add/configure that provider (see Configuring Amazon SES with AcelleMail).
  3. If it's a new dedicated IP, warm it up before full volume — AcelleMail's warmup strategy ramps your daily volume gradually. See Domain & IP Warmup.
  4. Keep sending consistent and watch your reputation — see Sender Reputation Monitoring.

Common questions

Can I run dedicated for marketing and shared for transactional? Yes — connect two sending servers in AcelleMail (one provider/IP per server) and route campaigns to the one you want. See Configuring Multiple Sending Servers.

Does a dedicated IP guarantee the inbox? No. IP reputation is one signal; authentication (SPF/DKIM/DMARC), list quality, and engagement matter just as much. A dedicated IP only isolates your reputation — you still have to earn it.

Related articles

9 comments

3 comments

  1. ahmed.hassan.c…
    dedicated IP made a measurable difference for us. We moved from shared SES to a dedicated IP at ~80k subs and saw ~8% lift in inbox placement within 6 weeks
    1. admin (edited)
      Thanks for the breakdown. Saving for our customer-success team's reference library.
  2. v.petrova.ru
    Has anyone tried PostgreSQL instead of MySQL for the AcelleMail DB? Curious if the indexes behave better at scale.
    1. admin
      Short answer: yes — set the MySQL session variable from your worker's .env on boot and you'll get the longer timeout per connection. We'll add an explicit recipe in the next refresh.
    2. admin (edited)
      Right — for RDS specifically, you can change wait_timeout via the parameter group without a reboot if it's set as 'dynamic'. Most defaults are.
    3. admin (edited)
      good question. the campaign:rerun audit writes to laravel.log only when the audit decides to force-resume — pure noop runs are silent. we'll add an info-level heartbeat in a future acelle release to make it easier to monitor.
    4. admin (edited)
      Yes — strict alignment requires the From: domain to match exactly. Subdomain-level (`bounce.example.com` vs `example.com`) passes relaxed but fails strict. Most operators run relaxed; the rare strict-DMARC setups need explicit subdomain DKIM configuration.
  3. nadia.r.cl
    confirming: at 500k+/day, MySQL becomes the bottleneck before workers. Moving to Redis queue freed up DB headroom for everything else.
    1. admin
      Appreciate the data point. Your numbers align with what our larger-volume customers report; helpful to see a third confirmation.

More in Email Infrastructure