Re: Murder: seems like timsieved of frontend does not proxy well.

2003-06-20 Thread Dmitry Novosjolov
e etc ... ? Any help would be so great. On Friday 20 June 2003 16:47, Dmitry Novosjolov wrote: > Hello, > > I'm finishing my Murder cyrus-2.2a installation: now I want that timsieved > running on a frontend server would be able to proxy requests to a proper > backend.

Murder: seems like timsieved of frontend does not proxy well.

2003-06-20 Thread Dmitry Novosjolov
Hello, I'm finishing my Murder cyrus-2.2a installation: now I want that timsieved running on a frontend server would be able to proxy requests to a proper backend. I'm accessing a sieve service with a websieve application (perl) (I also tried to work with sieve via sieve plugin for SquirrelMai

Sasl-2.1.13 with heimdal kerberos implementation does not comple

2003-06-18 Thread Dmitry Novosjolov
Hi, I've spent some time trying to complie sasl with GSSAPI support, but I've encoutered many problems. Here they are: 1. the configure script does not determine correctly the implementation of my kerberos libraries. I installed heimdal but it thinks it's MIT. I think this machine never knew

Some kind of bug in cyrus-imapd-2.2.0-alpha in vacation handling

2003-06-09 Thread Dmitry Novosjolov
Dear List Members, I've found that every message which gets answered with vacation facility of sieve has a subject "subject". I do not think it's intended :) I also do not think that I'm the first discoverer of this. For your information: in the file source_code_root/sieve/bc_eval.c should be

Murder installation: authentication hints.

2003-06-08 Thread Dmitry Novosjolov
Dear List members, I have a murder cyrus installation with 2 backends and 3 frontends. I'm using sasl_pwcheck_method: auxprop in the imapd.conf (PLAIN passwords I think ?). My users use IMAP and SIEVE rules. As I understand the murder concept: imapproxyd at frontends proxies connections to th

Re: Whether cyrus murder 2.1.11 can work with cyrus murder 2.2.0-alpha ?

2003-06-03 Thread Dmitry Novosjolov
Thanks a lot, Rob, All is fine. Cyrus forever :) About seen state: I cannot tell you what exactly was wrong with seen state first time I migrated from 2.1.12 to 2.2.0. But today all was ok. Dmitry. On Friday 30 May 2003 20:35, you wrote: > On Fri, 30 May 2003, Dmitry Novosjolov wrote: >

Whether cyrus murder 2.1.11 can work with cyrus murder 2.2.0-alpha ?

2003-05-30 Thread Dmitry Novosjolov
Dear List members, First I would like to thank you for answering to my previous questions, you gave me quite valuable feedbacks. Now there is another one: I had problems with preserving a seen state of mails while migrating from 2.1.11 to 2.2.0. So I would like to stay on version 2.1.11 on one

pop3proxyd not found

2003-05-29 Thread Dmitry Novosjolov
Dear List Members, I'm using IMAP on cyrus-murder installation (cyrus-imap-2.2.0-alpha). All is fine so far. I want to have a pop3 service on frontend machine, which will proxy pop3 connections to appropriate backend server. When I put these lines in cyrus.conf (as recommended in documentatio

Re: mail subject's problem

2003-02-20 Thread Dmitry Novosjolov
Hello, I think I had the same issue with subjects, here is what I did: I removed from cyrus-imapd sources a line which changes subject if the subject consists non 7 bit chars. You can easily find where it is in source code by greping the line: reject8bit. I cannot tell more specifically at the mo

SNMP cyrus monitoring.

2003-01-23 Thread Dmitry Novosjolov
Hi All, has anybody succeded in using SNMP statistics of cyrus IMAP server ? If so, can you please point me in right direction of how to monitor the activity of Cyrus-imapd-2.1.11 server? I've heard about togowar, but cyrus documents are empty in this chapter ... -

Cyrus-2.1.11 error: message is no longer available

2003-01-14 Thread Dmitry Novosjolov
Hello All, I've upgraded cyrus-2.1.4 to cyrus-2.1.11 and sometimes message could not be retrieved from the server, it is shown as deleted but not read in my outlook express. Outlook express shows "message is no longer available on server". The problem can be fixed manually by deleting message file