Steven Theck

We have been receiving and excessive amount of spam (although ESET Mail Security has been filtering it), so I thought I'd try enabling greylisting. Doing so has drastically reduced the amount of spam that is coming in to our server. My issue is that it is also blocking local SMTP requests as well. We have a program that runs on WS 2012 R2 with Remote Desktop Services. This program accesses a SQL database from a separate WS 2012 R2 running SQL 2012. When a user attempts to send an email from our program, the request is sent from the SQL server to our Exchange server (WS 2012 R2 running Exchange 2013 SP1). I have a receive connector enabled on the Exchange server for this relay. It is setup for TLS with permissions for anonymous users (settings required for SMTP from our aforementioned program), it will only receive mail from the SQL server, and it is only bound to the IPv4 address of the Exchange server through port 25. The setup for the relay is correct and works great when greylisting is disabled. That being said, is there a way to configure ESET Mail Security to allow this relay while having greylisting enabled?

I found my solution to the problem, and hopefully it will help frannac and any others experiencing the issue. The errors occur with Exchange 2013 SP1 only, and are due to invalid XML code in the global assembly cache (GAC) policy configuration files. A permanent fix will be released with CU5, but Microsoft has released a fix for now. hxxp://support.microsoft.com/kb/2938053

I am experiencing the same issue as frannac. I am using ESET Mail Security for Microsoft Exchange Server version 4.5.10022.0 on MS Exchange version 15.0.847.32 (2013 SP 1). I tried what Marcos recommended and it did not fix the issue. After digging deeper into the problem, I found that the "ESET Filtering AV Agent" Transport Agent is not being created in Exchange. I tried manually creating the Transport Agent from the PowerShell and received the following error: The TransportAgentFactory type "XmonAgent.XmonAgentFactory" doesn't exist. The TransportAgentFactory type must be the Microsoft .NET class type of the transport agent factory. Parameter name: TransportAgentFactory + CategoryInfo : InvalidArgument: ( [Install-TransportAgent], ArgumentException + FullyQualifiedErrorId : [Server=ExchangeServer,RequestId=5e13cc9d-1a7a-41b5-8822-bd8dcf4cf101,TimeStamp=6/30/2014 1 1:11:42 AM] [FailureCategory=Cmdlet-ArgumentException] 890B4548,Microsoft.Exchange.Management.AgentTasks.InstallTr ansportAgent + PSComputerName : exchangeserver.corp.mydomain.com