On Mon, 9 Dec 2002, Kevin M. Myer wrote:
> What I still need to figure out is how to specify which saslauthd mux
> socket for each domain's imap process to connect to. [...] I can't seem
> to find that documented anywhere (probably because its only in this
> special case scenario that you'd even n
On Mon, 9 Dec 2002, Kevin M. Myer wrote:
> Hi,
>
> With the recent Cyrus IMAP buffer overflow exploit, its time to upgrade our mail
> server. I've been sitting on a Cyrus IMAP 2.1.X CVS install from right before
> the SASL2 requirement went into effect and have been holding off on upgrading
> un
On Mon, 9 Dec 2002, Kevin M. Myer wrote:
> Including the mux named pipe causes this to work so I think the documentation
> should read that you DO need to include the mux named pipe or maybe the
> saslauthd_path option should be changed to saslauthd_mux_path.
Yes. This is what I get for believin
On Mon, 9 Dec 2002, Kevin M. Myer wrote:
> conversation (via , I don't give anything up security-wise. In other words, I
> can rely on the transport layer to provide encryption, instead of a higher layer
> and that way email can't be sniffed either.
You do of course realize that email is transmi
