3

right now my company structures our no reply emails like this:

noreply@[subdomin].[domain].com (example: [email protected])

I want to know if something like this is acceptable:

noreply_[subdomain]@[domain].com (example: [email protected])

Obviously the emails will send no problem, but my concern is being marked as spam when, of course, it's not, the user signed up with us. If you are wondering as to the why, it's due to how our Send Grid is set up.

I guess this boils down to: Is the first example any better than the second example in terms of deliverability?

Improve this question
2
  • The best practice is to not have a noreply email address. Were I not responsible for other peoples email I would penalise noreply emails on my Spamassassin instance - this is a dark pattern is illegal in some countries in the EU if configured to drop emails. Commented Jan 10, 2022 at 20:26
  • I agree, and I'll bring this up to management, but for the sake of argument, is the first example any better than the second example in terms of deliverability? Or all else being equal, they are effectively the same? Commented Jan 10, 2022 at 20:41

1 Answer 1

Reset to default
4

There is, of-course, no single correct answer here. Ignoring that noreply email addresses are not a good look I would argue -

[email protected] is likely to be MORE deliverable then [email protected] because the former is more likely be correctly set up with MX records, SPF, DKIM etc then the latter, so more likely to pass spam checks.

Similarly (but likely vastly less important) is that where spam filters are looking to penalise noreply email addresses, they might pick noreply@ out of a string more easily then noreply_ - but even if not, they are unlikely to penalise noreply_ worse then noreply@ (Indeed if anyone were to think this through carefully they might realise that having an _ and a domain provides more accountability then noreply@)

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.