Using Transportrule patterns in Exchange 2013

In Exchange 2010 I was able to send a specific disclaimer (with or without Mobile Phone number) based on a AD Pattern match. Strangly Exchange 2013 does not allow the expression I'm using. I was wondering if anyone could help me out:
I'm using powershell:
Get-TransportRule "Signature - With mobile" | Set-Transportrule -SenderADAttributeMatchesPatterns ("mobilenumber:\S(\S|\s)*")
I've also tried:
\S(\S|\s)*
/\S(\S|\s)*/g
The error i'm getting:
The specified regular expression '\S(\s|\S)*'is invalid.
Parameter name: SenderAttributeMatches
But none seem to work in Exchange 2013. When I stop using groupings (), the expression is allowed though.
Any help would be greatly appriciated

Hi Peter,
Just check if below article can help you which will help in adding the correct attributes and predicates in the command which will solve your problem
http://technet.microsoft.com/en-us/library/bb124352(v=exchg.141).aspx#ADAttributes
http://technet.microsoft.com/en-us/library/dd638183.aspx#PropertyTypes
Steps to create new transport rule
http://technet.microsoft.com/en-us/library/bb123927(EXCHG.80).aspx
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish
website - exchangequery.wordpress.com

Similar Messages

Exchange 2013 Mail flow rule using RegEx

We're trying to implement a rule on certain mailboxes that it shouldn't accept an email without a subject.
I found documentation from Microsoft on exchange 2010 to Configure
a Transport Rule for Messages That Have a Blank Subject, but I tried using the ^$ RegEx
with Exchange 2013 and it doesn't seem to work.
I also looked at the Transport
Rule Predicates for Exchange 2013 and it clearly says thatSubjectMatchesPatterns
matches messages where text patterns in the Subject field match a specified regular expression.
My workaround was to reject all messages to those specific mailboxes except if subject pattern matches. but
if I want to add now conditions ie. to reject emails with a subject "Sent from my snipping tool" I can't do it.
I found Here that
Exchange 2013 now supports extended RegEx but I didn't find that the syntax for ^$should
be any different in extended RegEx.

If you use any special character in the RegEx you must use
\m Escape m, where m is one of the meta characters described above: ^, ., $, |, (), [], *, +, ?, \, or /.
as decribed in http://technet.microsoft.com/en-us/library/jj674702%28v=exchg.150%29.aspx

Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them.
With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.
For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.
In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.
I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.
I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.
So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.
In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.
Questions are, Is this the right way to migrate all the users to Exchange 2013?
Will it affect the operation of existing Exchange 2007 server?

Read the below blog on Client Connectivity in Exchange co-existence. There can't be better blog than this on this topic.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Clients connect to Exchange from Internal-Outlook, External-Outlook, Web & Active Sync.
For Internal the configuration that you have mentioned should work as clients would get Autodiscover information from Active Directory (SCP) and get connected to right server.
However, for external connectivity it makes sense to use External URL on Exchange 2013 servers (keep the Exchange exposed to Internet), configure legacy URL for exchange 2007 and use Exchange 2013 external URL for mailboxes that are Exchange 2007 and Exchange
2013 for standardization.
Refer article for configuring URLs -
http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
- Sarvesh Goel - Enterprise Messaging Administrator

Introduction of New OAB Architecture in Exchange 2013 and Some General Troubleshooting methods

Exchange 2013 is different from previous versions of Exchange server on architecture, some of the old features have been changed. In this FAQ, I will demonstrate the changes on OAB and list a common issue for your reference.
[Agenda]
1. Differences between Exchange 2007/2010 OAB and Exchange 2013 OAB
a. Generation
b. Distribution
c. Download
2. Common issue and troubleshooting
3. More information
[Difference between Exchange 2007/2010 and Exchange 2013 on OAB]
As we know, OAB in Exchange 2007/2010 has 3 points, OAB files generated from MBX server, distributed to CAS server and downloaded to Outlook client. However in Exchange 2013, these 3 points have a little different from previous servers. For example, the OAB
Distribution process doesn’t depend on Microsoft Exchange File Distribution service anymore. Now let me show you the changes of OAB in Exchange 2013.
[OAB Generation]
====================
Exchange 2007/2010:
1. OAB generation server is the specific MBX server which has –server property.
2. If MBX01 is down, OAB generation will be affected.
3. Previous Server using Microsoft Exchange System Attendant service for OAB generation.
4. OAB generation is a scheduled process. By default, OAB files generated at 5:00AM every day.
5. The OAB files which generated from MBX server are located in following path:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
Exchange 2013:
1. OAB generation server is the MBX server that hosts a special type of arbitration mailbox, called organization mailbox. Thus, the same OAB files could be generated from multiple
MBX servers.
2. If one of the MBX server down, other MBX server still have the ability to generate the specific OAB files.
3. Exchange 2013 server using OABGeneratorAssistant for OAB Generation.
4. OAB generation is a throttled process. It depend on the Server workload.
5. The OAB files which generated from MBX server are located in following path:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
[OAB Distribution]
====================
Exchange 2007/2010:
Previous Servers use Microsoft Exchange File Distribution service to distribute OAB files from MBX server to CAS server. The distributed oab files stored in CAS server.
Exchange 2013:
The OAB files doesn’t distributed to CAS server. The OAB files only stored in MBX server.
[OAB Download]
====================
Exchange 2007/2010:
If Autodiscover works fine, Outlook should use OAB URL to get the OAB files and download it.
If Autodiscvoer doesn’t work, authenticated users can also get the OAB from the CAS server local disk.
Exchange 2013:
Microsoft Exchange File Distribution service has been removed from Exchange 2013 and the OAB files stored in MBX server. CAS server will proxy all OAB download requests to the appropriate MBX server.
Outlook also use Autodiscover to get the OAB URL and download it.
[Common issue and Troubleshooting]
Issue: Outlook doesn’t download OAB files automatically. When I try to manually download OAB, get this error: Task xxx reported error (0x80190194): The operation failed.
Troubleshooting:
1. First, please run following command to check the information of OAB Generation Server.
Get-Mailbox -Arbitration | where {$_.PersistedCapabilities -like “*OAB*”} | ft Name, Servername, Database
Example result as below:
2. Please make sure the authentication settings and URLs are set properly.
3. Try to verify whether the OAB files generated from MBX server successfully. Path as below:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
4. If all of the settings above set correctly, please try to check Autodiscover. Run “Test E-mail Autoconfiguration” to check whether there is anything abnormal on OAB. If has, please search the error code on MS official documents.
5. If this issue is related to local cache, please try to delete the OAB caches from local PC and re-download OAB for testing. Path as below:
C:\Users\Administrator.CU1(different)\AppData\Local\Microsoft\Outlook\Offline Address Books
[More information]
http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx
http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi Techy,
According to your description, I am still not quite sure about your environment. Could you please provide more information about it, such as:
1. How many Exchange servers in your coexistence environment? One Exchange 2010 with all roles and one Exchange 2013 with all roles? Or several Exchange 2010 and multiple Exchange 2013?
2. Are there two sites in your environment? What’s the Exchange deployment in different sites?
3. Please confirm if both Exchange 2010 and Exchange 2013 are Internet-facing.
Additionally, if you are using different namespaces for different services for internal access and external accessing, we need to include all service namespaces in your certificate with IIS service. Personal suggestion, we can follow ED Crowley’s suggestion
to use split-brain DNS in your environment and only use the same namespace for Exchange service URLs.
The following article described the details about how to configure different namespace for Exchange services by using Load Balance in Exchange 2013:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/introducing-load-balancing-exchange-server-2013-part2.html
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 and 2010 co-existance

We will have 2013 and 2010 exist together for a while...we plan to move away from using Unified Access Gateway for HTTP redirection to our Exchange services and implement Kemp
load balancers...two at our HQ site and two at our DR stie...
We plan to have a one arm configuration...from what I gathered...each load balancer will have a network connection and only one network connection and be on the same network as
our new Exchange 2013 servers. Can someone take a look at my config and give some input whether or not this will work and some suggestion on Ex13 urls, cert SAN names, etc.
HQKemp 2400 A
HQKemp 2400 B
DCKemp 2400 A        DCKemp 2400 B
172.16.1.104
172.16.1.105
172.25.1.104
172.25.1.10
Virtual IP   172.16.1.106
                         Virtual IP
172.25.1.104
From the video I’ve watched for Kemp install…we’ll create the following internal DNS records for the Exchange services that will be configured on balancers.
OWA/ECP
    mail.corp.local.com
              172.16.1.107
EWS               ews.corp.local.com
172.16.1.108
OAB               oab.corp.local.com
172.16.1.109
ActiveSync      mobile.corp.local.co
172.16.1.110
OA                 oa.corp.local.com
172.16.1.111
Autodiscover   autodiscover.corp.local.com 172.16.1.112
Question:
We will configure the Exchange services with these ip addresses linked to each service on all four load balancers?
Or will DR site load balancers have different IPs configured for same Exchange services?
Exchange services are split between our two sites…meaning Outlook Anywhere is configured for our CAS servers at our DR site and ActiveSync comes to HQ CAS servers as an example…so
I want all Exchange services to come through the newly installed load balancers at HQ and if they don’t respond…the Exchange services get redirected to the load balancers at our DR site.
Can you give some insight on the config of load balancers as to how we can do that?
I have a question about the cert we will have.
Our Microsoft rep says we should get a new wildcard cert…currently we have a UCC cert with the following SANs attached.
Will this new cert have to be installed on load balancers?
If so…can you suggest some ideas as to what new SANs I need if any of the new cert with Exchange 2010 and 2013 co-existing for a while.
Below are the SANs on our current UCC cert.
Outside resolvable SANs
Webmail.corp.local.com
205.223.19.25           portal.corp.local.com     205.223.27.78
Portal2.corp.local.com
205.223.19.25
Autodiscover.corp.local.com
205.223.19.25
Internal SANs
Hqcas1.corp.local.com
Hqcas2.corp.local.com
Dccas1.corp.local.com
Dccas2.corp.local.com
Owamail.corp.local.com
(this CAS Array server name that HQ CAS servers create)
What do you suggest we use for the external urls on Exchange 2013 for these services?
Our firewall guy says we’ll use same names,
but I’m not sure if we try to use same name if we’ll get an error?
Active Directory may say name already in use?
We plan to have firewall to just redirect requests for external urls to load balancers…sound correct?
Meaning load balancer won’t have an external NIC defined…which makes it a one arm config…correct?

Hi Techy,
According to your description, I am still not quite sure about your environment. Could you please provide more information about it, such as:
1. How many Exchange servers in your coexistence environment? One Exchange 2010 with all roles and one Exchange 2013 with all roles? Or several Exchange 2010 and multiple Exchange 2013?
2. Are there two sites in your environment? What’s the Exchange deployment in different sites?
3. Please confirm if both Exchange 2010 and Exchange 2013 are Internet-facing.
Additionally, if you are using different namespaces for different services for internal access and external accessing, we need to include all service namespaces in your certificate with IIS service. Personal suggestion, we can follow ED Crowley’s suggestion
to use split-brain DNS in your environment and only use the same namespace for Exchange service URLs.
The following article described the details about how to configure different namespace for Exchange services by using Load Balance in Exchange 2013:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/introducing-load-balancing-exchange-server-2013-part2.html
Regards,
Winnie Liang
TechNet Community Support

Converting from InMotion Hosting to Exchange 2013 Migration

Hello everyone,
We are looking to convert our current mail service being hosted on InMotion using POP3 to our Exchange 2013 server. Is there a migration guide somewhere I could find or something to lead me in the right direction? We want to forward the mail from InMotion
to the Exchange mailboxes as well. I know this involves converting MX records and the such but I feel like something is missing in the grand scheme of things.

Hi,
The migration can include:
1. Account migration.
2. Database migration.
3. Some A and MX records need to be configured.
For more details, you can either consult Inmotion support or Microsoft support below:
Inmotion Support
https://www.inmotionhosting.com/support/launch-chat/?rdid=2324923566971164486&url=http%3A//www.inmotionhosting.com/support/email/general-information/getting-started-guide-email
Microsoft Advisory Support
https://support.microsoft.com/gp/advisoryservice
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 coexistence with 2010

Who all has had problems with 2013 proxing requests to 2010? I tried a migration and couldn't even get OWA to proxy or redirect. I was receiving errors like this:
Autodiscover would fail for 2010 users but fine for 2013 users:
HTTP Response Headers:
request-id: d1e90875-53e1-4be5-ad64-24a9a5eb0c19
X-CasErrorCode: ServerNotFound
Persistent-Auth: true
X-FEServer: CPC8000-CAS01
Content-Length: 0
Cache-Control: private
Date: Sun, 01 Jun 2014 01:22:50 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 153 ms
and
Created a new user on 2010 and login to OWA does this:
Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
I've tried it multiple ways and I've actually done this migration before. Either way this was the same AD site, and I checked/tried the following:
Checked AD Replication and it was fine
Exchange 2013 was at SP1
Exchange 2010 was at SP3 Rollup 6
Exchange 2010 was a single server with CAS/HUB/Mailbox
Exchange 2010 was not using a CAS Array
Exchange 2013 had two mailbox servers in a DAG and one CAS server
I've tried both setting all external URL's on 2010 to https://legacy.domain.com/* and also not setting External URL's. Neither fixed the issue
https://legacy.domain.com/autodiscover/autodiscover.xml worked fine (600 invalid request response) and https://owa.domain.com/autodiscover/autodiscover.xml worked fine too (2013) but Test Connectivity and Outlook didn't work
I checked for bad HTTP Redirections on new and old servers and made sure there were no HTTP redirections added
Would really love some input to see what I did wrong. Thank you!

Thanks for responding!
The internal URL's for 2010 I set to https://legacy.domain.com/*. So the OWA internal URL is https://legacy.domain.com/owa. The external URL was set to the same and I also tried not settings the external URL at all.
Just FYI.. legacy.domain.com pointed to the internal IP when using internal DNS servers and legacy.domain.com pointed to the external IP when external which all went to the 2010 server
The detailed error from ExRCA is listed above. It failed autodiscovered and wouldn't continue. The thing is autodiscover seemed to work fine going to 2010 and to 2013 but it failed when it tried to proxy to 2010. So if a mailbox was on 2013 then ExRCA was
fine. If I opened a url to https://legacy.domain.com/autodiscover/autodiscover.xml and logged in I got the XML 600 error like I should. This is what autodiscover said:
HTTP Response Headers:
request-id: d1e90875-53e1-4be5-ad64-24a9a5eb0c19
X-CasErrorCode: ServerNotFound
Persistent-Auth: true
X-FEServer: CPC8000-CAS01
Content-Length: 0
Cache-Control: private
Date: Sun, 01 Jun 2014 01:22:50 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 153 ms

Cisco IronPort with On Premise Exchange 2013

Hello All
The company I work for is in the process of starting an on premise Exchange 2007 to Exchange 2013 migration.
Most of the issues I don't think I'll have an issue with; however, where I am not finding much info is in regards to other companies using Cisco IronPort with Exchange 2013.
SO, I have two questions within this topic...
One, is anyone using Cisco IronPort with Exchange 2013 (on premise) out here?
Two, my manager is very controlling. I am the Exchange Admin; however, anything having to do with this IronPort thing with regards to Exchange HE has to do it. So, if anyone is familiar with this IronPort thing... How much work on the IronPort is going
to have to be done during this migration to keep things going?

It shouldn't be any different with Exchange 2013 than it is with Exchange 2007.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Outlook 2010 connecting to Exchange 2013 and 2007 ... delivery fails

Hello,
we are having a problem with a few Outlook 2010 Clients that have two Exchange accounts setup in one profile. One account is connecting to the company's Exchange 2013 Server, the second account is connecting to an external provider's Exchange 2007 infrastructure
using Outlook Anywhere.
The companies Exchange 2013 was recently migrated from Exchange 2010 and this is the point where the problem started.
Some users are no longer able to send using the external Exchange 2007 account. When they try they are receiving an NDR with the following error message:
#554 5.6.0 STOREDRV.Deliver; Corrupt message content## from the external provider's servers.
When I setup a profile containing only the external provider's mailbox everything works fine until I am adding the company's Exchange 2013 back in at which point the same error appears.
We have no problems using the company's Exchange 2013 servers.
Does anyone have an idea what causes this and how to resolve it? The external provider is uncooperative in troubleshooting so we are left with the problem.
Thank you
Sascha

Hi,
The problem should be related to the External Exchange 2007.
Please refer to this kb below:
http://support.microsoft.com/kb/2203381/en-us
This problem occurs when the email message is a multipart/mixed MIME message which contains a text/plain body and an application/applefile body. If the corresponding body is not a real application/applefile body, the Exchange Server 2007 server considers
that the email message is invalid. Therefore, it generates the NDR. However, Exchange Server 2010 can deliver this kind of email message successfully.
To resolve this problem, you should let the External Provider install the following update rollup:
2279665 Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3
Hope this helps.
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Certificate Authority for Exchange 2013

Dear,
I will install exchange 2013, whether to install the Certificate Authority role also?
If it is necessary, to install this CA, is simply combined with ADDS server, Exchange Server or a separate server?
Thanks

Hi,
As all above says, Exchange 2013 can use Self-signed Exchange certificate which is installed automatically after Exchange 2013 installation. But please note that this self-signed certificate would be not trusted for Exchange using.
If your Exchange 2013 is not internet-facing, we can use the self-signed certificate in your internal domain environment. If you want to publish your Exchange 2013 to the internet and send/receive external mails, we need to have a valid and trusted certificate
for Exchange using.
To get trusted certificate, we can deployed an
Enterprise root CA which self-signs its own CA certificate and uses Group Policy to publish that certificate to the Trusted Root Certification Authorities store of all servers and workstations in the domain. Or we can directly buy a third-party certificate
for using.
About where to install the CA, my personal suggestion is to install ADCS (Active Directory Certificate Services) on a standalone server. You can also install it with your DC. About how to install a
Root Certification Authority, please refer to:
http://technet.microsoft.com/en-us/library/cc731183.aspx
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 and DKIM

Exchange 2013 SP1 with 1 DAG and 2 members. We are thinking about using DKIM:
http://www.emailarchitect.net/webapp/download/eaexchdomainkeys.exe
First, is this the recommended DKIM app to use or is there a different/better one? Second, we host many domains on our exchange servers. Is it possible to use DKIM with many domains? Third, if we use DKIM do we need to install DKIM on both exchange servers?
Both servers have all roles installed.

Hello, as recommended
earlier on the use DKIM in EDGE Exchange 2013 or 3rd party GW (Li Zhen)
DKIM Exchange
Server 2007/2010/2013
DKIM
Wizard
dkim-exchange
MCITP, MCSE.
Regards, Oleg
That top link is the same link i originally asked about. We may be able to do a hyper-v VM for edge server. Can this be done with an existing exchange install/setup?

F5 Big IP 4000 Send /Return String for Exchange 2013

Hi,
I need to Implement F5 Big IP 4000 and need to set send / return string for Exchange 2013 server for OWA monitoring... Can anyone help me with Exact output String.
Amit

Hi,
In the Send String box enter in GET /owa/healthcheck.htm. In the
Receive String box, enter in 200 OK.
Here is a related article for your reference.
http://port25guy.com/2013/07/24/how-to-use-managed-availability-in-exchange-2013-with-your-load-balancer/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

Queue viewer Exchange 2013 - risk level?

Hi folks,
does anyone know what the 'risk level' attribute means when I use Get-Queue in Exchange 2013? I didn't find any documentation about that attribute.
Many thanks in advance!
Greetings,
Nils

Hi，
I found a relevant article for your reference:
RiskLevel enumeration
Assigns a risk level to the associated message based on characteristics of the message.
Member name
Description
Normal
The associated message is normal risk.
Bulk
The associated message is part of a bulk mailing.
High
The associated message is high risk.
Low
The associated message is low risk.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.

Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.
First my organize has Exchange on 2 site like
site A (internet facing) : 2CAS 2 MB all are Services pack1
site B (DR Site , no user active on this site) : 2CAS 2MB all are Services pack 1
so today I upgrade Exchange 2013 from SP1 to CU5 start on "site B" and I found this issue and the details is....
When I open EMS on any CU5 for query something (like get-mailboxdatabasecopystatus) the response return very slow and some query will not return at all (like get-owavirtualdirectory).
But If I using EMS on SP1. Everything is ok then I try to use EMS on SP1 connect to CU5 and try to query something. the result is
some query command cannot return for any result that are server on siteB (just some query command)
Problem
EMS on CU5 return very slow result.
EMS on SP1 still ok.
Does anyone face this problem before for CU5??? Please help me figure this out. Thank you
reply from Social.technet

Hi,
Have you used the above cmdlets to check your Exchange server health?
"all other command that I ran on EMS didn't logged on event viewer.", my environment is the same with you. I use Exchange 2013, only errors will be displayed in MSExchange Management. Actually, it is not related to slow EMS response.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Sending email using Exchange 2013 defined email addresses not the account email address.

Currently we are using exchange 2013. Let's say a user has a mailbox account defined that has a default email reply address of [email protected] Now I define additional email address for the same account. When the user tries to send an email he can only send from
the default email address. Is it possible to send from a defined email anndress and not the default account email address?
Best Regards
Best Regards

Not natively with Exchange.
You will need 3rd party software if you want to have only one mailbox and the ability to send as any of the proxy addresses associated with it
Example:
http://www.ivasoft.biz/choosefrom2007.shtml
Not sure if Exchange 2013 is supported with it yet
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Using Transportrule patterns in Exchange 2013

Similar Messages

Maybe you are looking for