We don’t use marketing cookies. Functional cookies ensure a smooth performance of our website. If you continue to use our services, you agree to the use of cookies. Data protection at JAM OK

Knowledge Base

Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.

This "error message" is caused by greylisting solutions.
For example, if you are using ESET for Server, even if you disable anti-spam capabilities in its configuration, it will not be greylisted.
To disable greylisting, the Exchange Server Transport Agent must be disabled by ESET: (in the Exchange Server PowerShell)
Disable-TransportAgent -Indentity "ESET FilterAgent

This is a limitation of the receive connector of the MS Exchange Server. It only allows a certain number of simultaneous connections from a single IP. The default value is 20.

You can query the value for your receive connectors on the Exchange Powershell:

Get-ReceiveConnector -Identity <connectorname> | fl MaxInboundConnectionPerSource

To change the value you can use the following command:

Set-receiveconnector - identity "CONNECTOR_NAME" -MaxInboundconnectionPersource 100

Please restart the Microsoft Exchnage Transport service after changing the values.

Please also see MSDN: https://docs.microsoft.com/en-us/Exchange/mail-flow/message-rate-limits?redirectedfrom=MSDN&view=exchserver-2019#message-throttling-on-receive-connectors

It seems you are missing the correct OLE DB Provider. 

To correct this you have to go to this website from Microsoft and download the Access Database Engine 2010 in 32-bit.
Make sure you download and install the 32-bit version since the database connection is not supported with the 64-bit version.

The requested name is valid, but does not have an Internet IP address at the name server. This is not a temporary error. This means another type of request to the name server will result in an answer.

No such host is known. The name you used is not an official host name or alias. This is not a software error, another type of name server request may be successful.
Check that you have a name server(s) and/or host table configured. If you are using a name server(s), check whether the server host(s) are up (e.g. try to ping the server(s)). You could also try to resolve another host name you know should work, to check if the name resolution server application is running.

Current category: SmartPOP2Exchange