Using a Different "From" Address than Sending Domain

[FourFold_Sltns]

Hello,

I'm hoping someone can help me follow best practices with a specific use case.

Per I'm planning to set up a subdomain as my org's primary sending domain - something like mail.brand.com. This seems to be the recommended way to go for marketing emails in order to protect our primary domain's sending reputation.

However, for a nurture campaign, I would like to use a personalization token for the "From" and "Reply To" addresses so that they appear to come from the contact owner (in this case, the sales rep). These email addresses would utlize the primary brand domain - something like john@brand.com.

Are there any pitfalls with sending emails in this manner?

Thanks!

[FourFold_Sltns]

Great, thank you Karsten!

[karstenkoehler · Accepted solution]

Hi @FourFold_Sltns,

As far as I know, you can't have it both ways – you need to connect and authenticate the domain you want to send from.

You probably don't want to try to work around this either: Email service providers check the sender details against the authentication and penalise discrepancies. If you do manage to send from a different domain (cosmetically) than the authenticated one (in the background), your email deliverability is likely going to suffer.

Best regards

[FourFold_Sltns]

@karstenkoehler thanks for the quick reply and advice!

So it sounds like if I use the personalization token for the "From" address, then the sending domain would be whatever domain is set up with the sales rep's email. In my example, this would be "brand.com".

Then if I wanted to, I could still send out other, non-personalized, marketing emails with the subdomain (mail.brand.com) as the sending domain. For example, these might go to a less-engaged list of contacts.

Am I understanding that correctly?

Thanks again!

[karstenkoehler]

@FourFold_Sltns exactly – a personalization token in the from or reply-to field will still reference the matching connected email sending domain.