IME Notifications are not accepted by some recipient mail server

Summary:

IME Notifications are not accepted by some recipient mail server.

IME Sender's Package Tracking displays the delivery status as "Sent", but the recipients do not receive the notification.

Detailed Information:

When IME sends email notifications, the notification is getting bounced back from or getting lost at recipient mail server. Common reported mail servers are yahoo.com, aol.com, comcast.com and some .edu domains. Mail is getting delivered to most of the other domains. The problem happens because increasingly more and more mail servers are performing reverse A or MX record lookup on sender's domain when a message is received. So these mail servers reject messages coming from mail servers that do not have resolvable reverse lookup. By default IME message sender is ime_mailer_XXXXXXXX@ime_server_name, where the ime_server_name is backend IME Server name. For most production environments, this host is not resolvable.

Resolution:

* First step is to make sure that email notifications are getting delivered to at least some external domains.
* Proceed only if you are able to confirm Step 1. If you are not able to send messages to ANY external domain, it could be a different problem and this resolution will not fix your problem. Please contact Tumbleweed TAC at support@tumbleweed.com for detailed investigation.

Windows:

* Shutdown IME Server.
* If IME is distributed, identify the machine where SMTP components of IME are installed. To find out, open the registry editor (regedit or regedit32) on backend IME system.
* Go to HKEY_LOCAL_MACHINE/Software/Tumbleweed/Server/Network section.
* Find value of "SMTP Gateway" key. This is where IME's SMTP components are installed. It is usually same as IME Backend server.
* Go to registry editor of that machine (if not already open from previous step).
* Go to HKEY_LOCAL_MACHINE/Software/Tumbleweed/Server/Network section.
* Change the value of "SMTP Host" key to a URL name (or alias) that has fully resolvable reverse lookup. E.g., securemail.yourcompany.com, ime.tumbleweed.com, etc. For maintenance purposes, make it same as IME Web URL.
* IMPORTANT: Some recipient mail servers are performing reverse MX record check as well. To cover all the mail servers, please add an MX record for this URL as well.

Solaris:

* Shutdown IME Server.
* If IME is distributed, identify the machine where SMTP components of IME are installed.
* To find out, go to backend IME Server (using a telnet/ssh prompt). You must be logged in as 'root'.
* Open /config/server.ini file on backend IME system.
* Search for "SMTP Gateway" key. The value of this key where IME's SMTP components are installed. It is usually same as IME Backend Server.
* Open /config/server.ini file of that machine (if not already open from previous step).
* Search for key "SMTP Host".
* Change the value of "SMTP Host" key to a URL name (or alias) that has fully resolvable reverse lookup. E.g. securemail.yourcompany.com, ime.tumbleweed.com, etc. For maintenance purposes, make it same as IME Web URL.
* IMPORTANT: Some recipient mail servers are performing reverse MX record check as well. To cover all the mail servers, please add an MX record for this URL as well.