Re: SQL errors when not using SQL backend

Hi everyone, Ken Murchison wrote: Paul Boven wrote: Ken Murchison wrote: Paul Boven wrote: I'm building the latest Cyrus (imapd 2.2.8, sasl 2.1.19) and packaging it for Solaris to distrubute to several different Cyrus servers. Works like a charm but every time someone connects I get the followi

Re: SQL errors when not using SQL backend

Paul Boven wrote: Hi everyone, Ken Murchison wrote: Paul Boven wrote: I'm building the latest Cyrus (imapd 2.2.8, sasl 2.1.19) and packaging it for Solaris to distrubute to several different Cyrus servers. Works like a charm but every time someone connects I get the following errors on my seri

Re: SQL errors when not using SQL backend

Hi everyone, Ken Murchison wrote: Paul Boven wrote: I'm building the latest Cyrus (imapd 2.2.8, sasl 2.1.19) and packaging it for Solaris to distrubute to several different Cyrus servers. Works like a charm but every time someone connects I get the following errors on my serial console: imap[1

Re: SQL errors when not using SQL backend

Paul Boven wrote: Hi everyone, I'm building the latest Cyrus (imapd 2.2.8, sasl 2.1.19) and packaging it for Solaris to distrubute to several different Cyrus servers. For historic reasons we have quite a mix of authentication backends for these servers: some with /etc/passwd (via saslauthd), or

SQL errors when not using SQL backend

Hi everyone, I'm building the latest Cyrus (imapd 2.2.8, sasl 2.1.19) and packaging it for Solaris to distrubute to several different Cyrus servers. For historic reasons we have quite a mix of authentication backends for these servers: some with /etc/passwd (via saslauthd), or MySQL (via sasl_