Exchange 2013 Email Disclaimer

Posted on 2014-12-15
Medium Priority
Last Modified: 2015-06-23
I am setting up Email disclaimer on our Exchange server 2013 SP1 under mail flow - rules.
If I select : " Apply to all messages" the disclaimer works fine for both emails send to internal and external addresses.

If I select  " recipient is located outside the organization" . The discalimer does not work. Email sent but no disclaimer appended to the bottom of the message.

Do I need to do anything else to make it works only for external address ?
Question by:BMRT
  • 3
LVL 11

Expert Comment

by:Marshal Hubs
ID: 40501953
Firstly check if you have allowed "External out-of-office messages and legacy out-of-office messages" through Exchange Management Console or not.  Also,  check this post http://technet.microsoft.com/en-us/library/dn600323(v=exchg.150).aspx and verify if you have missed something in setting the disclaimers or not.

Author Comment

ID: 40505276
Yes, I set it up the same way as the instruction on your link.
Where is  " allowed "External out-of-office messages and legacy out-of-office messages" on EMC ?

But if I apply to all messages , it works for internal and external . Does that mean my Exchange Server already allowed "External out-of-office messages and legacy out-of-office messages" ?


Accepted Solution

BMRT earned 0 total points
ID: 40517011
The temp solution for now is to Enable it for "all messages" and then add another condion to exclude addresses contain our domain. So it works for external users only.

Author Closing Comment

ID: 40845985
No other solutions

Featured Post

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Steps to fix “Unable to mount database. (hr=0x80004005, ec=1108)”.
Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
Familiarize people with the process of utilizing SQL Server views from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Access…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

619 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question