My employer uses Tumbleweed. Be careful on how you setup the triggers for securing e-mails. I have sent innocuous e-mails that our policies flagged as requiring security (including to this list, hence the "not secure" addition to the subject line!). Yet I can send an e-mail with the phrase "the root password to the Solaris server is makemydaygeek" and it would sail through... Not Tumbleweed's fault, it's the arcane policies we have setup...
Mark Hennessey -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ballinger Sent: Friday, November 16, 2007 3:16 PM To: [email protected] Subject: Re: [U2] OT: Email encryption I have a client that uses Tumbleweed to send secure emails. It works at the email server level (these folks use Exchange), intercepting any email message with the string ##SECURE in the subject. It then sends an email to the recipient telling them they have a secure email waiting for them at the client site; they need to connect to the site (via https by clicking a link) and authenticate themselves (or if first time create a user & password), then they can view the text + attachments of the original email. Works seamlessly with outlook+exchange and with automatically generated emails from the UV/Linux system that use SMTP to connect to the exchange server. Should also work with other email clients. Not cheap, but pretty cool. Another option would be pgp/gpg if full paranoia mode is required. /Scott Ballinger Pareto Corporation Edmonds WA USA 206 713 6006 ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
