I have a couple of Xeams servers configured identically.  Each server is configured as a Smart Host for our actual e-mail server.  As of last night, messages are building up in the queue for each server and when I click on the icon to resend a message, I get the following:

Xeams Admin Console - Version 5.3, build 5858

Thanks!

Correction: Configured as SMTP Proxy.

I'm experiencing the same problem.

Last not a auto update took place. There are 2 strange things in my log about the update:

016-10-05 00:06:22,878 WARN  users.f - Config file config/UserConfig.xml not found. Cannot continue reading.
2016-10-05 00:06:22,878 INFO  users.f - UserConfig.xml will be extracted from /share/MD0_DATA/.qpkg/Xeams/config/archives/CONFIG_20161003.zip
2016-10-05 00:06:23,488 WARN  users.f - Config file config/UserConfig.xml not found. Cannot continue reading.

And after the update no mail is received on the internal mail server. The log is stating it can't connect:

2016-10-05 00:06:44,494 WARN  smtp.b - Unable to start TLS connection to 192.168.2.2, recipient: user@dom.com, sender: user@dom.com - Error: Remote host closed connection during handshake

I do not have TLS/SSL enabled (never had) and can't see anything in the config regarding something with SSL enabled.

The error about the UserConfig.xml seems to 'normal' for my server, so ignore that part.

Since the log also stated it did a update to build 5858 last night, and right after that the problems occurred, I did a rollback of the previous build (http://www.xeams.com/xeams-wont-start-after-update.htm) bringing me back to build 5849

Unfortunately, this didn't resolved the error. Somehow Xeams thinks it should talk TLS to the inside SMTP server, even these settings are disabled on Xeams nor did I ever used it (the inside server is not configured for TLS). I do believe it has something to do with the build update (5858) from last night, because right after that it stopped working (it eve wasn't able to send the update notification mail).

Richard,

Your problem is not related to the same issue that Robert is facing. I have a feeling that UserConfig.xml file is corrupted on your end. Xeams makes a backup of the entire config folder for 7 days. Try restoring UserConfig.xml file from /share/MD0_DATA/.qpkg/Xeams/config/archive/*.zip . You will have to get the last good backup.

Once the file is restored, you will have to restart Xeams.

If you run into problems, contact our support via email.

Imran

Hi Imran,

Thanks for your reply. Unfortunately none of the 7 ZIP's seems to have a UserConfig.xml at all. According to the logfile, the UserConfig.xml started missing on 23-09-2016 (but the TLS issue started last night right after the update). Is there some default UserConfig.xml online I can copy to start with?

(is it possible to split my messages into a new topic?)

Robert,

We have discovered a problem with Xeams that occurs when you use Smart Host in Xeams along with SMTP Proxy server in "Asynchronous" mode. We will fix this in the next update. In the meantime, switch the SMTP Proxy server back to "Synchronous" mode by Unchecking "Asynchronous Mode" in SMTP Proxy Server setting. That will fix the problem.

Apparently, this bug has been there for a long time but it did not appear because you were using SMTP Proxy Server in Synchronous mode. Asynchronous mode is better than Synchronous and the last update switched the default value for this parameter, which made the problem appear.

Let us know if anyone wants a patch before it's released to general public.

Thanks for the quick response.  I've turned off asynchronous mode - in the Server Proxy configuration - and messages in the queue when "forced" to send out still give the following error:

Xeams Admin Console - Version 5.3, build 5858

Robert,

You will have to modify the files slightly that are sitting in the OutboundMailQueue. Here are the steps:

• Open $INSTALL_DIR\OutboundMailQueue folder
• Open any file sitting there in Notepad
• Search for X-SMCustomAuth .
• The goal is to remove this header from the email that are sitting in your OutboundQueue. The quickest way is to use a utility that can do search/replace inside files and replace X-SMCustomAuth with some garbage value. For example X-SMCustomXXXAuth

The actual problem is occurring when Xeams is trying to use the Smart Host even for incoming messages.

Build 5859 has been released that takes care of this problem.