EmailsAndMore is built around deliverability. This policy lays out the standards we maintain, the requirements every sender must meet, and concrete SPF, DKIM, and DMARC guidance so your mail consistently reaches the inbox.
Our commitments
- Maintain warmed, segmented IP pools matched to sender reputation.
- Enforce SPF, DKIM, and DMARC alignment on every outbound message.
- Surface real-time bounce, complaint, and engagement signals.
- Monitor major blocklists and provider feedback loops continuously.
- Process unsubscribes automatically and immediately.
Sender requirements
- Authenticate your sending domain with SPF, DKIM, and DMARC before going live.
- Send only to recipients with documented, verifiable consent.
- Maintain a complaint rate below 0.1% and a hard-bounce rate below 2%.
- Include a clear sender identity, physical address, and one-click unsubscribe in every commercial message.
- Re-engage or remove subscribers with no activity in 6–12 months.
- Warm up new domains and IPs gradually — the platform's adaptive warm-up handles this automatically when enabled.
SPF setup
SPF (Sender Policy Framework) tells receiving servers which hosts may send mail for your domain. Add the following TXT record at the root of your sending domain (replace any existing SPF record — only one is allowed per domain):
Type: TXT Host: @ Value: v=spf1 include:spf.emailsandmore.in -allUse -all (hard fail) in production. Use ~all (soft fail) only while testing.
DKIM setup
DKIM (DomainKeys Identified Mail) cryptographically signs your messages so receivers can verify they weren't tampered with in transit. We provide two CNAME records per sending domain — copy the values shown in your dashboard:
Type: CNAME Host: eam1._domainkey Value: eam1._domainkey.emailsandmore.in Type: CNAME Host: eam2._domainkey Value: eam2._domainkey.emailsandmore.inWe rotate signing keys periodically — using CNAMEs (rather than raw TXT records) means rotations happen with no action on your side.
DMARC setup
DMARC ties SPF and DKIM together and tells receivers what to do with messages that fail either check. Start in monitoring mode, then enforce:
Type: TXT Host: _dmarc Value: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com; pct=100; adkim=s; aspf=sRecommended rollout:
- Week 0–2:
p=none— collect aggregate reports, fix any unauthenticated sources. - Week 2–6:
p=quarantine; pct=25, then 50, then 100. - Week 6+:
p=reject— the strongest protection against spoofing.
List hygiene
Built-in suppression lists handle bounces, complaints, and unsubscribes automatically. Run a re-engagement campaign before removing inactive subscribers — winning back an opt-in is cheaper than acquiring a new one.
Reputation management
We may throttle, pause, or require list cleaning when an account's metrics exceed safe thresholds. These actions protect deliverability for every sender on the platform.
Support
Deliverability questions: info@emailsandmore.in.