{"id":357,"date":"2012-02-22T08:41:56","date_gmt":"2012-02-22T13:41:56","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/2012\/02\/mail-flow-reloaded\/"},"modified":"2012-02-22T08:41:56","modified_gmt":"2012-02-22T13:41:56","slug":"mail-flow-reloaded","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2012\/02\/mail-flow-reloaded\/","title":{"rendered":"Mail Flow Reloaded"},"content":{"rendered":"<p><a href=\"http:\/\/www.exchangedefender.com\/blog\/media\/Mail-Flow-Reloaded_72A4\/resizedimage250187-pc-email-flying.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; border-right-width: 0px; padding-left: 0px; padding-right: 0px; display: inline; float: right; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px; padding-top: 0px\" title=\"resizedimage250187-pc-email-flying\" border=\"0\" alt=\"resizedimage250187-pc-email-flying\" align=\"right\" src=\"http:\/\/www.exchangedefender.com\/blog\/media\/Mail-Flow-Reloaded_72A4\/resizedimage250187-pc-email-flying_thumb.png\" width=\"189\" height=\"142\"><\/a>I have covered this topic here before. However, since my contribution in this blog is centered around repetitive support issues we&#8217;ll take another stab at it again since it seems that the gap in understand shows up every time we get a new batch of partners. Please feel free to print this or link this to your support staff because it&#8217;s pretty fail safe and it will save your team time as well as safe face in looking borderline incompetent when confronted with such an issue to your end users.  <\/p>\n<p>My client has reported to me that they have not received any email today (random interval of time they expected to receive mail and have not):  <\/p>\n<blockquote>\n<p>1. Always and foremost check the MX record. If this is pointed at anything other than or in addition to inbound30.exchangedefender.com, you&#8217;ve found your problem.<br \/>You can use a site like <a href=\"http:\/\/www.mxtoolbox.com\">www.mxtoolbox.com<\/a> to search this or if you&#8217;re savvy in windows cmd promp or linux there are commands to do this.  <\/p>\n<p>2. You&#8217;ve checked the MX records and the only thing that exists is inbound30.exchangedefender.com, what do I check next?<br \/>ExchangeDefender requires 1 hour to propagate across all inbound and outbound server (2 hours during peak which is defined by 8-6 EST)<\/p>\n<p>You access a computer&#8217;s command prompt and attempt the following steps:<\/p>\n<p>telnet inbound30.exchangedefender.com 25 &lt;enter&gt; (Wait for Welcome banner before proceeding)  <\/p>\n<p>ehlo yoursendingdomain.com &lt;enter&gt; (Use your actual test send domain, and wait for reply from server)  <\/p>\n<p>mail from: yourtest@domain.com &lt;enter&gt; (Use your actual test send address, and wait for reply from server)  <\/p>\n<p>rcpt to: yourclient@domain.com &lt;enter&gt; (Use your actual client address, and wait for reply from server)  <\/p>\n<p>DATA &lt;enter&gt;  <\/p>\n<p>Subject: Test &lt;enter&gt;  <\/p>\n<p>Testing please ignore. &lt;enter&gt;  <\/p>\n<p>. &lt;enter&gt; (The sole period indicates end of transmission).  <\/p>\n<p>&nbsp; <\/p>\n<p>Now you should have received a message ID if your test was successful. If you received such an ID the issue is not within ExchangeDefender. If you receive a relaying denied message you have not given the system enough time to populate the routing changes for your new or changed domain delivery point.  <\/p>\n<p>3. Log into https:\/\/admin.exchangedefender.com with your Service Provider ID (Hint: It&#8217;s not a domain nor an email address). If you need this and are unsure open a support request and we&#8217;ll provide you the credentials. Unfortunately, we cannot provide this type of information over the phone if you call in looking for this you&#8217;ll be directed as such.<\/p>\n<\/blockquote>\n<p>Once you log in, click on Mail Log at the top then search for your test message.  <\/p>\n<p>If you see the status as Deferred 9 times out of 10 its either the ISP or a firewall not allowing our subnets to deliver the message, the last 1 out of 10 is the IP restrictions weren&#8217;t set in Exchange. For an updated list of our ranges please visit:  <\/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>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-357","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/357","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=357"}],"version-history":[{"count":0,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/357\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=357"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=357"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=357"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}