Should I use a new domain or a new from address for software email alerts?

Marketer from Email Geeks suggests that assuming there are no current issues with the sending reputation, using a new address with the current domain is preferable to creating a brand new domain. Using a different DKIM key for the notifications would also be a good idea, and it's also fine to use a sub-domain in the return path address if that's how the software works. He suggests to make sure that they are easy to turn off.

Email marketer from Omnisend mentions one option is to set up a dedicated IP for transactional mail, they also make a point of recommending a different from domain to your main website as this will also stop click tracking links from impacting your sending reputation if you were to receive abuse or a spam attack.

Email marketer from Automizy recommends you segment emails based on purpose (marketing, transactional) and create separate sending profiles, so different issues won't impact others negatively.

Email marketer from Mailjet explains the importance of separating transactional and marketing emails. Using a different subdomain or dedicated IP for each type can help improve deliverability and maintain sender reputation.

Email marketer from SendGrid explains that warming up a new domain is crucial for deliverability. Sending emails from a new domain without warming it up can lead to deliverability issues and spam folder placement.

Email marketer from Reddit advises using a subdomain (e.g., alerts.yourdomain.com) for software alerts. This allows you to isolate the reputation of these emails without starting from scratch with a completely new domain.

Marketer from Email Geeks advises, if possible, to send software's notifications though an ESP (either the current one with different DKIM etc., or a specialist one for transactional emails). If it has to be kept internal, then set up a dedicated MTA for the job and have it relay out through a different IP than the one the corporate MTA uses.

Email marketer from Stack Overflow suggests implementing SPF, DKIM, and DMARC records for both the main domain and any subdomains used for email sending to improve deliverability and protect against spoofing.

Marketer from Email Geeks explains that one of the main problems with using a new domain is that you'll need to build up its sending reputation. This can take months, and with a low volume of emails, that task can be very challenging. Another issue is brand recognition; customers already know your current domain and likely have it whitelisted, so sending emails from a new domain can cause confusion and possible filtering.

Email marketer from Neil Patel's Blog explains that sender reputation is tied to the domain. Sending from a new domain means starting with a fresh reputation, which can lead to deliverability issues until the reputation is built. Using a subdomain can be a good middle ground.

Email marketer from Litmus emphasizes the importance of brand recognition in email marketing. Using a familiar domain or subdomain in the 'From:' address helps build trust and encourages recipients to engage with the emails.

Email marketer from GMass says that sending cold emails using a separate domain allows one to isolate your main domain's reputation and safeguard it from being affected if the cold emails receive spam complaints.

Expert from Word to the Wise explains that separating sending infrastructure (including domains and IPs) for different email streams (transactional, marketing, etc.) is crucial. This helps isolate reputation issues and protects the deliverability of critical emails.

Expert from Word to the Wise Staff highlights the importance of IP and domain reputation, emphasizing that both need to be carefully managed. Using a new domain requires building a reputation from scratch, whereas leveraging an existing, reputable domain can be advantageous if managed correctly. Consider deliverability and list hygiene before deciding.

Documentation from DMARC.org explains that DMARC helps protect your domain from email spoofing and phishing attacks. Implementing DMARC policies is essential for maintaining a good sender reputation and improving email deliverability.

Documentation from IETF explains that the 'From:' address in an email header identifies the sender. While technically you can use any address, using a consistent and recognizable address builds trust with recipients.

Documentation from Amazon Web Services explains that using a dedicated IP address for transactional emails can help maintain a separate reputation from marketing emails. This allows for better control over deliverability for critical alerts.

Documentation from Microsoft explains the sending limits on Office 365 and advises how to not hit those limits with bulk/transactional email by seperating them from corporate email traffic. You may also wish to consider third party transactional email services.