Dedicated vs Shared IP Address
Choosing between a dedicated and shared IP affects your sender reputation and warmup requirements. This guide compares both options with clear recommendations.
When you click Send Campaign in AcelleMail, a chain of events fires before the email reaches the inbox.
AcelleMail adds each recipient to a Laravel queue. Queue workers pick up jobs and hand them to your configured SMTP server (or local MTA like Postfix).
Your MTA needs to find where to deliver the message. It queries DNS for the recipient domain's MX records:
dig MX gmail.com
# Returns: gmail-smtp-in.l.google.com (priority 5)
The MX record points to Google's receiving server.
Your server opens a TCP connection on port 25 (or 587/465) to Google's server:
→ EHLO mail.yourdomain.com
← 250 mx.google.com at your service
→ MAIL FROM: <bounce@yourdomain.com>
← 250 OK
→ RCPT TO: <user@gmail.com>
← 250 OK
→ DATA
→ [email headers + body]
→ .
← 250 Message accepted
→ QUIT
Modern servers require STARTTLS or connect over port 465 (SMTPS). This encrypts the SMTP conversation, preventing eavesdropping in transit.
The receiving server runs three checks:
All three must pass for the best inbox placement.
Choosing between a dedicated and shared IP affects your sender reputation and warmup requirements. This guide compares both options with clear recommendations.
Understand how AcelleMail breaks campaigns into queue jobs, processes them with workers, handles retries, and tracks delivery status.
The Return-Path header controls where bounce notifications go. Learn how it differs from the From address and why alignment matters for DMARC.
Understand how AcelleMail breaks campaigns into queue jobs, processes them with workers, handles retries, and tracks delivery status.
Choosing between a dedicated and shared IP affects your sender reputation and warmup requirements. This guide compares both options with clear recommendations.
AcelleMail is the self-hosted email marketing platform you control end-to-end.
View Pricing