If you operate a corporate Exchange Server with a dedicated SMTP domain only, you might not require Sender Based Routing. The challenge begins, if you need to integrate a secondary domain, which is not exclusively hosted in your Exchange Server organization. What are typical scenarios for this situation?
- Most small businesses started with one corporate email account at a freemail provider such as T-Online, Gmail or Hotmail. The German “Handwerk” branch is a typical substitute for this scenario. After growth of the company and a demanding importance of information technology, many companies get their own domain but still need to operate the old account. The freemail provider forces to route the mails through their smarthost with an authentication per user.
- Accountants or law firms often work in independent national or global networks. They need to send mails as local “Miller Smith & Partner, LLP.” as well as global “The Law Network Corp.”. In this case the emails with their local domain are sent directly to the Internet and the emails with the global domain need to be delivered to the network’s headquarters.
- Outsourcing companies like call centers or sales agencies sometimes need to send emails in their client’s name to end customers. The client wants to log and archive all communication and forces their contractors to route all outbound mail with the client’s domain name to pass their internal email servers.
The three scenarios above show some very good examples of the need to route by sender or sender’s properties. There might be hundreds of similar scenarios in the market. In all of these cases messageconcept ExSBR is the solution to distinguish the email routes.
