On Sat, 18 Feb 2006, Simon Matter wrote:
My question: Did anybody using delayed expunge have any problem with it?
No, our experience is very good, too.
I run cyr_expire at 04:00, after backup is funished.
It takes about an hour:
Feb 20 05:01:06 errol cyr_expire[2687]: expunged 22206 out of
On Mon, 2006-02-20 at 10:48 +0600, mitrohin a.s. wrote:
On Fri, Feb 17, 2006 at 11:56:00AM -0500, Rosenbaum, Larry M. wrote:
How do I configure Cyrus to use multiple SSL certificates/private keys?
I want users to be able to reach the server as either a.example.com or
a.b.example.com. I
Kjetil Torgrim Homme wrote:
On Mon, 2006-02-20 at 10:48 +0600, mitrohin a.s. wrote:
On Fri, Feb 17, 2006 at 11:56:00AM -0500, Rosenbaum, Larry M. wrote:
How do I configure Cyrus to use multiple SSL certificates/private keys?
I want users to be able to reach the server as either
Scott Russell wrote:
In cyrus 2.3.1 can I configure some of the nntp groups to be read only?
For some groups I don't want users to be able to post messages through
nntp to the group.
Does anyone have an idea on how to set nntp groups as read only in
Cyrus? Review of the netnews docs did not
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi all,
i've cyrus-imap v2.3.1 built/installed on osx 10.4.5.
when i:
% telnet mail.myserver.com imap
the session response is:
Connected to mail.myserver.com.
Escape character is '^]'.
* OK devserver Cyrus
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi steve,
where, i *thought* servername: defines what that the * OK ... response
string should be.
where/what must i define to properly assign/display that string?
That's the right place, there's a bug in 2.3.1 (already fixed in CVS).
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi steve,
Nope, they didn't backport any of it, and it's basically that simple.
...
This is all I changed on mine, and it Works for Me(tm)
ez nuf ... works like a champ!
% telnet mail.myserver.com imap
Trying 10.0.0.5...
OpenMacNews wrote:
i am presuming that this fix, and fixes in general, are not backported to
releases.
i, of course, can apply the fix as a patch to 2.3.1 source myself ... do you,
perchance, have a
link to the *actual* cvs fix checkin? or is it as simple as your post implied,
namely:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi all,
i'm running cyrus-imapd 2.3.1 on osx 10.4.5.
i can login, open files, etc etc. loggings fine ... or so it seems.
if i restart in debug mode, -D, i see @ console:
No log handling enabled - turning on stderr logging
On Mon, 20 Feb 2006, OpenMacNews wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi all,
i'm running cyrus-imapd 2.3.1 on osx 10.4.5.
i can login, open files, etc etc. loggings fine ... or so it seems.
if i restart in debug mode, -D, i see @ console:
No log handling
Hello. I'm having a problem with Cyrus-IMAPD 2.2.12 with Cyrus-SASL 2.1.19's
saslauthd.
When I login using the LOGIN method, I see saslauthd doing it's lookup, and
OpenLDAP logs show it as well, and it's all successfull. However, when trying
to do a PLAIN, DIGEST-MD5, or CRAM-MD5 auth to the
11 matches
Mail list logo