fix(mailer): update mailer to use the EMAIL_DOMAIN

[waleedlatif1]

Summary

update mailer to use the EMAIL_DOMAIN instead of deriving the email from the NEXT_PUBLIC_APP_URL

Type of Change

• Bug fix

Testing

Tested manually.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sim	🛑 Canceled (Inspect)			Aug 8, 2025 8:13pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Skipped (Inspect)			Aug 8, 2025 8:13pm

[greptile-apps]

Greptile Summary

This PR updates the email sender configuration in the mailer service to prioritize the EMAIL_DOMAIN environment variable over the derived email domain from NEXT_PUBLIC_APP_URL. The change affects two functions in apps/sim/lib/email/mailer.ts:

1. Single email sending function (line 71): Updates the sender email logic from from || \noreply@${getEmailDomain()}`tofrom || `noreply@${env.EMAIL_DOMAIN || getEmailDomain()}``
2. Batch email sending function (line 135): Updates from \noreply@${getEmailDomain()}`to`noreply@${env.EMAIL_DOMAIN || getEmailDomain()}``

This change decouples email domain configuration from the application URL, which is particularly important for deployment scenarios where the app might be served from a different domain (like a CDN) than where emails should originate. The implementation maintains backward compatibility by falling back to the existing getEmailDomain() function when EMAIL_DOMAIN is not set. This improvement provides explicit control over email sender domains, which is crucial for email deliverability and DNS configuration with email service providers like Resend.

Confidence score: 5/5

• This PR is safe to merge with minimal risk as it's a straightforward configuration improvement
• Score reflects simple, well-contained changes with proper fallback mechanisms that maintain backward compatibility
• No files require special attention as the changes are isolated and follow good practices

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}