{"id":372,"date":"2012-03-14T12:40:43","date_gmt":"2012-03-14T17:40:43","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/2012\/03\/shockey-monkey-email-connector\/"},"modified":"2012-03-14T12:40:43","modified_gmt":"2012-03-14T17:40:43","slug":"shockey-monkey-email-connector","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2012\/03\/shockey-monkey-email-connector\/","title":{"rendered":"Shockey Monkey Email Connector"},"content":{"rendered":"<p>Today I am going to cross over into the Shockey Monkey realm to clarify some things that we didn\u2019t document in as much detail based on a few assumptions. And we all know what happens when you assume.  <\/p>\n<p>We assumed that nobody would point their MX record to ExchangeDefender without signing up for ExchangeDefender. And this is why I\u2019m blogging about it on the XD space, because it ends up as a support issue within in ExchangeDefender.  <\/p>\n<blockquote>\n<p><strong>I just signed up for Shockey Monkey in what order should I go about employing the email to ticket gateway?<\/strong>  <\/p>\n<p>First you need to sign up for ExchangeDefender for Service Providers (It\u2019s Free!) and it will allow you to deploy ExchangeDefender for your portal\u2019s desired email domain. Remember you must add your domain to ExchangeDefender for ExchangeDefender to process your email. The following guide walks you through the entire ordering process and deployment process. My personal piece of advice, don\u2019t touch the Exchange portion until your domain has propagated through ExchangeDefender.  <\/p>\n<p><a href=\"http:\/\/www.exchangedefender.com\/ExchangeDefender_Deployment_Guide.php\">http:\/\/www.exchangedefender.com\/ExchangeDefender_Deployment_Guide.php<\/a>  <\/p>\n<p>So don\u2019t make any DNS changes nor any Exchange side changes until the work in admin.exchangedefender.com is complete and has been propagated.  <\/p>\n<p>&nbsp; <\/p>\n<p><strong>Can I test this before I make changes?<\/strong>  <\/p>\n<p>Absolutely, you can do manual SMTP tests for both by telneting on port 25. But here\u2019s a full walk through:  <\/p>\n<p><a href=\"http:\/\/www.exchangedefender.com\/blog\/2012\/02\/mail-flow-reloaded\/\">http:\/\/www.exchangedefender.com\/blog\/2012\/02\/mail-flow-reloaded\/<\/a>  <\/p>\n<p>Once you have confirmed we are accepting mail on your behalf, then you can go back into the top link here and finish the DNS changes and Exchange side changes.<\/p>\n<\/blockquote>\n<p><strong>Finishing Touches<\/strong>  <\/p>\n<p>The smallest thus easiest thing to overlook is the vanity address forward. If you intend to use something that\u2019s NOT <a href=\"mailto:yourportal@rafiki.shockeymonkey.com\">yourportal@rafiki.shockeymonkey.com<\/a> as your email to ticket address, then you must set up a forward on your exchange or pop server to forward from (as an example) <a href=\"mailto:example@superawesomemsp.com\">example@superawesomemsp.com<\/a> to <a href=\"mailto:yourportal@rafiki.shockeymonkey.com\">yourportal@rafiki.shockeymonkey.com<\/a>.  <\/p>\n<p>NOW, you\u2019re all set.  <\/p>\n<p>Carlos Lascano<br \/>VP Support Services, ExchangeDefender<br \/><a href=\"mailto:carlos@ownwebnow.com\">carlos@ownwebnow.com<\/a><br \/>(877) 546-0316 x737<\/p>\n","protected":false},"excerpt":{"rendered":"<p> [&hellip;]<\/p>\n","protected":false},"author":40,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-372","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/372","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\/40"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=372"}],"version-history":[{"count":0,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/372\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=372"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=372"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=372"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}