{"id":1867,"date":"2018-06-12T14:00:00","date_gmt":"2018-06-12T18:00:00","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/?p=1867"},"modified":"2018-06-12T13:07:50","modified_gmt":"2018-06-12T17:07:50","slug":"redesigning-our-outbound-xd-network","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2018\/06\/redesigning-our-outbound-xd-network\/","title":{"rendered":"Redesigning Our Outbound XD Network"},"content":{"rendered":"

As we hinted before in our Outbound IoT announcement<\/a>, there are some big enhancements coming to our ExchangeDefender outbound network. The job of getting the mail delivered over the Internet is more art than science and we are looking to put more resources behind this as encryption, compliance and GDPR take over. So today, I want to briefly walk you through our vision (roadmap to follow on this months webinar) of what we\u2019re about to offer at scale. <\/p>\n

\"image\"
<\/a><\/p>\n

The biggest obstacle to efficient email delivery are the actual users. I know it sucks to have a finger pointed back at you but truth is most of the delivery problems aren\u2019t caused by connectivity, routing, or SPAM filtering software, they are caused by behavior and sending patterns of users. They fall into two categories: negligence and inappropriate email usage. Negligence comes in many forms but primarily lack of security (weak passwords, unpatched servers, compromised networks\/accounts) leading to a SPAM outbreak from a domain that otherwise wouldn\u2019t be sending SPAM. Inappropriate email usage comes from users knowingly abusing their personal email accounts to send large mail merge, mailing list, commercial SPAM sort of content. Yes, everyone has a justification and an excuse for behaving the way they do and we\u2019re not here to judge that \u2013 but machines have 0 judgement and only work off \u201cscore\u201d that is calculated by adding points to a total until a message has enough to qualify as SPAM. If you look like a spammer, the remote system isn\u2019t going to care much that you aren\u2019t. We can only address these through education and we\u2019re committed to doing that at ExchangeDefender\u2026 but, we can do even better. And that\u2019s our vision for our supported outbound network.  <\/p>\n

<\/p>\n

We are currently working on consolidating our entire outbound network into a single outbound.exchangedefender.com \u2013 that means saying goodbye to \u2013corp, \u2013jr, \u2013int, \u2013misc and specialty email routing services we\u2019ve written to help address unique business requirements of our users. Starting soon, the entire network will simply allow outbound mail for person-to-person communication regardless of the message format and contents (yes, you\u2019ll be able to use out of office (OOF) notices and autoresponders again). For non person-to-person email, we\u2019ll use outbound-auth for devices, services, etc. For marketing (newsletters) we\u2019ll have one as well. <\/p>\n

\n

The big change will be in support and an active managed postmaster<\/strong>. This simply means that there will now be a monkey-in-the-middle facilitating, reporting and auditing outbound mail sending patterns to assure delivery and proper routing. Say Bob from Marketing decides to do a mail blast using his Outlook and attempts to hit 5,000 contacts. All but maybe 100-200 of those messages will actually make it through our network. Say your \u201cPassword1!\u201d security credential was compromised and someone started using your Exchange login to run a SPAM campaign \u2013 that too isn\u2019t getting out. And the support team that will be managing this flow will be the same one that will be helping you address mail problems immediately, not as a reaction 3 days later when your domain ends up on an RBL.<\/p>\n

That and you\u2019ll have additional intelligence embedded in outbound mail routing to assure delivery and start realtime conversations for things that are better handled in a chat vs. email. But sssssh that\u2019s a secret for now. Everything else about this (and the new UI) is coming in this months webinar, I cannot encourage you enough to register for it, tune in live and ask questions:<\/p>\n

New Features Webinar<\/strong>
\nWed, Jun 27, 2018 12:00 PM – 1:00 PM EDT
\nClick here to register<\/a><\/p>\n<\/blockquote>\n

We believe that the division of email flow \u2013 separating machine\/service\/device\/non-person mail from person-to-person email will give us the unique ability to more precisely deliver messages over notices and also improve our ability to get around bulk filtering that plagues us just because of the way email is routed. Getting support in there, in realtime, will make the difference between an issue being handled directly and right away as opposed to dragging on for days and offering no assurance to the client or recipient where the message went. So not only will support and client relationships improve, so will our ability to embed more features into outbound mail that will make it more effective as opposed to leaving it at \u201cbest-effort\u201d.<\/p>\n

<\/p>\n


<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-1867","post","type-post","status-publish","format-standard","hentry","category-exchangedefender"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/1867","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=1867"}],"version-history":[{"count":1,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/1867\/revisions"}],"predecessor-version":[{"id":1868,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/1867\/revisions\/1868"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=1867"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=1867"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=1867"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}