You’ve set up your EmDash CMS site. Posts are flowing, comments are coming in. But when a new user registers, does the email actually arrive? If you’re relying on the default email configuration, the answer is probably “not reliably.” Let’s fix that.<\/p>\n
Transactional emails \u2014 password resets, comment notifications, form submissions \u2014 are the backbone of user engagement. EmDash gives you the tools to configure them properly. But the default setup isn’t built for production. Here’s how to swap it out for SMTP, and why you should.<\/p>\n
EmDash, in its early v0.1 state, ships with a simple email handler. It uses the underlying runtime’s mail capabilities \u2014 on Cloudflare Workers, that means the built-in email integration; on a local Node.js server, it likely falls back to a basic The problem is deliverability. Default mailers often land in spam folders. They lack authentication, rate limiting, and dedicated IPs. For a blog with ten visitors a month, that’s fine. For a business site sending password resets and order confirmations, it’s a liability.<\/p>\n EmDash stores its email settings in the admin panel under Settings > Emails<\/strong>. As of version 0.1, the interface is minimal. You won’t find security settings yet \u2014 that’s on the roadmap. But the core fields are there.<\/p>\n In your EmDash admin dashboard, click the gear icon. Select “Emails” from the left menu. You’ll see fields for SMTP host, port, username, password, and from address.<\/p>\n Three reliable options exist. I’ll compare them in the table below, but for most sites, SendGrid<\/a><\/strong> or Mailgun<\/a><\/strong> are the safest bets. Both offer free tiers that cover thousands of emails per month.<\/p>\n For SendGrid:<\/p>\n For Mailgun:<\/p>\n Use a verified domain (e.g., EmDash doesn’t have a built-in test button yet. You’ll need to trigger a real event \u2014 create a new user, submit a form, or publish a post. Check the inbox (and spam folder) to confirm.<\/p>\n Hit save. The settings are applied immediately. No server restart required.<\/p>\n Winner for most users:<\/strong> SMTP. It balances reliability and simplicity. The free tiers handle thousands of emails, and the setup takes minutes.<\/p>\n Some developers argue that for low-traffic sites \u2014 a personal blog, a small portfolio \u2014 the default email handler is fine. Why add complexity? EmDash is already serverless and cheap. Adding an external SMTP provider feels like overkill.<\/p>\n That argument holds only if you never send a critical email. The moment a user resets their password and the email doesn’t arrive, you’ve lost trust. And “small site” doesn’t mean “small consequences.” A single lost password reset can lock someone out permanently. The default mailer’s deliverability is inconsistent \u2014 even for tiny volumes. I’ve tested it on Cloudflare Workers: emails to Gmail and Outlook routinely land in spam. That’s not acceptable for any site that accepts user accounts or form submissions.<\/p>\n The five minutes you spend configuring SMTP eliminate that risk. You don’t need a paid plan for most providers \u2014 SendGrid’s free tier covers 100 emails per day, which is more than enough for a personal blog. The complexity is minimal. The cost is zero. There’s no good reason to skip it.<\/p>\nsendmail<\/code>codecodecode or a console log. Neither is enterprise-ready.<\/p>\nStep-by-Step: Configuring SMTP in EmDash<\/h2>\n
\n
\n
\n
\n
\n
smtp.sendgrid.net<\/code>codecodecode<\/li>\n587<\/code>codecodecode (TLS) or 465<\/code>codecodecode (SSL)<\/li>\napikey<\/code>codecodecode<\/li>\n\n
\n
smtp.mailgun.org<\/code>codecodecode<\/li>\n587<\/code>codecodecode<\/li>\n\n
noreply@yourdomain.com<\/code>codecodecode). This improves deliverability and prevents your emails from being flagged as spam.<\/p>\n\n
\n
Original Comparison Table: Email Delivery Options for EmDash<\/h3>\n
\n\n
\n \nOption<\/th>\n Deliverability<\/th>\n Setup Complexity<\/th>\n Cost (up to 10k emails\/month)<\/th>\n Key Limitation<\/th>\n<\/tr>\n<\/thead>\n \n Default mailer (built-in)<\/td>\n Low \u2014 often flagged as spam<\/td>\n None (zero config)<\/td>\n Free<\/td>\n No authentication; no dedicated IP; rate limits unclear<\/td>\n<\/tr>\n \n SMTP (SendGrid\/Mailgun)<\/td>\n High \u2014 authenticated, tracked<\/td>\n Medium \u2014 5 minutes<\/td>\n $0\u2013$20 (free tiers cover 100\u20135k emails)<\/td>\n Requires API key management; outbound only<\/td>\n<\/tr>\n \n Third-party API (SendGrid API, Mailgun API)<\/td>\n High \u2014 direct integration<\/td>\n High \u2014 requires custom plugin or hook<\/td>\n $0\u2013$20<\/td>\n Not supported natively in EmDash v0.1; needs developer work<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n The Counterargument: “Default Is Good Enough for Small Sites”<\/h2>\n
What About Transactional Email APIs?<\/h2>\n