FAQs & Knowledge Base

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

Categories: SmartPOP2Exchange | Show all categories

No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host.

So either you tried to connect the wrong host, or the service (SMTP, POP3, IMAP) you're trying to contact isn't available. Check the destination address you are using. If you used a host name, did it resolve to the correct address? It's also possible that the remote services use a different port number.

A connect or send request failed because the connected server did not respond properly after a period of time. Check, if the destination address is a valid IP address. If you used a host name, did it resolve to the correct address?

An operation on a socket or pipe was not performed because the system lacked sufficient buffer space or because a queue was full.
This error indicates a shortage of resources on your system. It can occur if you're trying to run too many applications (of any kind) simultaneously on your machine. If it persists, exit Windows or reboot your machine to remedy the problem.

A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or a reboot.

A connection abort was caused by the server or some software in between (e.g. firewall, proxy). Turn off any proxy (check if your antivirus software installed a proxy) and firewall for testing.

This error results of invalid DNS settings. To solve it add the local server's IP to our hosts file (C:\Windows\System32\drivers\etc\hosts):
 192.168.1.5 server
 192.168.1.5 server.domain.local
Then restart "Microsoft Frontend Transport" and "Microsoft Exchange Transport" services.

This error may occur if you only have 1 domain controller and put a router as secondary DNS server on all configurations.
Simply remove the secondary DNS which does not point to the internal DNS/Domain Controller.
Forwarding typically would be handled by the DNS servers in your environment, so a secondary public DNS would not be configured in a typical production environment.

If this does not correct the error, try to create a reverse lookup zone on the DNS server.

Please ensure that the Exchange SMTP receive connector allows anonymous sending of emails, this is important for incoming emails. And please turn off SMTP authentication in the SmartPop2Exchange SMTP configuration if the problem persists and it is turned on.

Your Exchange/SMTP server is not configured to receive mail for yourdomain.com. From your Windows Start Menu, select Start | Programs | Microsoft Exchange | System Manager. There select: Recipients | Recipient Policies | Properties. Click on the "email Addresses" tab, under Generation rules, select SMTP, and then click Edit and change the value to "@yourdomain.com". Please also make sure that the email addresses of all users are specified in their Active Directory entries on the "email Addresses" tab.

All entries (Page 4 / 12)