MS Exchange 2013 failed to send e-mail batch from 3-rd party program

Hello experts.
I have a 3-rd party program, which connect to CAS server thru smtp for sending batch of e-mails. It began to work, but after 30-40 e-mails stop transfering, with "remote socket error" in CAS`s receive connector logs. I checked default frontend receive connector, and have changed "maxinboundconnectionspersource" from 20 (default) to unlimited and "maxinboundconnectionpercentagepersource" from 2 to 100% still without success. Before ms exchange 2013 has exchange 2010 with the same parameters on CAS/HUB default receive connector and all worked fine.
Please help to resolve this issue.
ameriaadminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Adam FarageEnterprise ArchCommented:
On the CAS check for backpressure by searching the Event Viewer: Application logs for the following Event ID's..

- Event ID 15004 - 15007, all should be MSExchangeTransport as the source, Resource Manager for the category.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ameriaadminAuthor Commented:
Dear Adam, I`ll check it. Now I am out of the office.
Want to make new receive connector especialy for this batch sending. In some articles read that this issue can rase because of bult-in anti-malware, which can`t process lot of e-mails at a time. How can I configure to stop using built-in anti-malware for that special receive connector?  And the other question, when I use this 3-rd party program, route is:
sending server --> CAS --> MBX --> ex2010 edge. What MBX doing here, if recepients are outside?
Best regards
0
Adam FarageEnterprise ArchCommented:
The mailbox would do nothing.. it should go Exchange 2010 EDGE > CAS > Mailbox (for local delivery). If you are just relaying you relay off the CAS not the Mailbox role.
0
ameriaadminAuthor Commented:
and what about anti-malware, can I configure it to not touching that receive connector?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.