We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

MSExchange Transport receive connector flooded with failed connections after open relay

D_Hartup
D_Hartup asked
on
Medium Priority
598 Views
Last Modified: 2013-11-15
sbs2008 server, exchange 2007 latest service packs.  Discovered an open relay on the server last night.  80,000 emails queued up.  

They were going through a specific send connector I set up for a 3rd party application on a 2nd server on the LAN to relay email. I disabled the send connector and deleted the queue database.  As soon as I enable that connector, the mails start flooding in again.  I have AV on the 2nd server, and ran a MWB scan which all came up clean. The IP addresses all appear to be external and have been creating this event warning every few seconds.

The send connector is still disabled, however I created a fresh one and ran an open relay test on it and it passed.  There are no messages stuck in the queue now and mail is flowing, however I'm concerned at the number of warnings appearing all coming from different IPs. The event ID relates to the new send connector that I created too.

Any insight would be appreciated.
Comment
Watch Question

Author

Commented:
sorry to amend, everywhere I've said 'send connector' I meant receive connector
Office 365 & Exchange Architect
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
Already done:

"The send connector is still disabled, however I created a fresh one and ran an open relay test on it and it passed"

Author

Commented:
knowing I had an open relay was just the beginning.  Emptying the queue was another.  2003 exchange is a piece of cake in comparison!
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.