Email Security.cloud

Hi,

it may be a odd question, but I have problems understanding the system of this outbound/inbound routes.

Following scenario: an external company should be able to send emails on behalf of us to our employees. Did I understood it right that I need to add the IP address of the mail server of this company to our outbound route? If so, can this company then try to send emails by using cluster1.eu.messagelabs.com? Or does the company need to use the cluster1out.eu.messagelabs.com?

These emails are just going in one direction: from the external company to us (but using our domain as sender).

Or did I misunderstood it and I need to add an inbound route? I would be very happy if someone could explain that to me. Thanks a lot!

Regards,

sisc1005

Hello!

Third-parties routing mail on your behalf should not be attempting to route mail out through our systems.  It would not be an inbound or outbound route with us.  The third-party server should use DNS to send mail to your MX Records the same as any party sending mail to you.  If they are unable to route via MX and want a specific server, then you would provide cluster1.eu.messagelabs.com. The fact they are using your own domain doesn't mean they should be added as routes, it is no different than other mail coming in from any other sender.

Note: You would need to make sure they are properly authorized in your SPF Record if you have one in DNS.  They should be able to advise you what to add as the SPF Record.

For clairity:

Outbound Routes are servers under your care and control, routing mail only for your organization, that are allowed to send outbound through us to reach a third-paty recipient. This would generally be your mail server.

Inbound Routes are where we deliver mail for a domain once it enters our system.  This would generally be your mail server.