> From: [EMAIL PROTECTED] [mailto:info-cyrus-
> [EMAIL PROTECTED] On Behalf Of Chris Hilts
>
> > We don't support CRAM-MD5, but we don't want to be warned every time
> > somebody tries to use it. Cyrus SASL was compiled without CRAM-MD5
> > support. Here is some other configuration information:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> We don't support CRAM-MD5, but we don't want to be warned every time
> somebody tries to use it. Cyrus SASL was compiled without CRAM-MD5
> support. Here is some other configuration information:
Is Cyrus reporting it can do CRAM-MD5 in the CAPABIL
> From: Ken Murchison [mailto:[EMAIL PROTECTED]
>
> Rosenbaum, Larry M. wrote:
> > Running Cyrus IMAP 2.3.1 on Solaris 9.
> >
> > Is there any way to suppress the following messages which have been
> > showing up in the syslog and authlog?
> >
> > Mar 10 10:32:23 email imaps[3908]: [ID 702911 auth
Rosenbaum, Larry M. wrote:
Running Cyrus IMAP 2.3.1 on Solaris 9.
Is there any way to suppress the following messages which have been
showing up in the syslog and authlog?
Mar 10 10:32:23 email imaps[3908]: [ID 702911 auth.notice] Couldn't find
mech CRAM-MD5
We don't support CRAM-MD5, but we d
Running Cyrus IMAP 2.3.1 on Solaris 9.
Is there any way to suppress the following messages which have been
showing up in the syslog and authlog?
Mar 10 10:32:23 email imaps[3908]: [ID 702911 auth.notice] Couldn't find
mech CRAM-MD5
We don't support CRAM-MD5, but we don't want to be warned every
