Hi everyone,
I've setup a Cyrus-Imapd-2.2.2-BETA with these statements in the imapd.conf:
altnamespace: yes
virtdomains: yes
unixhierarchysep: true
However, since adding unixhierarchysep (and doing a clean reinstall,
this is on a test server) I can no longer add user mailboxes: these all
get
Some users are complaining about random delays in communication with our
cyrus v2.1.13 server. In the telemetry logs there are lines like
11:06:20A00119 STORE 1806 +FLAGS (\Deleted)
11:06:26* 1806 FETCH (FLAGS (\Recent \Deleted \Seen))
(timestamps changed to a better readable format). This seems
Andreas S. Kerber wrote:
On Mon, Dec 08, 2003 at 03:02:36PM +0100, Andreas S. Kerber wrote:
Yes the test User has a mailbox on the backend and it is possible
login as the test User on the backend, without any problems. Accessing
the INBOX via IMAP works too (I've used mutt). Here is the output
Title:
??!
On Tue, 9 Dec 2003, Ken Murchison wrote:
Andreas S. Kerber wrote:
On Mon, Dec 08, 2003 at 03:02:36PM +0100, Andreas S. Kerber wrote:
Yes the test User has a mailbox on the backend and it is possible
login as the test User on the backend, without any problems. Accessing
the INBOX via
When trying to connect to sieve using sieveshell, using the same
userid/passwd that I've verified does work with IMAP, I'm getting the
following in the log file(s):
Dec 9 20:28:24 xx sieve[28283]: no secret in database
Dec 9 20:28:33 xx sieve[28304]: no secret in database
Dec 9
Marc G. Fournier wrote:
When trying to connect to sieve using sieveshell, using the same
userid/passwd that I've verified does work with IMAP, I'm getting the
following in the log file(s):
Dec 9 20:28:24 xx sieve[28283]: no secret in database
Dec 9 20:28:33 xx sieve[28304]: no secret in
On Tue, 9 Dec 2003, Marc G. Fournier wrote:
On Tue, 9 Dec 2003, Ken Murchison wrote:
Marc G. Fournier wrote:
When trying to connect to sieve using sieveshell, using the same
userid/passwd that I've verified does work with IMAP, I'm getting the
following in the log file(s):
