Skip to main content
JetEmail Marketing uses JetEmail’s delivery network, sending pools, and reputation monitoring. Your domain configuration, list source, content, and sending behaviour still determine how receivers treat your mail.

​
Authenticate every sender

Publish every record shown under Marketing → Domains:
  • Return-path CNAME
  • Two DKIM CNAME records
  • DMARC TXT record
  • Branded tracking CNAME
Wait for the domain to become Active before using it in a template. Keep the tracking hostname unproxied. Authentication provides:
  • DKIM signing for message integrity
  • An aligned return path for SPF and bounce handling
  • A DMARC policy for domain alignment
  • Branded links for open and click tracking
See Domains & DNS.

​
Send only with permission

Build audiences from people who reasonably expect the messages you send. Record the source and time of consent in your system or as appropriate contact properties. Do not use:
  • Purchased lists
  • Scraped addresses
  • Old lists with no reliable consent history
  • Role accounts collected without context
  • An import that silently changes unsubscribed people back to subscribed
Email and privacy obligations depend on the sender, recipient, jurisdiction, and message. These guides describe JetEmail controls, not legal advice. Obtain appropriate advice for the rules that apply to your organisation.

​
Keep suppression signals

JetEmail contact statuses include unsubscribed, bounced, and complained. Keep those records so later imports and campaigns do not repeat unwanted delivery.
  • Unsubscribe instead of deleting when preserving an opt-out
  • Investigate repeated bounces
  • Stop sending to complained addresses
  • Import suppression status when migrating providers

​
Separate sending streams

Use a dedicated marketing subdomain, such as news.example.com, instead of mixing campaigns with employee or critical application mail. Separate subdomains make it easier to:
  • Recognise mail streams
  • Diagnose DNS and reputation
  • Change campaign tooling without changing corporate mail
  • Limit the effect of a marketing-volume spike

​
Warm new reputation gradually

A new domain or dedicated IP has little receiver history. Start with smaller groups of recently engaged recipients and increase volume consistently. Avoid:
  • Sending the entire historical database on day one
  • Large and irregular spikes
  • Rapid changes in sender identity
  • Continuing a campaign after bounce or complaint rates deteriorate
A dedicated IP isolates reputation but also removes the benefit of a shared pool’s established traffic. Use one only when your consistent volume and operational discipline justify it.

​
Build trustworthy content

  • Use a recognisable from name and reply-to address
  • Make the subject match the body
  • Keep links on expected, secure domains
  • Include meaningful text, not one large image
  • Add alt text
  • Include sender identification and a working unsubscribe link
  • Test HTML and plain text
  • Avoid URL shorteners and misleading calls to action

​
Monitor after every send

Use the broadcast report for campaign results and Marketing Metrics for trends. Watch:
  • Delivery and rejection rates
  • Bounces
  • Deferrals by recipient provider
  • Complaints
  • Unique clicks
  • Sudden differences between broadcasts and non-broadcast email
Open individual logs to read the receiver response before changing infrastructure or content.

​
A practical incident flow

1

Pause avoidable volume

Stop new campaigns or pause the affected workflow while you establish the scope.
2

Segment the evidence

Compare timeframe, send type, sender domain, audience source, and top recipient domains.
3

Read receiver responses

Filter logs for deferred and rejected messages and inspect their timelines.
4

Check DNS and sender identity

Confirm the exact Marketing domain is active and the template uses it.
5

Correct list or content causes

Remove invalid acquisition sources, preserve suppressions, and fix misleading or broken content.
6

Resume gradually

Start with engaged recipients and monitor the same metrics before increasing volume.

​
Preflight checklist

  • Domain is active and tracking CNAME is DNS-only
  • Sender and reply-to are monitored
  • Audience source and consent are known
  • Unsubscribed, bounced, and complained contacts remain suppressed
  • Template includes unsubscribe and sender details
  • Test renders correctly in real inboxes
  • Links and merge fields work
  • Schedule and audience count are expected
  • Metrics and logs will be reviewed after sending