Skip to content

SendingDeliverability

Deliverability best practices

Deliverability is the share of your email that lands in the inbox, not in spam or bounced back. It depends on your sending reputation, your DNS authentication, the quality of your list, and what you write.

Last updated

Why deliverability matters

Gmail, Outlook and other mailbox providers decide between inbox and spam based on your sender reputation. You build it over weeks of clean sending. One bad send can cost you months of repair.

Understand a delivery failure

Open a message's delivery details in your inbox or Analytics. For each recipient you see the latest outcome, an explanation, and the receiving server's original response.

The page opens with how many recipients reached each outcome. Recipients that need attention (bounced, not delivered, complained) come first in the list. Filter the list by status or search it by address. The event log below shows the latest events, and Show all lists the rest.

A soft bounce shows as "Not delivered", which replaced the old "Deferred" label. That attempt is over and Shipmail does not retry it. The API event status is still deferred. A temporary cause does not mean the email is still waiting in a queue.

  • Orange/Wanadoo spam rejection (OFR_506): the receiving provider suspected spam but does not say why. Check your domain authentication, your content and links, and whether the recipient expects your email. If the block continues, contact Shipmail support with the message ID.
  • Relay access denied: the receiving server refused mail for this recipient. Confirm the address, then ask the recipient through another channel to have their administrator check mail routing before sending again.
  • Mailbox full: ask the recipient to free up space, then send a new email. For an invalid address, fix or confirm it first.

If Shipmail does not recognize the cause, it says so and still shows the server response. New delivery events update the details as they arrive. Reload to see them. A new send is a separate attempt, so the earlier rejection stays on record.

Authentication

Authentication proves to the receiving server that a message really comes from your domain and nobody changed it on the way. It uses three DNS-based checks:

  • SPF (Sender Policy Framework) declares which servers may send email for your domain. The receiving server compares the sending IP with your SPF record.
  • DKIM (DomainKeys Identified Mail) signs every outgoing message. The receiving server checks the signature against a public key in your DNS. A valid signature means nobody altered the message.
  • DMARC (Domain-based Message Authentication, Reporting and Conformance) tells receivers what to do when SPF and DKIM fail. For a domain that only Shipmail sends from, use p=reject. If other services still send from the same domain, publish a temporary custom policy until every sender passes.

Shipmail sets up DKIM when you add a domain. You add the SPF and DMARC records at your DNS host. See the DNS records page for the exact values. If a record stays pending or does not match the dashboard, use the domain troubleshooting guide.

List hygiene

Nothing hurts your reputation faster than sending to dead addresses or people who do not want your email.

  • Remove bounced addresses immediately. Shipmail adds hard bounces to your suppression list for you, and pauses an address for 30 days after 3 soft bounces in 14 days. Do the same in any list you keep elsewhere.
  • Use the suppression list. Before you import contacts into a new tool or campaign, check GET /api/v1/suppressions and exclude any matches. A complaint stops only the kind of email it was about: one about a newsletter has scope marketing, so keep that person off marketing lists, but your transactional email still reaches them.
  • Never buy email lists. Purchased lists contain spam traps, invalid addresses, and people who never asked to hear from you. One campaign to a purchased list can get your domain blocklisted.
  • Re-confirm inactive subscribers. If a contact has not opened or clicked in 90 days, send one email asking if they still want to hear from you. Remove anyone who does not respond.

Domain warm-up

Mailbox providers distrust a new domain that suddenly sends a lot of email. Build up volume slowly so receiving servers have a history to judge you on before the volume arrives.

  • Start slow. Send to your most engaged recipients first. Opens and replies tell providers that people want your email.
  • Increase volume gradually. Double your daily sends every few days rather than jumping from 50 to 10,000 overnight.
  • Pace yourself. Shipmail does not enforce a ramp for mailbox email: your plan's daily limit applies from the first day after you pay. Staying well under it for the first weeks still helps your email reach the inbox.
  • New newsletter domains warm up too. For its first two weeks after verification, a newsletter domain starts at 500, then 2,000, then 5,000 newsletter emails in 24 hours, and each clean day doubles what it may send next. Shipmail spreads a larger newsletter over several days for you and sends to your most engaged readers first. A domain whose root is older than 30 days, and already runs Shipmail mailboxes, skips this. See the sending policy.

Monitoring

Watch these numbers all the time:

  • Bounce rate. Keep bounces below 2%. Shipmail slows down your sending at 5% once at least 25 recipients failed in 7 days, and lifts the slow-down when the rate is back under 4%.
  • Complaint rate. Keep complaints below 0.05%. Shipmail slows down your sending at 0.1% once at least 3 recipients reported spam in 7 days (2 for an organization in its first week).
  • Analytics dashboard. Analytics shows bounce and complaint rates, delivery counts, and suppressions in real time. Owners see the whole organization. Members see the mailboxes they can access.
  • Webhooks. Add a webhook endpoint to get bounce, complaint, and delivery events as they happen, so your app can act on them right away.

Common spam triggers

Spam filters score every incoming message. These patterns raise the score:

  • ALL-CAPS subjects. Filters flag uppercase subject lines. Shipmail warns you when a subject over 10 characters is mostly uppercase.
  • Too many links. A message full of URLs looks like phishing. Keep links few. Shipmail caps a standard outbound message at 20 unique URLs. Newsletter preflight fails when there are too many clickable destinations and warns when there are many remote resources.
  • No plain-text version. Filters flag HTML-only messages more often. Always include a text part.
  • Misleading subjects. Subject lines that do not match the body, such as "Re:" on a first message, violate CAN-SPAM and trip filters.

List-Unsubscribe

For marketing and bulk email, include a List-Unsubscribe header. Recipients can then opt out from their mail client instead of marking you as spam. Gmail and other providers show an unsubscribe button when the header is there.

  • Add a List-Unsubscribe header with an HTTPS URL that processes the unsubscribe.
  • Add a List-Unsubscribe-Post header with the value List-Unsubscribe=One-Click to support RFC 8058 one-click unsubscribe.
  • Honor unsubscribe requests immediately. Every email you send after one invites a spam complaint.