Email delivery¶

Loveshack sends everything — sign-in links, confirmations, and digests — through the WordPress wp_mail() API, using the theme's shared HTML email layout.

That means Loveshack does not care which provider you use. Whatever handles wp_mail() handles Loveshack's mail.

Why this matters more than usual¶

Because authentication is passwordless, broken email means nobody can sign in. Email is not a nice-to-have on a Loveshack site; it is part of the login path. Configure it before launch, not after.

FluentSMTP¶

FluentSMTP is the recommended transport, and Loveshack detects it directly in LoveShack → Subscriptions, showing its current status.

Recommended settings for most providers:

Setting	Value
Encryption	TLS
Port	587

Any SMTP or transactional provider works — Postmark, Mailgun, SES, Fastmail, your own server. The provider matters less than the authentication being correct.

Sender identity¶

Set the sender name and address in LoveShack → Subscriptions.

Use an address on your own domain

A sender address at a free mail provider will fail SPF and DKIM alignment and land in spam. Use something like hello@example.com on the site's own domain, with SPF, DKIM, and DMARC records published for it.

Deliverability checklist¶

SPF record includes your sending provider
DKIM signing is enabled and verified at the provider
DMARC record is published
The From address is on the site's domain
A test message arrives in the inbox, not spam
The plain-text variant renders readably

Testing¶

Loveshack includes a test-email path for digests so you can check rendering and delivery without publishing a post or waiting for the schedule.

For sign-in mail, the fastest check is to register a throwaway address and confirm the link arrives and works.