Exchange Send Connectors with Sophos and Mimecast
We are currently deploying Mimecast to our environment. We had setup the journaling and send connectors. We found that all the journaled traffic was causing a backlog in our on premise Sophos Email appliance. My question is, can I configure the primary send connector to our email domains instead of *, and configure the mimecast send connector for it's domain @journal.ourdomain.com.au,
ASKER
Thanks Jackson, Yeah that's what I was thinking might happen. Correct, our send connector is using Sophos as a smart host, but we don't have a second connector handling outbound. The send connector is currently set to * address space, so it does everything at the moment. The second connector would only be configured for Mimecast's Journaling.
I would setup a send connector to handle Journaling traffic which goes to mimecast directly via the edge network device and bypassing the Sophos Email Appliance.
ASKER
When you say "edge network device" what do you mean exactly? The send connector is configured to route to the primary and secondary mimecast journal servers, but I kept seeing the journal entries in the mail queue on Sophos. It makes me wonder is the first sender connector configured for "*" is interfering somehow?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'm presuming that send connector is using the Sophos as a Smart Host?
Do you have a send connector handling outbound to External domains? ( * )
Is Journaling Mimecast's only job?