Hi Guys if I want to set a disclaimer based on a users UPN, is it simply the case of creating transport rules then modifying the "when the from address contains" field and inputing the UPN's (@upn.com) i.e user_a@upn.com -- gets a disclaimer from upn.com user_b@upn1.com -- gets a disclaimer from upn1.com I did a quick test and it did not work any gotchers James remember this is Exch 2007

Hi, it should work. Have you installed the actual patches/Service Packs? regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com

thanks peddy I will check, tbh I just did a quick test -- it's an enertprise environment, so maybe the setting needed to propogate to the other Hub servers was an issue with transport rule fixed in an SP then?

Hi, OK, this might explain the delay. Is it possible that you give us some more details of your infrastructure? Active Directory Site Configuration (replication settings) and Exchane configuration accordingly the the AD Site configuration. regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com

if I want to set a disclaimer based on a users UPN, is it simply the case of creating transport rules then modifying the "when the from address contains" field and inputing the UPN's (@upn.com) Hi James, Please remove the @ and test it again. Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Frank Wang TechNet Community Support

Hi James, after reading this threat again I noticed that you want to create a transport rule based on the UPN and you give us an example userr_a@upn.com. Please rember that this is a UPN and not an email address so you are not able to compare this value with the from field value in an email. It is possible that the two information are identical but in enterprise environments normally it is not identical. So you have to hut the email address in the transport rule "When the from address contains" and not the UPN of an useraccount. regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com

yep, thanks peddy the logic was, users accounts where being udated with a UPN, which in turn was driving an EAP -- then discalimer appended as required to the @upn.com and as noted works without the @ it was for a rollout of Office365 thanks to all