Log error entries

<< Click to Display Table of Contents >>

Navigation:  FAQ >

Log error entries

Errors on forwarding

Q: For some emails, I receive a message from the exchange server saying "maximum message size exceeded". What can I do?

A: This notification is typical for Exchange Server 2007/2010 because they both have a standard option limiting email sizes to 10MB. These can be modified by changing the limitations of the Receive Connector. This occurs over the Powershell: Help article at Microsoft  (Set-ReceiveConnector  --->  MaxMessageSize)

Q:I get an error message "unable to relay..." in the log of SmartPOP2Exchange when it tries to send mail to my SMTP server. What does this mean?
A:"unable to relay..." means your SMTP server does not allow SmartPOP2Exchange to send mail to it (as a SMTP relay server). Please first check the entered mail addresses in the "SMTP settings" of SmartPOP2Exchange. Make sure that these addresses also exist on your SMTP server. If you like your SMTP Server to send/forward that mail to an external server then set your SMTP server to allow all SMTP relays or at least relaying from SmartPOP2Exchange. (For MS Exchange Server you will find this setting in the properties of the "virtual SMTP server")
Q:When SmartPOP2Exchange tries to forward mail messages to our mail server, the error message "Unable to relay for user@domain.com" shows up. Why?
A:Please add the shown email address to the appropriate Windows user in the Active Directory's "Email" tab.
Q:In the eventlog I see the error "Relaying not allowed for yourdomain.com" and I don't receive any mail in my inbox. What is wrong?
A: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.
Q:What can I do if the Exchange Server responds: "Client does not have permissions to send as this sender"?
A: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.
Q:What can I do if the Exchange Server responds: "451 4.7.0 Temporary server error. Please try again later. PRX2"?
A: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.
Q:What can I do if the Exchange Server responds: "451 4.7.0 Temporary server error. Please try again later. PRX5"?
A: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): server server.domain.local
Then restart "Microsoft Frontend Transport" and "Microsoft Exchange Transport" services.


Socket Errors (These errors may occur on receiving or forwarding messages. In most cases they are caused outside of SmartPOP2Exchange)

"..too many connections"

See "Socket Error # 10068 Too many users".

"Connection Closed Gracefully."

See "Socket Error # 10053 Software caused connection abort".

"Socket Error # 10053  Software caused connection abort"

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.

"Socket Error # 10054  Connection reset by peer"

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.

"Socket Error # 10055 No buffer space available"

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.

"Socket Error # 10060  Connection timed out"

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?

"Socket Error # 10061  Connection refused"

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.

"Socket Error # 10068 Too many users"

The server quota ran out. The server refused a connection because there are currently too many users connected to the server. Try again later.

"Socket Error # 11001 Host not found"

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.

"Socket Error # 11004 Valid name, no data record of requested type"

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.
This error is similar to the "Socket Error # 11001 Host not found".