The service that sends your website's email. It makes sure an enquiry from your form actually lands in your inbox — and not unseen in spam.
The form says “sent”, but the email never arrives. You find out weeks later.
Every enquiry lands in the inbox, and I can check whether it was delivered.
- The mail comes from the server, not the browser
Your address therefore isn't in the page source and isn't harvested by scrapers.
- The sender address is authenticated
Entries in your domain's naming system let the recipient verify the mail really is from you — that's the difference between inbox and spam folder.
- Delivery is traceable
Delivered, opened, rejected — it's on the record instead of a guess.
- Bots run into nothing
An invisible field in the form and a send limit per connection keep most of the junk out.
- Form submitted
- Check for bots
- Resend sends
- In your inbox
A check sits between form and inbox: a hidden field only machines fill in, and a limit on how often one connection may send.
A service that sends system email through an interface rather than a classic mail server. It sets up the records other inboxes use to confirm the mail really comes from your address, and logs whether it was delivered.
- Route
- interface, not a mail server
- Authenticity
- SPF, DKIM, DMARC
- Proof
- delivery log
- Purpose
- system email
Delivering enquiries from the form
Confirmation emails to your customers
Proof that a message actually arrived
It isn't meant for newsletters to large lists. That needs a tool with unsubscribe handling — otherwise marketing quickly becomes a legal problem.
When someone here picks “Send by email”, the message travels to me along this route.