EML files written to the root of the system drive on Exchange 2013 Client Access (CAS) Servers

  • Article ID: 120820
  • Rating:
  • 1 customers rated this article 5.0 out of 6
  • Updated: 06 Nov 2014


When PureMessage is installed on an Exchange 2013 Client Access (CAS) Server, EML files are written to the root of the system drive, by default this is C:\.

A typical file has the below properties:

File name: {DB35E454-E864-40fa-A27F-81AD8EE319F4}.eml

File contents:

X-Sender: <>
X-Receiver: PureMessage.Trigger@95B5EF1C.A6B4.483e.B662.9BF25F4DB9E7
To: PureMessage
From: PureMessage
Subject: Trigger
PureMessage trigger message sent by MailSending.dll

First seen in
PureMessage for Microsoft Exchange 4.0


Client Access Servers do not have the Exchange Replay directory which is required by PureMessage.

What To Do

Uninstall PureMessage from your CAS servers

PureMessage is not supported on Exchange 2013 servers hosting only the Client Access (CAS) role and must be uninstalled.

Note: Uninstalling PureMessage from your CAS servers may cause a temporary loss in SMTP scanning on your Exchange 2013 servers hosting the Mailbox role as described in the next steps, so this uninstall should be scheduled for a maintenance period if possible.

Check the PureMessage Transport Agents on your Mailbox servers

Uninstalling PureMessage from your CAS servers may result in this uninstall remotely removing the PureMessage Transport Agents from your Mailbox servers, so you need to ensure that the agents are still present.

  1. Run the below Exchange Management Shell command on all Mailbox servers which have PureMessage installed:


  2. Confirm whether the below agents are listed in the output:


  3. If the agents are not present then you need to follow the steps in the 'Install the PureMessage Transport Agents on affected Mailbox servers' section, if the agents are present then no further action is required.

Install the PureMessage Transport Agents on affected Mailbox servers

  1. Run the below Exchange Management Shell commands on an affected Mailbox server, the first commands install the agents:

    Install-TransportAgent -Name "PmE15Protocol" -AssemblyPath "C:\Program Files\Sophos\PureMessage\Bin\PmE15Transport.dll" -TransportAgentFactory "PmE15Protocol.PMProtocolAgentFactory"

    Install-TransportAgent -Name "PmE15Transport" -AssemblyPath "C:\Program Files\Sophos\PureMessage\Bin\PmE15Transport.dll" -TransportAgentFactory "PmE15Transport.PMTransportAgentFactory"

    the next commands enable the agents:

    Enable-TransportAgent -Identity "PmE15Protocol"

    Enable-TransportAgent -Identity "PmE15Transport"

    the last command sets the priority for PmE15Transport to 1:

    Set-TransportAgent -Identity "PmE15Transport" -Priority "1"

  2. Restart the Microsoft Exchange Transport service to complete the installation
  3. Repeat steps 1 and 2 on every affected Mailbox server where the Transport Agents are not present

Note: If you have installed PureMessage to a non-default location then you need to change the path in the above -AssemblyPath parameters accordingly.

Related Articles

Installation fails on Exchange 2013 Edge Server with 'COM error-code 0x80004005'

If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent