All 15 Email & Notifications questions
More in Email & Notifications
What is the difference between the 'to', 'cc', and 'bcc' fields when sending an email programmatically, and why does 'bcc' matter for privacy? Why should sending an email typically happen in a background job rather than synchronously within an HTTP request handler? How would you send a push notification from a Node.js backend to a mobile app using Firebase Cloud Messaging (FCM)? What is email template rendering, and how might you use a templating engine to generate dynamic HTML emails in Node.js? What is an unsubscribe mechanism, and what specific requirements does it need to meet for compliance with regulations like CAN-SPAM? What is the difference between sending SMS via a provider's REST API (like Twilio) versus using SMTP-based email in terms of a Node.js integration? How would you test that a Node.js application correctly sends emails without actually sending real emails during automated tests? What are SPF, DKIM, and DMARC, and why do they matter for a Node.js application's transactional emails actually reaching users' inboxes? How would you design a multi-channel notification system in Node.js that can send the same logical notification via email, SMS, or push depending on user preference? How would you implement rate limiting or throttling for outgoing notifications to avoid overwhelming users or violating a provider's sending limits?
Advertisement
Node.js › Email & Notifications

What is the difference between transactional email and marketing email, and why do most Node.js applications use separate providers or sending domains for each?

Intermediate

Answer

Transactional email is triggered by a specific user action and expected as part of using the product (password resets, order confirmations, receipts) -- it must be delivered reliably and promptly. Marketing email (newsletters, promotional campaigns) is sent in bulk to an opted-in list and is held to different deliverability and compliance standards (like unsubscribe requirements). Using separate sending domains or subdomains for each helps protect transactional email's sender reputation from being harmed by marketing email's inherently higher spam-complaint and bounce rates.
// Transactional: sent from a dedicated subdomain with strict reputation protection
from: 'noreply@transactional.example.com'

// Marketing: sent from a separate subdomain, isolating reputation impact
from: 'newsletter@marketing.example.com'
Real-world example A company separates its password-reset and receipt emails (sent from transactional.example.com) from its weekly newsletter (sent from marketing.example.com), so a spike in spam complaints against the newsletter doesn't damage the sender reputation of critical, time-sensitive transactional emails.

Common follow-ups: What compliance requirements (like CAN-SPAM or GDPR) specifically apply to marketing email that don't apply the same way to transactional email?;How do email providers like SendGrid support separating these two categories at the account or subdomain level?

Security;HTTP & HTTPS Modules
All 15 Email & Notifications questions