Date: Thu, 2 May 2002 13:31:31 +0200 From: "Aragon Gouveia" <aragon@phat.za.net> To: "Mario Pranjic" <mario.pranjic@irb.hr>, <freebsd-security@FreeBSD.ORG> Subject: Re: sslwrap and imap Message-ID: <002d01c1f1cc$e93bd740$01000001@aragon> References: <Pine.GSO.4.32.0205021249220.566-100000@nippur.irb.hr>
next in thread | previous in thread | raw e-mail | index | archive | help
Howdy, > > A possibly much better solution is to just use courier-imap in > > /usr/ports/mail. Courier-imap is a more robust, more secure, more > > featureful imap daemon, and it speaks ssl natively - no need to use > > sslwrap. The only barrier to using courier-imap is that the mailspools > > must be maildirs instead of traditional mbox's. > > Yes, the maildir concept doesn't suit me. So I gave up from Courier-imap. > Too bad, because I think it's a great imapd. I'm assuming you're using uw-imap. If so, I can highly recommend compiling your cclient with SSL support (and possibly any other mods like home Mailboxes?) before installing uw-imap. Like this, it gets called from inetd as follows: imaps stream tcp nowait root /usr/local/libexec/imapd imapd And you have a nice neat uw-imaps daemon :). Calling it using just "imap" as the service name will still allow you a clear text imapd. Haven't tried sslwrap, but I used to do the same thing with stunnel and a non SSL'd uw-imap and found it problematic at times. This works flawlessly! Regards, Aragon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002d01c1f1cc$e93bd740$01000001>