{"id":2100,"date":"2018-09-18T13:03:24","date_gmt":"2018-09-18T17:03:24","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/?p=2100"},"modified":"2018-09-18T13:03:24","modified_gmt":"2018-09-18T17:03:24","slug":"exchangedefender-introduces-new-spam-reports","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2018\/09\/exchangedefender-introduces-new-spam-reports\/","title":{"rendered":"ExchangeDefender Introduces New SPAM Reports"},"content":{"rendered":"

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

SPAM Email Reports<\/h3>\n

ExchangeDefender SPAM Email Reports remain one of our most popular features and after nearly 6 years since the last major revision we\u2019re looking to improve both the value and the functionality. For many of our end users, ExchangeDefender is the sole provider of cyber security training and information \u2013 so the responsibility of better educating our clients on the threats they are likely to face via email and web is crucial.
\nThen there is the look and feel of it. White collar workforce has largely gone away from dual monitor configurations to smaller portable devices on which users don\u2019t spend the whole day in Outlook \u2013 so our email reports that were designed for the Microsoft desktop era needed a little face lift.<\/p>\n

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

\n

New ExchangeDefender SPAM Email Reports are launching on October 1st 2018 and we\u2019ve made several significant changes to the look and feel based on user feedback.<\/h3>\n<\/blockquote>\n

– New reports feature \u201cfriendly\u201d From addresses, instead of the actual From: line we\u2019ve always used.
\n– Contrast has been improved as well as spacing, so finding information in the email is much simpler.
\n– Font size, padding, colors, etc has been modernized as well, allowing the report to look amazing on both small phone screens and large wide-screen computer displays.<\/p>\n

On the backend, our reports and email release requests are starting to embed our support at the point of release, making sure our end users get exactly what they are expecting right away. If the message isn\u2019t displaying correctly, or if it cannot be located, or if the message is continuously ending up in the SPAM quarantine even though the user believes they whitelisted it (99.999999999% they whitelist the disposable from tracking email which changes every time a message is sent, instead of whitelisting the domain) \u2013 our support will be there to assist them immediately without picking up a phone, without opening up a support ticket, without escalating it to the office manager or creating additional work. On demand service #ftw.<\/p>\n

Our mission to help protect our clients from dangerous and malicious content also has to account for threats before they become problems \u2013 which is why we\u2019re investing in training and info collateral aimed at the users so they are aware of new ways hackers are trying to exploit them. This info will be featured prominently in the service and we will cover it in detail as we ramp up production but for the time being we understand our end users have limited time and limited interest in what is going on in the world of cyber crime \u2013 so we will limit our content to 140 characters and feature relevant stuff only, nothing commercial.<\/p>\n

If you have any suggestions or ideas for our Email SPAM Reports, please do not hesitate to let us know.<\/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,48],"tags":[51,52,101,102],"class_list":["post-2100","post","type-post","status-publish","format-standard","hentry","category-exchangedefender","category-security","tag-email","tag-email-security","tag-spam-filtering","tag-spam-reports"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2100","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=2100"}],"version-history":[{"count":13,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2100\/revisions"}],"predecessor-version":[{"id":2115,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2100\/revisions\/2115"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=2100"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=2100"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=2100"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}