asked on
Rewrite From: address field with Exchange 2010 Transport Server
Non profit organization using Exchange 2010
Getting a lot of "Message rejected due to DMARC policy" NDR's back
We use Exchange 2010 Distribution Lists extensively with most entries on them being Contacts in Exchange/AD going to personal email addresses (AOL, Gmail, etc.)
Here's what a sample distribution list looks like:
DistributionList1@domain.o
Someone@yahoo.com
SomeoneElse@gmail.com
AnotherSomeone@aol.com
A member of the list might Reply to an email sent from the list. The reply would be to DistributionList1@domain.o
DMARC is in play now and it looks like Yahoo has set theirs to "Reject" and that's the reason I'm getting the NDR. The "From" field in the email show Someone@yahoo.com and "Resent" from DistributionList1@domain.o
Looks like the "From" address is the problem with DMARC. The receiving SMTP server looks at the From address, looks at our IP as we sent it and sees using DMARC/DKIM/SPF that we aren't an authorized email server for "@yahoo.com". And I get the NDR email in return.
It looks like I can rewrite the "From:" address using Exchange 2010 Transport Server role to be from our domain. As in From: DistributionList1@domain.o
So, how do I rewrite the From: address with Transport Server? I guess I would see the incoming email arriving at our Exchange server with To: showing DistributionList1@domain.o
I can't quite figure it out looking at the Microsoft TechNet hits I get in Google.
Some initial help and steering would be appreciated.
Getting a lot of "Message rejected due to DMARC policy" NDR's back
We use Exchange 2010 Distribution Lists extensively with most entries on them being Contacts in Exchange/AD going to personal email addresses (AOL, Gmail, etc.)
Here's what a sample distribution list looks like:
DistributionList1@domain.o
Someone@yahoo.com
SomeoneElse@gmail.com
AnotherSomeone@aol.com
A member of the list might Reply to an email sent from the list. The reply would be to DistributionList1@domain.o
DMARC is in play now and it looks like Yahoo has set theirs to "Reject" and that's the reason I'm getting the NDR. The "From" field in the email show Someone@yahoo.com and "Resent" from DistributionList1@domain.o
Looks like the "From" address is the problem with DMARC. The receiving SMTP server looks at the From address, looks at our IP as we sent it and sees using DMARC/DKIM/SPF that we aren't an authorized email server for "@yahoo.com". And I get the NDR email in return.
It looks like I can rewrite the "From:" address using Exchange 2010 Transport Server role to be from our domain. As in From: DistributionList1@domain.o
So, how do I rewrite the From: address with Transport Server? I guess I would see the incoming email arriving at our Exchange server with To: showing DistributionList1@domain.o
I can't quite figure it out looking at the Microsoft TechNet hits I get in Google.
Some initial help and steering would be appreciated.
ExchangeEmail Software
Last Comment
Simon Butler (Sembee)
ASKER CERTIFIED SOLUTION
Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
The Edge Transport server is a separate role that is installed on a dedicated server. If you a have a single combined role server then you do not have an Edge Transport server. There is a difference between the HUB transport and the EDGE transport.
-JJ
-JJ
ASKER
Was just going to edit my post to "Edge Transport" rather than "Transport Server", but was locked out while you were making your comment :)
Yup, only a single server in this organization, so no Edge Transport server.
So I guess that means I'm hosed in this case via that solution.
Any other possible solutions?
I wouldn't think we're the only ones having problems with DMARC and messages going out via Exchange Distribution Lists.
Yup, only a single server in this organization, so no Edge Transport server.
So I guess that means I'm hosed in this case via that solution.
Any other possible solutions?
I wouldn't think we're the only ones having problems with DMARC and messages going out via Exchange Distribution Lists.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
You've encountered one of the problems of adding external recipients to distribution groups. I'm afraid I don't have a solution.
-JJ
-JJ
SOLUTION
Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Doesn't that combine several roles including the Transport Server role? I know I've played with both Send Connectors and Receive Connectors there.