Server Fault works best with JavaScript enabled. A moderator for a moderated recipient approved the message, so the message was delivered to the moderated recipient. Message generated by inbox rules: For more information about these Transport Rule agent values, see the “Data logging” section in the DLP Policy Detection Management topic, transport-traffic-type In on-premises Exchange, this field is blank or has the value Email. For more information, see Inbox rules. The values in the source field in the message tracking log indicate the transport component that’s responsible for the message tracking event. Users can use the Delivery reports tab in Outlook on the web to search the message tracking logs for information about messages sent to or sent by their own mailbox.

Uploader: Kagazahn
Date Added: 7 May 2017
File Size: 28.38 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 34758
Price: Free* [*Free Regsitration Required]

A message submitted by the Pickup directory or the Replay directory that can’t be delivered or returned. Version number of the Exchange server that created the message tracking log file.

Thx for the reply. A message was put in the poison message queue or removed from the poison message queue. You should also look at the Source and Recipients fields when inspecting messages with this event.

How to Tell Which Transport Rule Was Applied to an Email Message

No message content is stored in the message tracking log. This is related to the LOAD event type. By default, Exchange uses circular logging to limit the message tracking log based on file size and file age to help control the hard disk space that’s used by the log files.


When it comes to searching the message tracking logs, you eent different options.

I think it might be important in certain circumstances to know faill. So, that’s one way to find a rule by using message tracking logs to determine which rule ID was applied to the message. Another way we could have approached this is to search the transport rules for those that match a criteria. Delivery reports for users: Message tracking logs contain vast amounts of data as messages move through a Mailbox server or Edge Transport server.

An alternate recipient for the message was already a recipient. Other files that do not follow the name prefix convention are not counted in the total folder size calculation.

Our new feedback system is built on GitHub Issues. A shadow message failed to be created. A shadow message was received by the server in the local database availability group DAG or Active Directory site. Date-time of the message submission.

The event sequence number. Yes No Comment Submit. Some message events appear in only one type of message tracking log file, and some message events appear in all types of message tracking log files. Very Important MessageThis is an email from Alan.


Tracking messages in Exchange log files – easy and quick!

Resources for IT Professionals. Contains the report link, which is the Message-Id skurce of the associated delivery status notification also known as a DSN, bounce message, non-delivery report, or NDR if a DSN is generated subsequent to this event.

Each message tracking log file has a header that contains the following information:.

In my case, the server tried to connect via ipv6 to the domain server in a network that had only ipv4 routes, as result failing the connection as invalid when the DNS returned eveht unreachable ipv6 IP. The event source was the routing resolution component of the categorizer in the Transport service. How could you then check the rule for an email that is in fact not there?

Did this article provide the information you were looking for? A message stoerdriver sent by SMTP between transport services. Home Questions Tags Users Unanswered. Product feedback Sign in to give documentation feedback. Ian Chilvers 1 3 The IPv4 or IPv6 address of the messaging server or messaging client that submitted the message.