After much time using xeams, i become a huge fan. Been working with Xeams integrated with my Exchange 2013 without any problem for almost 2 years, allways running without a problem. Until the day i upgraded Exchange to 2016.

After upgrading Exchange to 2016, Xeams started to fail and forced me to put it aside.

The problem that i face is the following ( doesn't matter what flavor of Xeams i use ( tried Windows, VM and Linux)) :

Installation runs and finishes without a problem ( running Xeams in SMTP Proxy mode, diagnostics run and nothing failed)

Xeams works without a problem until the first mail is received, then all hell brakes through :

First mail gets redirected to Exchange ( no problem here), but after that no mail is received ( although many test mails are sent through outside accounts). So i go to diagnostics and connection to my Exchange is failed. Checked internet connection : Is active and online ; checked Firewall : ports 25, 80 and 53 are open both ways ( in and out) on both Xeams machine and Exchange 2016 Machine. ( I know full open ports are not safe but just making sure everything worked fine. From this point forward no mail is received and resent by Xeams, unless i restart Xeams again ( BTW , i did tried both on Windows and on Linux machines with exactly the same result).

After restart Xeams starts working fine and diagnostics passes all tests, UNTIL THE FIRST MAIL IS RECEIVED, then all blocks up again ...

I had the same kind of setup with Exchange 2013 and everything worked ok ... so my guess is some kind of problem between Xeams and Exchange 2016 ...

Does anyone got the same problem ?

Just to update some information :

I get on Xeams : ERROR on SERVER COMUNICATION : Can't connect to email server

After getting this error i did a ping on my mail server and got response, i did check for open ports ( port TCP 25 on my mail server) and they were open, checked DNS and Firewall and was also open. I even went to my Receive Connector ( Frontend Transport, on port 25) and added as mailserver the ip from Xeams machine ...

Did all those checks and alterations and still get ERROR : Can't connect to email server. I only use Spam Firewall Mode.

The error cannot be, as i could think off, from my email server, and it could only be form a problem on XEAMS side, because from time to time the connection get back up and mail flow from a short period ( around 1 to 5 mails received) and then connection drop again.

I really love Xeams and would like to continue on using. 

Any help or thought would be apreciated

Update : If i change NAT on my router, from XEAMS IP back to EXCH IP, XEAMS diagnostics don't get any error. Will try to change ports to see if anything changes ...

No luck ... Did change my router's NAT to this setting :

Outside TCP 25 -> Xeams TCP 10025

Still get SERVER COMUNICATIONS ERROR

No luck ... Did change my router's NAT to this setting :

Outside TCP 25 -> Xeams TCP 10025

Still get SERVER COMUNICATIONS ERROR

Hi Nuno,

I had something similar in the past with Exchange 2013.

Could you check your "Send connector" and add xeams as a smart host?

That fixed it for me, hope it helps.

PS: Do not forget to create a DNS record in your local domain so your Xeams IP is bound to the smarthost.

Hi, Laurens. Thanks for your help, but unfortunately my problem isn't on sent mails , but on receive ( SMTP, port 25). I always get , right after xeams receives 1 or 2 mails, a connection error ( viewed in diagnostic) , saying that Xeams can't connect to SMTP. I had in fact added my xeams dns and even ip to exchange connectors, because i had thought of that, but hadn't any luck ...

But still trying and having hope that someone gets the same problem and eventually find a way to solve it ... I had report this in support, but since my budget doesn't allow me to buy the paid support, i have to stick to my 2nd option, manually delete spam ... 

Nuno,

As far as I know, you do not need to change anything in the receive connectors for Exchange. The default connector that used to work prior to Xeams should now work with Xeams. Do do you see in SMTPProxyConversation.log? Post a small snippet from this log here. 

You could also install a small SMTP client, such as Thunderbird, on the same machine where Xeams is running. Configure its SMTP server to Exchange and see if you can send messages to Exchange without Xeams from that machine.

BTW, my experience with Xeams support is very good. Try sending them an email.

Pasha, nothing strange shows on logs, but i think i've found the problem although i don't know how to solve it.

In my network i have the following servers :

My domain server ( Windows 2012) with DNS Server and where I've installed Xeams ( ip : 192.168.1.5)

My database server ( Windows 2012) with SQL Server and FTP Server ( nothing strange and not the culprit) ( ip: 192.168.1.4)

My Exchange server ( Windows 2012) with Exchange 2016 ( working great, with or without Xeams) (ip: 192.168.1.6)

And finally the culprit : A Linux machine with Sentora Web Server ( ip: 192.168.1.2)

If i disconnect Sentora Server, Xeams works great. If i connect Sentora, Xeams breaks. I still haven't figure it out on what level is the problem. My guess is something to do with DNS, but haven't find out where. 

Does anyone had a setup more or less like this ? Any clue on how to solve or to workaround this ?

Finally i found a workaround, not the perfect solution but is working!

The culprit was postfix server on my Sentora Web Server. Disabled it and worked and Xeams started working fine ...

Since i don't have the need to use postfix on my Sentora Web Server that is not really a problem to me ... but to someone with the same problem a solution is still needed.

To me is working now, so i will not bother you guys again ( hopefully ;) )

A big thank you to all that tried to help me !!!