Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 810
  • Last Modified:

Exchange2003 retired Internet domain name auto-reply message.

I'm using Exchange 2003 and have two domains.  domain1.com and domain2.com.  Users can receive email from both domains so user@domain1.com and user@domain2.com are both valid.  We have retired domain1.com and want to let people know through a reply message that we've retired domain1.com and to use domain2.com.

I removed the domain1.com from users email address but now external people receive a non-delivery message which is not cool.  How can tell external people to use domain2.com instead of domain1.com in an automated fashion?
0
kucelkj
Asked:
kucelkj
  • 3
  • 2
  • 2
  • +1
2 Solutions
 
czcdctCommented:
You shouldn't have retired it.
What you needed to do was to run both in parallel for the full term of a domain registration (couple of years?) but obviously only have the primary addresses on signatures and stationary etc.
Sending automated answers is an unreliable and unpredictable solution which should be avoided.
0
 
ArneLoviusCommented:
I agree with czcdct, but if you really want to do what you've asked for, I'd create a mail enabled public folder with every address that you have previously used as extra addresses, and then set a rule on it to reply with your message unless it's to teh address that you're sending from in which case to delete it.

if you set a short age time on the pf then the messages won't build up.
0
 
mario_andresCommented:
This is all very true fellows. I have traveled this  road. I added a line at the beginning of my disclaimer stating that the company's domain name has changed.  My users still have the  the old addresses just for NDR's sake....I hate to NDR anything that may be client /customer related.
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
kucelkjAuthor Commented:
Allow me to clarify.
1. Both addresses are in tact and we're receiving email for both domains.
2. I tried the following solution but it didn't work.
2a. remove address domain2.com from a test user
2b. use MS KB article 295653 to have all NDR's sent to a specific user address of RetiredDomain (that worked just fine)
2c. use MS KB article 291956 and prepared a server-side rule for user RetiredDoman to automatically reply with a specific message (that didn't work).
3. I'm looking for another creative solution like the one I tried above.

Thanks for all replies with ideas,

-Ken
0
 
mario_andresCommented:
if you remove this user's the proxy address the rule will never be tiggered/process.  you would have to leave the proxy addressese in place and create a rule to accomplish steps 2b and 2c.
0
 
czcdctCommented:
Yes. Stop with all this complex step based stuff.
Just have the recipient policy with both domains and make sure the new domain is primary. That's it. Period. Finish. Do nothing else.
0
 
kucelkjAuthor Commented:
Czcdct,

You're suggestion is to do nothing at all.  Please provide good useful feedback or drop out of the conversation.
0
 
czcdctCommented:
You read it wrong. Everyone is telling you to do pretty much nothing at all.

You said:
"I removed the domain1.com from users email address but now external people receive a non-delivery message which is not cool.  How can tell external people to use domain2.com instead of domain1.com in an automated fashion"

You must now:
1. Put domain1.com back into the recipient policy and make sure everyone gets the address.
2. Make sure domain1.com is the secondary domain.
3. Make sure everyone's signatures are reflecting the right domain name.
4. Make sure the disclaimer software (whatever you use) has a single liner to state that you're changing your domain name.

That's it.
You should not, as everyone has agreed, do anything with auto replies. As you saw from ArneLovius the other option is very onerous.
0
 
ArneLoviusCommented:
kucelkj,

It might be usefull if you explained exactly what are you trying to acheive here, and why.

Otherwise you have been provided with two solutions, one to acheive exactly what you have asked for, and another that is the better way of dealing with a domain name change.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now