{"id":2483,"date":"2019-05-09T07:03:38","date_gmt":"2019-05-09T11:03:38","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/?p=2483"},"modified":"2019-05-08T16:44:42","modified_gmt":"2019-05-08T20:44:42","slug":"exchangedefender-ptr-rbl-whitelisting","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2019\/05\/exchangedefender-ptr-rbl-whitelisting\/","title":{"rendered":"ExchangeDefender PTR & RBL Whitelisting"},"content":{"rendered":"\n
<\/div>\n\n\n\n
\"\"<\/figure><\/div>\n\n\n\n

ExchangeDefender is opening a wider beta test of our whitelisting functionality, which allows IT Solution Providers to whitelist sender mail servers that have broken DNS (missing PTR, mismatched A\/PTR records) and poor sender reputation (hosts listed on multiple RBL blacklists).<\/p>\n\n\n\n

If you have a sender you would like to whitelist against these essential network tests, please open a ticket at support.ownwebnow.com with subject \u201cWhitelist PTR\/RBL: IP Address\u201d and provide as much information in the ticket so we can accommodate this specific request. Only hard non-negotiable rejections to whitelist will be for unknown address space and dialup\/consumer cable IP addresses (because due to their nature those are typically dynamically assigned address spaces that shouldn\u2019t be relaying mail at all, they should be using their ISP mail server provided smarthost)<\/p>\n\n\n\n

Requests will be reviewed and either approved (and enrolled) or rejected within 24 hours by our CSO.<\/h3>\n\n\n\n

Background: Inability to previously whitelist broken DNS and dynamic IP address space is rooted in our mission statement. We are here, beyond everything else, to help secure the email. We know our partners, IT Solution Providers, VARs, MSPs, etc do not have the skill set, the time to properly research underlying issues, enough data and statistical models to evaluate sender IP reputation, or even the incentive to discern how big of a security threat and compromise a specific IP address with broken DNS or poor reputation may pose to your client.<\/p>\n\n\n\n

In fact, you pay us to worry about those things and keep your clients secure. But, sometimes clients like to think they know better than their technology experts, generally accepted security standards on the Internet, and ExchangeDefender. And the client is always right. But, when they get infected attachments, broadcast storm, password dumps, or other security compromises because they insisted on lowering their security \u2013 then ExchangeDefender is on the hook for securing them. And we don\u2019t get to say \u201ctold you so\u201d nor do we have any rapid means to fix the issue. <\/p>\n\n\n\n

Since my retirement, all of those hard-line policies designed to keep clients safe beyond whatever \u201cspecific business case requirement\u201d they may have, are slowly going away. Good news for the client, good news for the partners. <\/em>Good news for us, because going forward we will start providing Email Security Engineering services \u2013 so when you get a security compromise or an usual issue and you\u2019ve asked us to compromise your security \u2013 we will be able to address the issue on your behalf.<\/p>\n\n\n\n

I choose to look at this as a positive \u2013 we will help our clients meet their business needs and get the mail they desperately need \u2013 and if something breaks we will be there to help assist with the cleanup (for a fee, of course). This, among many other service related things, is just the part of the ExchangeDefender being more responsive and service oriented when it comes to our clients demands as opposed to our expert opinion as a security policy.<\/p>\n\n\n\n

\"\"
Sign up for the Webinar, click here<\/a><\/strong>!<\/figcaption><\/figure><\/div>\n\n\n\n

<\/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,1,8,22,48,17],"tags":[51,110,52,32,128,129],"class_list":["post-2483","post","type-post","status-publish","format-standard","hentry","category-exchangedefender","category-uncategorized","category-hosted-services","category-pro-tips","category-security","category-support","tag-email","tag-email-hosting","tag-email-security","tag-exchangedefender","tag-whitelist","tag-whitelisting"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2483","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=2483"}],"version-history":[{"count":34,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2483\/revisions"}],"predecessor-version":[{"id":2519,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2483\/revisions\/2519"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=2483"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=2483"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=2483"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}