I have found the below two possibilities not sure if either is a possible solution or completely irrelevant. Know nothing about servers and email etc but my comp sci lecturer (only did java) always answered every question with "google it"...
1. Mail server configuration error. Too many recursive forwards.
When an email client tells hMailServer who the email message is for, hMailServer tries to determine the "end recipient". The email address the client has given hMailServer may not be the end recipient. For example, if you have set up an alias, firstname.lastname@example.org
which points at email@example.com
, and the email client tells hMailServer that the message is for firstname.lastname@example.org
, the end recipient is actually email@example.com
It is possible to configure hMailServer in an incorrect way in this area. For example, say you have an alias named firstname.lastname@example.org
pointing at email@example.com
, and the alias firstname.lastname@example.org
is pointing at email@example.com
. When hMailServer is trying to determine the end recipient for an email to firstname.lastname@example.org
, it will give up since there is none and report the above error message. The error will always be reported if hMailServer can not determine the end recipient.
The following causes are the most common ones:
• A catch-all address has been specified for the recipient domain, but no account exists which matches the specified catch-all address.
• The message is being sent to an alias which does not point at a valid account
2. The mail server software tried to deliver e-mail to the local machine
This error message typically indicates a server configuration error. hMailServer does a number of checks before message delivery to prevent infinite message looping. When an email is sent and the recipient can not be found in the local installation, hMailServer will normally try to connect to the recipients email server to deliver the email message.
Before hMailServer connects to the recipients email server, hMailServer checks that the IP it is going to connect to is not a local IP address. If the IP is a local IP address, this would mean that hMailServer would connect to itself, which would likely cause a message loop. In this case, hMailServer rejects the message delivery and returns an error message to the sender instead.
The following causes are common for this problem:
• A host name or IP address which points at the local computer has been entered as SMTP relayer. Go to the Delivery of e-mail section in the SMTP settings. Check the SMTP Relayer setting. If you have entered localhost, 127.0.0.1, your-own-domain-name.com, or something similar in this textbox, this is likely the cause of the problem. If this is the case, read more about this setting in the SMTP reference guide, and then correct it.
• One of the MX records for the domain points at your server, but the domain has not been added to your installation.