Hello. I am desperate for help and this topic is the closest thing I could find to the problem I am experiencing. I have an Exchange 2003 server behind our company firewall which is configured both with port forwarding and mail forwarding to the mail server using an accepted recipient table in Postfix. The system has been running for years with no issues but we recently decided to switch to a different domain name that we also own. So, I added the secondary domain to the server by editing the default recipient policy and making sure the authoritative box was checked. Everything went very smoothly and new addresses were created for all the users in the system reflecting the secondary domain name.
Here is where it gets strange. The recipient policy is setup to incorporate user names for both domains as follows: %g%1s@domain1.com and %g.%s@domain2.com
This worked and the names are set up properly as I wanted. However, when I try to send new messages from outside the firewall to
first.last@domain2.com the transport fails (as seen in the exchange logs) but no NDR is sent to the outside originator. It also fails if I try to reply to a message that originated from
first.last@domain2.com.
The really weird thing is that I can successfully send new messages to
first@domain2.com as this email is also set up in AD for each user (but is not specifically part of the recipient policy). Even weirder, I can send a message successfully to the first name with first letter of the last name such as
DaveP@domain2.com and that email address is not set up for that user in AD at all.
Switching the Primary Domain from domain1 to domain2 does not seem to have any effect.
Everything seems to show that the firewall is passing things to the mail server properly and I can see the messages are getting to the mail server in the Exchange logs but the only variation that still fails is
first.last@domain2.com.
Can you help me resolve this strange issue?