Updated Xeams, Getting server communication exchange error David
    Updated Xeams, Getting server communication exchange error Synametrics Support
        Updated Xeams, Getting server communication exchange error david
            Updated Xeams, Getting server communication exchange error Anonymous
                Updated Xeams, Getting server communication exchange error david

From: David
Date: 9/21/16 3:00 AM
Topic: Updated Xeams, Getting server communication exchange error
Type: General Discussions
Post a follow up

Hi,

After a recent update. I"m just using Xeams as a Proxy on port 25. then It shoot the email to my exchange server on port 25 also. Today There was no email coming in. So I run the Diagnostic Test and it failed Server Communication: It say error communicating on my exchange server on port 25. I login to the exchange server and it is running fine. I'm able to send out email. I can even telnet exchange.server.ip 25 and was able to get in from the xeams server. I rebooted the xeams but still same error. I restarted exchange store and it started to work again. Until 4pm today it stopped again. I have to restart the exchange store again to bring it back up running. So Today two downtime

Anyone know what is causing this? Please advise. Just started happening today.

 

Top

From: Synametrics Support
Date: 9/21/16 10:33 AM
Topic: Updated Xeams, Getting server communication exchange error
Type: General Discussions
Post a follow up

David,

I have a feeling the problem is on Exchange's end and not Xeams. I say that because restarting Exchange fixes the problem temporarily. It it were Xeams, you would see this temporarily relief. How far did you get in your "TELNET" test? Did you go all the way to the DATA and QUIT commands?

Please remember that when you use the SMTP Proxy Server, Xeams will go down if Exchange goes down. If you use the regular SMTP Server for inbound, Xeams will accept the message but will queue them if Exchange won't accept them.

Check SMTPProxyConversation.log and post a small snippet here. That should show the error Exchange is running into.

 

Top

From: david
Date: 9/21/16 11:39 AM
Topic: Updated Xeams, Getting server communication exchange error
Type: General Discussions
Post a follow up

Hi,

thanks for your reply. Ok I have lookeded into the .log file and this is what I notice. I have compared the time when this happen and today is working fine. I do noticed that an error of 254 4.3.1 Insufficient system resources. (I believe it is an exchange issues running out of resources?) Am I getting too many spam that is causing this? How do I find out?

thanks

David.

 

log:

2016-09-20 20:30:17,245 - [ 618630] C --> MAIL FROM:<SpiceworksDesktoponshngdc-l1l1i@cmail19.com>
2016-09-20 20:30:17,354 - [ 618653] C --> MAIL FROM:<shipping383998@themusiczoo.com>
2016-09-20 20:30:17,838 - [ 618651] S <-- 452 4.3.1 Insufficient system resources
2016-09-20 20:30:18,103 - [ 618651] C --> QUIT
2016-09-20 20:30:18,103 - [ 618651] S <-- 221 shangback. SMTP Proxy connection successfully closed.
2016-09-20 20:30:18,103 - [ 618651] ~~~~~~~~~~~~ Connection Terminated (5769:999999)
2016-09-20 20:30:18,806 - [ 618655] ************ New connection from: 122.248.112.132
2016-09-20 20:30:19,040 - [ 618655] C --> EHLO [122.248.112.132]
2016-09-20 20:30:19,040 - [ 618655] S <-- 250-shng-exch.shangback.com Hello [ Proxied ]
2016-09-20 20:30:19,040 - [ 618655] S <-- 250-SIZE
2016-09-20 20:30:19,040 - [ 618655] S <-- 250-DSN
2016-09-20 20:30:19,040 - [ 618655] S <-- 250-ENHANCEDSTATUSCODES
2016-09-20 20:30:19,040 - [ 618655] S <-- 250-AUTH NTLM
2016-09-20 20:30:19,040 - [ 618655] S <-- 250 OK
2016-09-20 20:30:19,258 - [ 618655] C --> MAIL FROM:<shipping4842@themusiczoo.com>
2016-09-20 20:30:21,291 - [ 618652] S <-- 504 5.7.4 Unrecognized authentication type
2016-09-20 20:30:21,353 - [ 618656] ************ New connection from: 77.102.141.62
2016-09-20 20:30:21,478 - [ 618652] ~~~~~~~~~~~~ Connection Terminated (5549:999999) Unexpected input termination. Connection terminated without a graceful QUIT.
2016-09-20 20:30:21,509 - [ 618656] C --> EHLO cpc69959-sand12-2-0-cust61.16-1.cable.virginm.net
2016-09-20 20:30:21,509 - [ 618656] S <-- 250-shng-exch.shangback.com Hello [ Proxied ]
2016-09-20 20:30:21,509 - [ 618656] S <-- 250-SIZE
2016-09-20 20:30:21,509 - [ 618656] S <-- 250-DSN
2016-09-20 20:30:21,509 - [ 618656] S <-- 250-ENHANCEDSTATUSCODES
2016-09-20 20:30:21,509 - [ 618656] S <-- 250-AUTH NTLM
2016-09-20 20:30:21,509 - [ 618656] S <-- 250 OK
2016-09-20 20:30:21,665 - [ 618656] C --> MAIL FROM:<shipping87581@themusiczoo.com>
2016-09-20 20:30:22,149 - [ 618654] S <-- 452 4.3.1 Insufficient system resources
2016-09-20 20:30:22,165 - [ 618654] C --> RSET
2016-09-20 20:30:22,243 - [ 618630] S <-- 452 4.3.1 Insufficient system resources
2016-09-20 20:30:22,274 - [ 618630] C --> RSET
2016-09-20 20:30:22,352 - [ 618653] S <-- 452 4.3.1 Insufficient system resources
2016-09-20 20:30:22,545 - [ 618653] C --> QUIT
2016-09-20 20:30:22,545 - [ 618653] S <-- 221 shangback. SMTP Proxy connection successfully closed.
2016-09-20 20:30:22,545 - [ 618653] ~~~~~~~~~~~~ Connection Terminated (5581:999999)
2016-09-20 20:30:24,261 - [ 618655] S <-- 452 4.3.1 Insufficient system resources
2016-09-20 20:30:24,308 - [ 618657] ************ New connection from: 194.30.155.198
2016-09-20 20:30:24,479 - [ 618655] C --> QUIT
2016-09-20 20:30:24,479 - [ 618655] S <-- 221 shangback. SMTP Proxy connection successfully closed.
2016-09-20 20:30:24,479 - [ 618655] ~~~~~~~~~~~~ Connection Terminated (5673:999999)
2016-09-20 20:30:24,558 - [ 618657] C --> EHLO adslon-155-198.logos.cy.net
2016-09-20 20:30:24,558 - [ 618657] S <-- 250-shng-exch.shangback.com Hello [ Proxied ]
2016-09-20 20:30:24,558 - [ 618657] S <-- 250-SIZE
2016-09-20 20:30:24,558 - [ 618657] S <-- 250-DSN
2016-09-20 20:30:24,558 - [ 618657] S <-- 250-ENHANCEDSTATUSCODES
2016-09-20 20:30:24,558 - [ 618657] S <-- 250-AUTH NTLM
2016-09-20 20:30:24,558 - [ 618657] S <-- 250 OK
2016-09-20 20:30:24,886 - [ 618657] C --> MAIL FROM:<shipping852793@themusiczoo.com>
2016-09-20 20:30:26,681 - [ 618656] S <-- 452 4.3.1 Insufficient system resources
2016-09-20 20:30:26,790 - [ 618658] ************ New connection from: 103.27.238.252
2016-09-20 20:30:26,837 - [ 618656] C --> QUIT
2016-09-20 20:30:26,837 - [ 618656] S <-- 221 shangback. SMTP Proxy connection successfully closed.
2016-09-20 20:30:26,837 - [ 618656] ~~~~~~~~~~~~ Connection Terminated (5484:999999)
2016-09-20 20:30:26,977 - [ 618658] C --> EHLO ylmf-pc
2016-09-20 20:30:26,977 - [ 618658] S <-- 250-shng-exch.shangback.com Hello [ Proxied ]
2016-09-20 20:30:26,977 - [ 618658] S <-- 250-SIZE
2016-09-20 20:30:26,977 - [ 618658] S <-- 250-DSN
2016-09-20 20:30:26,977 - [ 618658] S <-- 250-ENHANCEDSTATUSCODES
2016-09-20 20:30:26,977 - [ 618658] S <-- 250-AUTH NTLM
2016-09-20 20:30:26,977 - [ 618658] S <-- 250 OK
2016-09-20 20:30:27,165 - [ 618654] S <-- 250 2.0.0 Resetting
2016-09-20 20:30:27,165 - [ 618654] C --> MAIL FROM:<April.V@travelstore.com> SIZE=127344
2016-09-20 20:30:27,165 - [ 618658] C --> AUTH LOGIN
2016-09-20 20:30:27,305 - [ 618630] S <-- 250 2.0.0 Resetting
2016-09-20 20:30:27,305 - [ 618630] C --> MAIL FROM:<SpiceworksDesktoponshngdc-l1l1i@cmail20.com>
2016-09-20 20:30:29,896 - [ 618657] S <-- 452 4.3.1 Insufficient system resources
2016-09-20 20:30:30,223 - [ 618657] C --> QUIT
2016-09-20 20:30:30,223 - [ 618657] S <-- 221 shangback. SMTP Proxy connection successfully closed.
2016-09-20 20:30:30,223 - [ 618657] ~~~~~~~~~~~~ Connection Terminated (5915:999999)
2016-09-20 20:30:30,869 - [ 618659] ************ New connection from: 43.224.112.134
2016-09-20 20:30:31,399 - [ 618659] C --> EHLO [43.224.112.134]
2016-09-20 20:30:31,399 - [ 618659] S <-- 250-shng-exch.shangback.com Hello [ Proxied ]
2016-09-20 20:30:31,399 - [ 618659] S <-- 250-SIZE
2016-09-20 20:30:31,399 - [ 618659] S <-- 250-DSN
2016-09-20 20:30:31,399 - [ 618659] S <-- 250-ENHANCEDSTATUSCODES
2016-09-20 20:30:31,399 - [ 618659] S <-- 250-AUTH NTLM
2016-09-20 20:30:31,399 - [ 618659] S <-- 250 OK
2016-09-20 20:30:31,820 - [ 618659] C --> MAIL FROM:<shipping033825@themusiczoo.com>
2016-09-20 20:30:32,163 - [ 618654] S <-- 452 4.3.1 Insufficient system resources
2016-09-20 20:30:32,163 - [ 618658] S <-- 504 5.7.4 Unrecognized authentication type
2016-09-20 20:30:32,179 - [ 618654] C --> QUIT
2016-09-20 20:30:32,179 - [ 618654] S <-- 221 shangback. SMTP Proxy connection successfully closed.
2016-09-20 20:30:32,179 - [ 618654] ~~~~~~~~~~~~ Connection Terminated (15043:999999)
2016-09-20 20:30:32,304 - [ 618630] S <-- 452 4.3.1 Insufficient system resources
2016-09-20 20:30:32,335 - [ 618630] C --> QUIT
2016-09-20 20:30:32,335 - [ 618630] S <-- 221 shangback. SMTP Proxy connection successfully closed.
2016-09-20 20:30:32,335 - [ 618630] ~~~~~~~~~~~~ Connection Terminated (55296:999999)
2016-09-20 20:30:32,335 - [ 618660] ************ New connection from: 198.101.123.219
2016-09-20 20:30:32,351 - [ 618660] C --> EHLO mail.travelstore.com
2016-09-20 20:30:32,351 - [ 618660] S <-- 250-shng-exch.shangback.com Hello [ Proxied ]
2016-09-20 20:30:32,351 - [ 618660] S <-- 250-SIZE
2016-09-20 20:30:32,351 - [ 618660] S <-- 250-DSN
2016-09-20 20:30:32,351 - [ 618660] S <-- 250-ENHANCEDSTATUSCODES
2016-09-20 20:30:32,351 - [ 618660] S <-- 250-AUTH NTLM
2016-09-20 20:30:32,351 - [ 618660] S <-- 250 OK
2016-09-20 20:30:32,351 - [ 618658] ~~~~~~~~~~~~ Connection Terminated (5561:999999) Unexpected input termination. Connection terminated without a graceful QUIT.
2016-09-20 20:30:32,351 - [ 618660] C --> MAIL FROM:<> SIZE=5655
2016-09-20 20:30:32,636 - [ 618661] ************ New connection from: 142.11.250.242
2016-09-20 20:30:32,636 - [ 618662] ************ New connection from: 103.27.238.252
2016-09-20 20:30:32,699 - [ 618661] C --> EHLO disharmonizes.tomstrignanoforexexclusive.com
2016-09-20 20:30:32,699 - [ 618661] S <-- 250-shng-exch.shangback.com Hello [ Proxied ]
2016-09-20 20:30:32,699 - [ 618661] S <-- 250-SIZE
2016-09-20 20:30:32,699 - [ 618661] S <-- 250-DSN
2016-09-20 20:30:32,699 - [ 618661] S <-- 250-ENHANCEDSTATUSCODES
2016-09-20 20:30:32,699 - [ 618661] S <-- 250-AUTH NTLM
2016-09-20 20:30:32,699 - [ 618661] S <-- 250 OK
2016-09-20 20:30:32,761 - [ 618661] C --> MAIL FROM: <stephanie.hawkins@tomstrignanoforexexclusive.com>
2016-09-20 20:30:32,823 - [ 618662] C --> EHLO ylmf-pc
2016-09-20 20:30:32,823 - [ 618662] S <-- 250-shng-exch.shangback.com Hello [ Proxied ]
2016-09-20 20:30:32,823 - [ 618662] S <-- 250-SIZE
2016-09-20 20:30:32,823 - [ 618662] S <-- 250-DSN
2016-09-20 20:30:32,823 - [ 618662] S <-- 250-ENHANCEDSTATUSCODES
2016-09-20 20:30:32,823 - [ 618662] S <-- 250-AUTH NTLM
2016-09-20 20:30:32,823 - [ 618662] S <-- 250 OK
2016-09-20 20:30:32,995 - [ 618662] C --> AUTH LOGIN
2016-09-20 20:30:33,681 - [ 618663] ************ New connection from: 42.113.179.14
2016-09-20 20:30:33,791 - [ 618664] ************ New connection from: 121.54.32.174
2016-09-20 20:30:33,884 - [ 618663] C --> EHLO [42.113.179.14]
2016-09-20 20:30:33,884 - [ 618663] S <-- 250-shng-exch.shangback.com Hello [ Proxied ]
2016-09-20 20:30:33,884 - [ 618663] S <-- 250-SIZE
2016-09-20 20:30:33,884 - [ 618663] S <-- 250-DSN
2016-09-20 20:30:33,884 - [ 618663] S <-- 250-ENHANCEDSTATUSCODES
2016-09-20 20:30:33,884 - [ 618663] S <-- 250-AUTH NTLM
2016-09-20 20:30:33,884 - [ 618663] S <-- 250 OK
2016-09-20 20:30:33,978 - [ 618664] C --> EHLO [121.54.32.168]
2016-09-20 20:30:33,978 - [ 618664] S <-- 250-shng-exch.shangback.com Hello [ Proxied ]
2016-09-20 20:30:33,978 - [ 618664] S <-- 250-SIZE
2016-09-20 20:30:33,978 - [ 618664] S <-- 250-DSN
2016-09-20 20:30:33,978 - [ 618664] S <-- 250-ENHANCEDSTATUSCODES
2016-09-20 20:30:33,978 - [ 618664] S <-- 250-AUTH NTLM
2016-09-20 20:30:33,978 - [ 618664] S <-- 250 OK
2016-09-20 20:30:34,087 - [ 618663] C --> MAIL FROM:<shipping813@themusiczoo.com>
2016-09-20 20:30:34,165 - [ 618664] C --> MAIL FROM:<shipping090@themusiczoo.com>
2016-09-20 20:30:36,835 - [ 618659] S <-- 452 4.3.1 Insufficient system resources
2016-09-20 20:30:37,193 - [ 618665] ************ New connection from: 14.166.77.82
2016-09-20 20:30:37,303 - [ 618659] C --> QUIT
2016-09-20 20:30:37,303 - [ 618659] S <-- 221 shangback. SMTP Proxy connection successfully closed.
2016-09-20 20:30:37,303 - [ 618659] ~~~~~~~~~~~~ Connection Terminated (6434:999999)
2016-09-20 20:30:37,365 - [ 618660] S <-- 452 4.3.1 Insufficient system resources
2016-09-20 20:30:37,365 - [ 618665] C --> EHLO static.vnpt.vn
2016-09-20 20:30:37,365 - [ 618665] S <-- 250-shng-exch.shangback.com Hello [ Proxied ]
2016-09-20 20:30:37,365 - [ 618665] S <-- 250-SIZE
2016-09-20 20:30:37,365 - [ 618665] S <-- 250-DSN
2016-09-20 20:30:37,365 - [ 618665] S <-- 250-ENHANCEDSTATUSCODES
2016-09-20 20:30:37,365 - [ 618665] S <-- 250-AUTH NTLM
2016-09-20 20:30:37,365 - [ 618665] S <-- 250 OK
2016-09-20 20:30:37,365 - [ 618660] C --> QUIT
2016-09-20 20:30:37,365 - [ 618660] S <-- 221 shangback. SMTP Proxy connection successfully closed.
2016-09-20 20:30:37,365 - [ 618660] ~~~~~~~~~~~~ Connection Terminated (5030:999999)
2016-09-20 20:30:37,537 - [ 618665] C --> MAIL FROM:<shipping552@themusiczoo.com>
2016-09-20 20:30:37,771 - [ 618661] S <-- 452 4.3.1 Insufficient system resources
2016-09-20 20:30:37,833 - [ 618661] C --> QUIT

Top

From: Anonymous
Date: 9/21/16 11:50 AM
Topic: Updated Xeams, Getting server communication exchange error
Type: General Discussions
Post a follow up

David,

Before answering your actual question, I'd like to make a comment regarding the log files. The number you see in the square brackets is called LCID and it uniquely identifies a complete conversation for one email. Therefore, specify one LCID on the previous page to restrict the log just for one message. That will prevent mixing up multiple incoming emails together. For example, search for 618661.

This is definitely an Exchange problem. I don't think Exchange is running into this issue because you are receiving too many junk messages. If Xeams is quarantining the messages correctly, they will never hit your Exchange server.

I recommend you:

  1. Check the Event Viewer on the machine where Exchange is running and see if it is logging any specific problem.
  2. Google "452 4.3.1 Insufficient system resources". I am sure you are not the only one running into this issue.
Top

From: david
Date: 9/21/16 12:14 PM
Topic: Updated Xeams, Getting server communication exchange error
Type: General Discussions
Post a follow up

Thanks for your reply. It is definitely not an XEAMS issues. I think I nailed down the cause of the problem. The server was running Symantec endpoint security that was causing the resource issues. I have removed it and do not need it anymore.

Thank you so much..

Top