Hi,

I have been running XEAMS as SPAM Firewall in front of my Exchange 2010 server in my home lab for a while now. But a couple a days ago i noticed that e-mails are not coming thru so i started to troubleshoot the issue and i cant seem to the issue or fix it.

When i run a diagnostic check - Inbound the result is: Server Communication - Failed.

Like the description says i made sure that the:

- IP/Host is correct; checked even did a nslookup on the machines where xeams is installed on returning the correct IP and Hostname

- Ping the server; checked did this on the machine where xeams is installed on

- is listening on the correct port; Recieve connector on exchange is 25 and in XEAMS configured on 25

What i did test too:

- Enable SMTP Proxy; On

- Asynchronous Processing; On

- Exchange Receive connector -> Permission Groups -> Anonymous users; this is checked

- Windows Firewall; allows TCP-in on port 25

- Machine where XEAMS is installed on; Telnet {IP} 25 -> EHLO; Did get a response from the exchange server

- Exchange Services; all running; even did a restart of all service and a reboot

- XEAMS Host; Reboot server

Specs:

- Xeams Community Edition Version 6.1, build 5960; Ubuntu 17.04

- Exchange Server 2010 Version 14.03.0352.000; Windows server 2008 R2

AG,

The SMTP Proxy Server requires your Exchange to be up and running. If Exchange goes down, so will Xeams. I have a feeling something is wrong with your Exchange and it is not accepting any emails. 

Try downloading Email Sender from http://xeams.com/email-sender.htm and try sending an email directly to your Exchange. You can do that by putting the IP address of your Exchange server in the SMTP Server field. Let me know what error you get.

Thank you for your fast response. I executed the Synametrics Email Sender FX

- TO; aXXg@aXXiXg.com (valid mailbox on the exchange server)

- Subject; Test Synametrics Email Sender

- Email content; Test

- SMTP Server; 192.168.XXX.XXX (Exchange server IP)

- Sender's Name; AG

- Sender's Email; aXXg@aXXiXg.com

Got the following result in the SMTP Log (i did receive a e-mail in the corresponding inbox) :

22-11-17 21:54 - [ 2] ************ New connection to: 192.168.XXX.XXX
22-11-17 21:54 - [ 2] C --> 220 XXX.aXXiXg.com Microsoft ESMTP MAIL Service ready at Wed, 22 Nov 2017 21:54:07 +0100
22-11-17 21:54 - [ 2] S <-- EHLO PXXDXOR.aXXiXg.local
22-11-17 21:54 - [ 2] C --> 250-XXX.aXXiXg.com Hello [192.168.XXX.23]
22-11-17 21:54 - [ 2] C --> 250-SIZE
22-11-17 21:54 - [ 2] C --> 250-PIPELINING
22-11-17 21:54 - [ 2] C --> 250-DSN
22-11-17 21:54 - [ 2] C --> 250-ENHANCEDSTATUSCODES
22-11-17 21:54 - [ 2] C --> 250-STARTTLS
22-11-17 21:54 - [ 2] C --> 250-X-ANONYMOUSTLS
22-11-17 21:54 - [ 2] C --> 250-AUTH NTLM
22-11-17 21:54 - [ 2] C --> 250-X-EXPS GSSAPI NTLM
22-11-17 21:54 - [ 2] C --> 250-8BITMIME
22-11-17 21:54 - [ 2] C --> 250-BINARYMIME
22-11-17 21:54 - [ 2] C --> 250-CHUNKING
22-11-17 21:54 - [ 2] C --> 250-XEXCH50
22-11-17 21:54 - [ 2] C --> 250-XRDST
22-11-17 21:54 - [ 2] C --> 250 XSHADOW
22-11-17 21:54 - [ 2] S <-- STARTTLS
22-11-17 21:54 - [ 2] C --> 220 2.0.0 SMTP server ready
22-11-17 21:54 - [ 2] ************ New (secure) connection to: 192.168.XXX.XXX
22-11-17 21:54 - [ 2] S <-- EHLO PXXDXOR.aXXiXg.local
22-11-17 21:54 - [ 2] C --> 250-XXX.aXXiXg.com Hello [192.168.XXX.23]
22-11-17 21:54 - [ 2] C --> 250-SIZE
22-11-17 21:54 - [ 2] C --> 250-PIPELINING
22-11-17 21:54 - [ 2] C --> 250-DSN
22-11-17 21:54 - [ 2] C --> 250-ENHANCEDSTATUSCODES
22-11-17 21:54 - [ 2] C --> 250-AUTH NTLM LOGIN
22-11-17 21:54 - [ 2] C --> 250-X-EXPS GSSAPI NTLM
22-11-17 21:54 - [ 2] C --> 250-8BITMIME
22-11-17 21:54 - [ 2] C --> 250-BINARYMIME
22-11-17 21:54 - [ 2] C --> 250-CHUNKING
22-11-17 21:54 - [ 2] C --> 250-XEXCH50
22-11-17 21:54 - [ 2] C --> 250-XRDST
22-11-17 21:54 - [ 2] C --> 250 XSHADOW
22-11-17 21:54 - [ 2] S <-- MAIL FROM:<aXXg@aXXiXg.com>
22-11-17 21:54 - [ 2] C --> 250 2.1.0 Sender OK
22-11-17 21:54 - [ 2] S <-- RCPT TO:<aXXg@aXXiXg.com>
22-11-17 21:54 - [ 2] C --> 250 2.1.5 Recipient OK
22-11-17 21:54 - [ 2] S <-- DATA
22-11-17 21:54 - [ 2] C --> 354 Start mail input; end with <CRLF>.<CRLF>
22-11-17 21:54 - [ 2] C --> 250 2.6.0 <32143133.1.1511384047544@PXXDXOR.aXXiXg.local> [InternalId=1] Queued mail for delivery
22-11-17 21:54 - [ 2] S <-- QUIT
22-11-17 21:54 - [ 2] C --> 221 2.0.0 Service closing transmission channel
22-11-17 21:54 - [ 2] ~~~~~~~~~~~~ Connection Terminated ( 1891)

AG,

This means your Exchange is fine. Can you please contact us via phone or email. We may have to do a remote screen share to see what is wrong. Please note that our office is closed on Thursday and Friday for Thanksgiving. Therefore, if possible call us so this gets resolved before the upcoming long weekend.

message send to your support mailbox support@synametrics.com 

After contacting the supportdesk i managed to solve the issue, many thanks to the support team of synametrics.

For the people who are having similar issues and see this topic, a quick resume of what solved my problem:

Cause:

* After a look in the XEAMS webconsole -> Tools -> View logs -> SMTPProxyConversation.log, the supportdesk did find the following error "452 4.3.1 Insufficient system resources"

*.* If you have this error this means your Exchange Server exceeded the "Back Pressure" threshold and that inbound mail submission has stopped or in other words the disk where the Exchange database transition logs are stored is (almost) full.

* If you have like me a (homelab) environment with no backup software that is Exchange aware + Full VSS (Volume Shadow Copy Service) support then your transition logs are not being truncated.

*.* In my case i did backup my sever but not with a Backup tool that is Exchange + Full VSS aware the transition logs used 44GB of space.

Fix:

* The easy way expend your disk and wait until free space passes the threshold again. (not recommended)

* Backup your server with a tool that supports Exchange + Full VSS. (such tools cost a lot of money i cant afford for a hobby/learning)

* Do a Full Windows Backup, a feature in Windows Server that can be activated, on the Exchange machine with Full VSS option. The windows backup will do a backup and truncate your logs files.

Note: Its not recommended to manual delete the transition logs because you lose the recoverability of data.