Hi Robert,
I believe that the CREATE is actually being tried at the top level, and
not under INBOX. Cyrus stores all of its users' email under INBOX.
Try setting your inbox root to "INBOX" in your client...
Cove
On Friday, February 21, 2003, at 07:44 PM, Robert Urban wrote:
Hello,
i've just
Hello,
i've just set up v2.1.12 on a RedHat 8.0 system using sasl2.
I've created a single user (urban) using cyradm, and now I'm using
Mozilla 1.0.1 ("the client") as MUA to test. The client is connecting
to the IMAP server using TLS sucessfully. When the client tries to
create the "Drafts" or
> thing is: I can't log me in. Although Cyrus is up and running (telnet
> localhost imap: "cyrus imap4 2.1.9 server ready"), when I try e.g. LOGIN
> cyrus, it will say LOGIN BAD please login first.
Just to be very clear, you can't just send LOGIN user pass and hope it
works, you have to follow the
To be clear about this, you did create an account within Cyrus's db using
cyradm, not just a system account correct?
- Original Message -
From: "Jochen Stärk" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 21, 2003 3:44 PM
Subject: beginner's question
> hi there,
>
>
hi there,
I've installed Suse 8.1 professional and decided to go from uw imap with
shadow authentication to the cyrus server that ship with suse. Well, the
thing is: I can't log me in. Although Cyrus is up and running (telnet
localhost imap: "cyrus imap4 2.1.9 server ready"), when I try e.g. LO
On 21 Feb 2003, James Miller writes:
> Would the LOGFILE statement go into the .procmailrc recipe?
Yes. Running the command "man procmailrc" will provide more details,
if you need them.
> It seems to me LMTPD is rejecting the messages because of header
> problems.
Only because what you are sen
Date: Fri, 21 Feb 2003 12:30:21 -0500 (EST)
From: David A Powicki <[EMAIL PROTECTED]>
[...]
This computer seems happy and fast in all respects, except for
mailbox creations (4 seconds) and deletions (about 2 seconds) and
ACL updates (2 seconds). A truss of an imapd that creates a
James Miller wrote:
>
> Would the LOGFILE statement go into the .procmailrc recipe? Also, I have
> MIMEDefang (calling SpamAssassin and ClamAV virus scanner). Here are some
> of the headers that get added to all of our mail.
>
> X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mime
On Fri, 21 Feb 2003, James Miller wrote:
> Are there any know issues between cyrus and mimedefang?
I run cyrus, sendmail, and MIMEDefang. I use the cyrusv2 mailer though,
I don't use procmail. I've used it with procmail too, but it's been a
while...
( and yes, the LOGFILE= part would go in the
Would the LOGFILE statement go into the .procmailrc recipe? Also, I have
MIMEDefang (calling SpamAssassin and ClamAV virus scanner). Here are some
of the headers that get added to all of our mail.
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
X-Spam-Status: No, hits=-1.
Salutations,
We are seeing slow mailbox creation times and are wonderin
On Fri, 21 Feb 2003, Etienne Goyer wrote:
> I would have another question concerning MUPDATE. The white-paper on
> Cyrus imapd Murder hinted about the possibility(1) of having your MUPDATE
> server replicating. If it is available, I would like to replicate the
> MUPDATE server for both scalabili
Robert Scussel wrote:
There are actual multiple ways to do this. From what I understand you
have 2 boxes, one the original server, and a new one.
You may want to do this in two stages. Cyrus provides a lot of tools
to upgrade between versions. That being said, you may want to
replicate Cyru
On Fri, 21 Feb 2003, Etienne Goyer wrote:
> First, the installation we are planning must support both POP (legacy)
> and IMAP. Since the mailboxes will be spread on at least two imapd
> backend, we will have a problem presenting a unified POP access. The
> obvious solution would be to have diffe
The biggest thing when upgrading this way is if you change the type of
layout that you want (ie. fullhashdir, etc.) however, since the
distribution has tools to change things around (tools/rehash), I have
found that converting the mailboxes a few times will not break anything
too severely :)
T
Greeting again,
I would have another question concerning MUPDATE. The white-paper on
Cyrus imapd Murder hinted about the possibility(1) of having your MUPDATE
server replicating. If it is available, I would like to replicate the
MUPDATE server for both scalability and automatic failover, somewha
Greeting,
We are presently considering the use of a Cyrus imapd Murder for a
somewhat large installtion (12K mbox now, expected to grow to 100K
somewhen in the future). I would have two questions.
First, the installation we are planning must support both POP (legacy)
and IMAP. Since the mailbox
There are actual multiple ways to do this. From what I understand you
have 2 boxes, one the original server, and a new one.
You may want to do this in two stages. Cyrus provides a lot of tools to
upgrade between versions. That being said, you may want to replicate
Cyrus-2.0.16 on the new box,
I currently have an olde version of cyrus working:
name : Cyrus
version: v2.0.16
vendor : Project Cyrus
support-url: http://asg.web.cmu.edu/cyrus
os : Linux
os-version : 2.4.18-4GB
environment: Cyrus SASL 1.5.27
Sleepycat Software: Berkeley DB 4.0.14: (November 18
19 matches
Mail list logo
