Simon Matter wrote:
Simon Matter wrote:
On Sun, 23 May 2004, Simon Matter wrote:
I have just finished rebuilding my 2.2.4 rpms and I've got the same
problem on my own server where I tested the build. I was able to
access
some folders but some others didn't work.
Was there anything
Yes, I think I have turned on imaps in my cyrus.conf...
# UNIX sockets start with a slash and are put into /var/imap/socket
SERVICES {
# add or remove based on preferences
imap cmd="imapd" listen="imap" prefork=0
imaps cmd="imapd -s" listen="imaps" prefork=0
pop3 cmd="pop3d" listen="pop3"
Title:
2004
www.xingtaiedu.com???,.
?
0319-2394259 2626330
0319-2624300
:http://www.xingtaiedu.com
Hello,
I am trying to do an update from Cyrus 1.5.19 to Cyrus 2.1.16.
My problem is, that with Cyrus 2.1.16 I cannot read mailboxes which were
created with 1.5.19. The client says: Mailbox does not excist, or
something like that. Creating a new mailbox and then read it, is no problem.
I think
I'm trying to set up the IMAP server so that the mail boxes are auto
created. For authentication I'm using saslauthd that uses my OpenLDAP
server. I can authenticate fine but the mailboxes don't seem to get
created.
This is my /etc/imapd.conf:
configdirectory: /var/imap
partition-default:
## Paul van der Vlis ([EMAIL PROTECTED]):
I am trying to do an update from Cyrus 1.5.19 to Cyrus 2.1.16.
My problem is, that with Cyrus 2.1.16 I cannot read mailboxes which were
created with 1.5.19. The client says: Mailbox does not excist, or
something like that. Creating a new mailbox and
On Mon, 24 May 2004, Simon Matter wrote:
The backtrace is from RedHat 7.2 running ext3. Nothing special here.
Switching back to 2.2.3 made it work again and I also don't see any
corruption.
Are the backtraces and straces consistent in their content?
Here is an ltrace in case this helps:
[snip]
Ok,
Hi all,
i am new subscriber here, so sorry for replying in this form.
2 days ago i tryed Cyrus-Imapd-2.2.4 on two host. And get same problem :
lmtp crash with BUSY error. But only for one host, and not allways(on
same user).I donwgraded to 2.2.3. For another host all works ok up to
today with
Simon Matter wrote:
Simon Matter wrote:
On Sun, 23 May 2004, Simon Matter wrote:
I have just finished rebuilding my 2.2.4 rpms and I've got the same
problem on my own server where I tested the build. I was able to
access
some folders but some others didn't work.
Was there anything
On Mon, 24 May 2004, Simon Matter wrote:
The backtrace is from RedHat 7.2 running ext3. Nothing special here.
Switching back to 2.2.3 made it work again and I also don't see any
corruption.
Are the backtraces and straces consistent in their content?
Here is an ltrace in case this helps:
Hi all,
Not trying to steal the tread ;-)
But i hope additional/other info could be helpfull ?
For the last couple of days i try to upgrade a FreeBSD 4.9 box from
2.2.3 to 2.2.4 ...
Luckally i did not have the problems described here, but NO WAY i was
able to get sieve working with
On Mon, 24 May 2004, Bob Tito wrote:
Luckally i did not have the problems described here, but NO WAY i was able to
get sieve working with unixhierachysep and altnamespace enabled.. The scripts
were just ignored.. reverting back to 2.2.3 solved the problem right away. I
disabled altnamespace,
On Mon, 24 May 2004 [EMAIL PROTECTED] wrote:
What do you mean by normal IMAP LOGIN command ?
Uh, the LOGIN command as defined by RFC3501, RFC2060, and so on. As
opposed to using SASL (the protocol -- not the library) to authenticate.
If you want to talk about someting like using outlook express
What do you mean by normal IMAP LOGIN command ?
If you want to talk about someting like using outlook express or eudora
by default, it does not work :-/
I think I will require email clients like Mozilla or Thunderbird, with a
secured authentification, the others way are definitively impossible
Well, then you have another problem unrelated to the advertising of
PLAIN and LOGIN SASL mechanisms, I suspect.
I think so ;)
On Mon, 24 May 2004 [EMAIL PROTECTED] wrote:
What do you mean by normal IMAP LOGIN command ?
Uh, the LOGIN command as defined by RFC3501, RFC2060, and so on. As
Bob Tito wrote:
Hi all,
Not trying to steal the tread ;-)
But i hope additional/other info could be helpfull ?
For the last couple of days i try to upgrade a FreeBSD 4.9 box from
2.2.3 to 2.2.4 ...
Luckally i did not have the problems described here, but NO WAY i was
able to get sieve working
Ken Murchison wrote:
Bob Tito wrote:
Hi all,
Not trying to steal the tread ;-)
But i hope additional/other info could be helpfull ?
For the last couple of days i try to upgrade a FreeBSD 4.9 box from
2.2.3 to 2.2.4 ...
Luckally i did not have the problems described here, but NO WAY i was
able
Bob Tito wrote:
Hi all,
Not trying to steal the tread ;-)
But i hope additional/other info could be helpfull ?
For the last couple of days i try to upgrade a FreeBSD 4.9 box from
2.2.3 to 2.2.4 ...
Luckally i did not have the problems described here, but NO WAY i was
able to get sieve
Simon Matter wrote:
Bob Tito wrote:
Hi all,
Not trying to steal the tread ;-)
But i hope additional/other info could be helpfull ?
For the last couple of days i try to upgrade a FreeBSD 4.9 box from
2.2.3 to 2.2.4 ...
Luckally i did not have the problems described here, but NO WAY i was
able to
On Mon, 24 May 2004, Ken Murchison wrote:
The hash_enumerate() function is also used by some other cyrus-imapd
programs so I could think, without having a closer look, that it could
also break other programs, right? I suggest testing it on a affected
platform with the patch applied.
Obviously a
On Mon, 24 May 2004, Ken Murchison wrote:
The hash_enumerate() function is also used by some other cyrus-imapd
programs so I could think, without having a closer look, that it could
also break other programs, right? I suggest testing it on a affected
platform with the patch applied.
Simon Matter wrote:
Bob Tito wrote:
Hi all,
Not trying to steal the tread ;-)
But i hope additional/other info could be helpfull ?
For the last couple of days i try to upgrade a FreeBSD 4.9 box from
2.2.3 to 2.2.4 ...
Luckally i did not have the problems described here, but NO WAY i was
Hi:
I am new to cyrus imapd.
I have configured sendmail using cyrusproto.mc, and I tried to send
email to cyrus imapd, the email were queued , and when I ran sendmail -v
-q, I got error messages Conneting to Cyrus... Operating system error,
can you shed some light on this. Thanks.
Frank Zhang
I just tried this patch, and everything compile fine.
I wiped out my installation and mailbox partitions and started from
scratch with this new version. I ran into another problem right away.
When trying to do various cyradm operations, set ACL's and Deleting
mailboxes, cyradm will just hang.
On Mon, 24 May 2004, AJ wrote:
I just tried this patch, and everything compile fine.
I wiped out my installation and mailbox partitions and started from
scratch with this new version. I ran into another problem right away.
When trying to do various cyradm operations, set ACL's and Deleting
Rob,
I reverted back again, I need to keep the box up for some folks to
test a new web interface for a few days, they are already shouting at
me. :) I know for a fact there were no stale imapd's around, I checked
that out when this happened, and completely removed the old
/usr/cyrus/bin
26 matches
Mail list logo
