BorderWare Technologies announced the release of version 5.0 of MXtreme Mail Firewall software at the Networld+Interop show in Las Vegas. The new release is specifically designed with increased performance to better protect an organization’s e-mail infrastructure.<\/p>\n","protected":false},"excerpt":{"rendered":"
MXtreme 5.0 is specifically designed with increased performance to better protect an organization’s e-mail infrastructure against attacks that can bring down a corporate e-mail system in real time.<\/p>\n
E-mail is business critical and time sensitive, so any delays in processing due to volume spikes or increasing volumes are unacceptable,” said Tim Leisman, CEO, “MXtreme 5.0 performance enhancements translate to significant added value because they can process increasing e-mail volumes without changing their current infrastructure.”<\/p>\n
BorderWare has more closely integrated MXtreme into corporate directory services to improve its ability to provide real-time directory lookups. This allows any updates to the directory to be automatically recognized by MXtreme 5.0, removing the need to update disparate systems on a continuous basis.<\/p>\n
Mxtreme 5.0 also adds Objectionable Content Filtering, an end user-manageable list that can be customized to meet the specific needs of any organization.<\/p>\n
The rules can also be applied to both inbound and outbound messages in order to stop unwanted content from entering an organization and prohibiting sensitive information from leaving an organization.<\/p>\n
Also included is the ability to customize the lists in accordance with specific compliance requirements such as HIPAA, Sarbanes Oxley and PIPEDA.<\/p>\n
Finally, BorderWare has upgraded the administrator and user interfaces to be easier to use.<\/p>\n
http:\/\/www.messagingpipeline.com\/showArticle.jhtml?articleID=162100577<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1410","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1410","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1410"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1410\/revisions"}],"predecessor-version":[{"id":3897,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1410\/revisions\/3897"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1410"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1410"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1410"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}