Safe-Post offers ‘safe’ email delivery


Safe-Post offers ‘safe’ email delivery

Safe-Post has launched an email delivery system to address the email security issues businesses face. It claims to be the first solution to guarantee safe, immediate and confirmed delivery of sensitive information in emails, as well as the prevention of spam.

Safe-Post says this will allow IT managers to present an alternative email solution to senior management to ensure that important emails always arrive at their destination because they are delivered instantly through a direct connection created between the email sender’s out-box and receiver’s in-box.
Safe-Post suggests the ‘fatal flaw’ of today’s business email systems is that there is no guarantee that the first person to read an email is the intended recipient, thus presenting a huge security risk. Traditional email systems typically download a copy of the email message from the ISP to the corporate server before it is forwarded to the recipient’s in-box. However, during this time the email could be read by anyone with access to the corporate server and even deleted without the recipient ever knowing.

Safe-Post says it eliminates these concerns because it establishes a direct connection between the email sender’s out-box and the recipient’s in-box allowing a confidential email to be sent directly to the recipient with no risk of interception.

Safe-Post is the latest in a number of supposedly revolutionary new ‘secure’ email systems that all have swanky ‘secure’ names, but will they convince businesses that they are necessary – and usable?

Email Alerts

Register now to receive IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

COMMENTS powered by Disqus  //  Commenting policy