From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <2324AE74-36F9-4BF3-B0C8-55B517EFBFFE@orthanc.ca> From: Lyndon Nerenberg To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> In-Reply-To: <1a579fc66314c00596b0b6f99acf5fc8@quanstro.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Subject: Re: [9fans] upas/smtpd password authentication Date: Mon, 17 Dec 2007 13:05:52 -0800 References: <1a579fc66314c00596b0b6f99acf5fc8@quanstro.net> Topicbox-Message-UUID: 1bd5430e-ead3-11e9-9d60-3106f5b1d025 On 2007-Dec-16, at 15:16 , erik quanstrom wrote: > tls seems like something extra to break. i have several > dozen mac/windows users that need detailed instructions > for every change. > > i'm not a security expert. what case that i can't currently see > would tls solve for me that's worth the extra configuration. > what am i missing? Starting with RFC 3516 (latest IMAP4rev1), TLS support is mandatory. I'm not sure what problems you're running into with clients -- I've rolled out TLS-aware IMAP clients to hundreds of end-users, and it's no more difficult than any of the other IMAP4 configuration you have to deal with. For most clients these days, enabling TLS involves ticking off a checkbox.