<div>
So I would need to build a rule that would look at the content of the message rather than to/from/subject fields for example?
</div>


<div>
Confirmed to work when the rule uses subject/body as the &quot;trigger&quot; for it to do something. Thanks!
</div>


<div>
<div class="content wysiwyg-content">
Perhaps silly question:<br />
<br />
Can messages that are using Anonymous SMTP Relay in Exchange 2013 be controlled via Transport rules?<br />
<br />
I can see the messages hitting the exchange server in the SMTP &quot;send&quot; logs (C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\<wbr />Logs\Front<wbr />End\Protoc<wbr />olLog\Smtp<wbr />Send) but I am not able to do anything to them with the Rules in Exchange. I see two options (aside from possibly the old &quot;well, something is broken&quot;):<br />
<br />

<div class="bullet">
I am doing something wrong when setting up the rules, or
</div>
<div class="bullet">
Those messages cannot be affected by the rules
</div>
<br />
Well - which one of the two (3) is it?<br />
<br />
Thank you guys :)
</div>
</div>


Perhaps silly question:

Can messages that are using Anonymous SMTP Relay in Exchange 2013 be controlled via Transport rules?

I can see the messages hitting the exchange server in the SMTP "send" logs (C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpSend) but I am not able to do anything to them with the Rules in Exchange. I see two options (aside from possibly the old "well, something is broken"):

I am doing something wrong when setting up the rules, or
Those messages cannot be affected by the rules

Well - which one of the two (3) is it?

Thank you guys :)

SMTP relay on Exchange 2013 and Transport Rules

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.

Email Servers

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.