Static from/reply-to sender address | Community
Skip to main content
K
Khyra
Level 3
December 14, 2022
Solved

Static from/reply-to sender address

  • December 14, 2022
  • 2 replies
  • 2896 views

I'm trying to put my Marketo from/reply-to sender address on a type of allow-list so that when emails deployed from Marketo to Outlook recipients do not have a BULK/MARKETING disclaimer. I was advised that in order to do so, the Marketo from/reply-to has to be static.

 

I've removed all token elements from my Marketo from/reply-to sender address in question, and it is still not static.... anyone have any idea what other change I can look into to make it static? I'd also like to mention that I'm on a shared IP in case that plays into anything.

 

Thank you!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Darshil_Shah1

As long as your email content is apt, SPF/DKIM, branding domain, etc. is set up and verified properly, you're sending out emails with your branded domains, and following other deliverability best practices, you should ideally be able to reach recipients' primary inbox and avoid any disclaimers as well (as Sandy says, using static email addresses might not be relevant today).

 

Also, are you seeing emails referencing token values even after replacing them with static values for the email from/reply-to email addresses? It may sound a little silly, but I hope you would have approved the email post updates.

 

2 replies

SanfordWhiteman
SanfordWhiteman
Level 10
December 14, 2022
I'm trying to put my Marketo from/reply-to sender address on a type of allow-list so that when emails deployed from Marketo to Outlook recipients do not have a BULK/MARKETING disclaimer. I was advised that in order to do so, the Marketo from/reply-to has to be static.

Sounds like some old-school FUD.

 

Outlook (and Microsoft-hosted Exchange/O365) do not add you to an allow list based only on sending from an (easily forged) From: header address.

    Darshil_Shah1
    Community Advisor and Adobe Champion
    Darshil_Shah1Community Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    December 14, 2022

    As long as your email content is apt, SPF/DKIM, branding domain, etc. is set up and verified properly, you're sending out emails with your branded domains, and following other deliverability best practices, you should ideally be able to reach recipients' primary inbox and avoid any disclaimers as well (as Sandy says, using static email addresses might not be relevant today).

     

    Also, are you seeing emails referencing token values even after replacing them with static values for the email from/reply-to email addresses? It may sound a little silly, but I hope you would have approved the email post updates.

     

    K
    KhyraAuthor
    Level 3
    December 16, 2022

    Hi there,

    Thanks for your input.

     

    My Marketo instance is being used to to send internal employee communications and the idea is that we are trying to remove those inbox labels for that specific use case. 

     

    And yes, the latest updates to the email have been approved and there are no token elements in my email from/reply-to email address fields.

    Darshil_Shah1
    Community Advisor and Adobe Champion
    Darshil_Shah1Community Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    December 16, 2022

    That's great! So now you must be seeing static email addresses in the from/reply-to fields. 🙂

    Terms & ConditionsAccessibility statement

    Loading footer...