Those clients using the JangoMail transactional email platform can now send their transactional emails with greater confidence, because we've added a layer of redundancy to the sending process for these transactional emails.
Previously, all clients were assigned a single email sender through which transactional emails were routed when calling the API method SendTransactionalEmail. Non Sender Score Certified clients would have their transactional emails routed through sender bombay.jangomail.com, while Sender Score Certified clients would have their transactional emails routed through castle.jangomail.com. But, if that single email sender was down, then calls to SendTransactionalEmail would result in an exception, due to the API being unable to transmit the email message to the designated sender.
Now, all users are assigned two transactional email senders on two separate networks, and if the primary sender is down, the email is automatically routed through the backup email sender.
This is another small step in our goal of building the most powerful, and easiest to use, transactional email messaging platform available. For more information on JangoMail's transactional email platform, see this web page.
