Deliverability
Your reputation, guarded while you sleep.
Your SES account and your domain carry your sending reputation. HeySender checks the setup, handles every bounce and complaint, and pauses a sender on its own when the numbers turn bad, before a mailbox provider does it for you.
Free checklist, no signup
Six things Gmail checks before it trusts your SES domain
Google and Yahoo tightened their rules for bulk senders in 2024. If you send marketing email from SES, this is the short version of what they look at. Work through it whether you ever use HeySender or not.
- DKIM signs your mail with your own domain. SES gives you three CNAME records. Until they are published, your mail is signed as Amazon's, not yours.
- SPF passes. SES handles this for its own sending domain. It lines up with your From address only once you set a custom MAIL FROM domain in SES.
- You have a DMARC record. Start with
p=noneso nothing breaks, read the reports, then tighten it. - Marketing email has one-click unsubscribe. That means the
List-UnsubscribeandList-Unsubscribe-Postheaders, not only a link in the footer, and the unsubscribe has to take effect within two days. - Your spam complaint rate stays low. Google asks senders to stay below 0.1% and to never reach 0.3%. Check it in Google Postmaster Tools.
- You stop mailing addresses that bounce. Keep sending to dead addresses and it reads as a list nobody maintains.
Based on Google's published email sender guidelines. Check the current version before you rely on a number.
What HeySender does about it
From connection to every send, handled.
A connection that never holds your AWS keys.
Launch the ready-made CloudFormation stack and HeySender works through a role with its own external ID. Disconnect by deleting the stack, and access is gone.
The DNS records, written out for you.
Add a domain and HeySender shows the DKIM and DMARC records to publish, then keeps checking until AWS confirms them.
Plain language when something is wrong.
Role refused, domain not verified, account still in the sandbox, feedback not flowing. Each state says what it means and the one thing that fixes it. Quota, sandbox and identity status are re-checked every 10 minutes.
Proof that bounces really come back.
HeySender sets up the SES configuration set and the notification topic, then sends a test to the SES mailbox simulator. Sending stays locked until the signed event for that test has actually arrived, so no bounce is ever lost.
Bounces and complaints suppress on arrival.
A hard bounce or a complaint suppresses the address for good. Those suppressions apply to transactional email too, so a receipt never goes to an address that already bounced.
An automatic pause before real damage.
HeySender watches complaint and hard bounce rates per sender. When they climb past safe levels, that sender pauses and your admins get a notification saying why, so a bad list can't ruin a good domain.
Honest numbers
Opens and clicks, with the caveats printed on the label.
Apple Mail Privacy Protection opens emails nobody read, and security scanners click links nobody clicked. HeySender counts opens from privacy proxies and likely automated clicks separately, so you are not steering by inflated numbers.
HeySender tracks opens and clicks itself instead of letting SES rewrite your links, so unsubscribe links always stay intact.
No platform can guarantee the inbox, including this one. HeySender enforces good practice and shows you the evidence. What you send, and who you send it to, is still yours.
Using SMTP instead of SES?
You can connect a regular SMTP server. It sends fine, but SMTP gives no bounce or complaint feedback, so the automatic suppression and the automatic pause have nothing to work with. SES is the recommended route for anything beyond small volumes.
Keep your domain out of the spam folder without watching it every day.
HeySender is not open for signups yet. Request an invite and start on the free plan.