Rewrite From: address field with Exchange 2010 Transport Server

pwashburn1224 used Ask the Experts™
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:

A member of the list might Reply to an email sent from the list.  The reply would be to and "From"  that person, say

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 and "Resent" from

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 "".  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:  Then our DMARC policy and DKIM and SPF would all be happy.

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 and then rewrite the From: to be From: before sending it out of Exchange.

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.
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Do you have the Edge Transport role installed in your organization? It is a requirement to do address rewriting with Exchange.

Here is a guide -



I'm running Exchange 2010 on one Win2008 R2 server.  So all roles are on the one server.  I see Hub Transport under both Organization Configuration and Server Configuration in EMC.

Doesn't that combine several roles including the Transport Server role?  I know I've played with both Send Connectors and Receive Connectors there.
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.

Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!


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.
You've encountered one of the problems of adding external recipients to distribution groups. I'm afraid I don't have a solution.

Most Valuable Expert 2014
This is a well known issue with Yahoo and there is nothing you can do about it.

I hate giving out a Google search, but this one will show you the history:

It has broken most list managers, not only Exchange is affected.

The only solution is to stop using Yahoo.


Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial