Email deliverability defined.
Email deliverability is the likelihood that a message you send reaches the recipient's inbox rather than the spam folder, decided by authentication (SPF, DKIM, DMARC) and the sender's reputation.
How email deliverability works
Sending an email and getting it read are two different things. Once a message is relayed to the receiving server, that server scores it and decides whether to drop it in the inbox, file it under spam, or reject it outright.
Two factors drive the score. The first is authentication: SPF lists which servers may send for your domain, DKIM cryptographically signs the message so tampering shows, and DMARC ties the two together and tells receivers what to do when they fail. The second is reputation, the running track record of your sending domain and IP, built from how recipients engage and how much spam has come from you before. Weak authentication or a poor reputation quietly sends good mail to spam.
This is exactly why a form backend takes over sending: FormWire emails your notifications and auto-responses from authenticated, well-reputationed infrastructure, so a submission does not vanish into a spam folder you never check.
What moves the deliverability needle.
Authentication
SPF, DKIM and DMARC prove the mail is really from your domain and untampered. Fail these and even genuine mail is treated as suspect.
Sender reputation
A domain and IP earn trust over time through low complaint rates and real engagement. Reputation is slow to build and quick to burn.
Managed sending
Routing over infrastructure that is already authenticated and warmed means your form mail inherits a strong reputation from day one.
Related questions
They are three DNS-based checks that prove an email is legitimate. SPF says which servers are allowed to send for your domain, DKIM adds a signature that reveals tampering, and DMARC combines both and instructs receivers what to do on failure. Together they are the baseline for landing in the inbox, and a form backend handles them so you do not have to.
Usually because they are sent as your visitor's address from a server not authorized to send for it, which fails authentication outright. The fix is to send from an authenticated address and use Reply-To for the human, which keeps the message deliverable while replies still reach the submitter.
How Reply-To keeps notifications deliverable →No. SMTP acceptance just means a relay took the message; deliverability is whether it survives the receiving server's filtering and reaches the inbox. A message can be accepted and still be filtered to spam, which is why the two are worth separating.
Especially so, because it goes to a stranger's inbox that has no history with you. If the confirmation fails authentication it lands in spam and the visitor thinks the form is broken. Sending over authenticated infrastructure is what makes automated confirmations trustworthy.
Want to see it working?
Read the docsGet every submission into the inbox.
Free tier forever. No credit card required.