I commented out sieve daemon in cyrus.conf.

The last few responses have been very helpful. I should be able to solve this 
now and will post again after some "playing around" with it.

Saturday, April 3, 2010, 4:07:57 PM, you wrote:

> Quoting Nybbles2Byte <nybbles2b...@gmail.com>:

>> Hello Reinaldo,

>> I don't use either nor do I know what these are. My limit of  
>> knowledge about sieve is that it came as part of cyrus but I have  
>> never used it.

>> I have installed horde and it has a program called ingo that filters  
>> email and uses sieve to do it. However, that is not the source of  
>> the errors as I haven't got to trying that out yet. These errors  
>> just come when an email is delivered.


> On delivery cyrus is looking for the sievescript to use for filtering.
> If there is no active sieve script, you will see the error in the log.
> If you have configured ingo it can create and activate a sievescript.

> I think the log message should be changed from IOERROR to a notice


>>> On Sat, Apr 3, 2010 at 3:39 AM, Nybbles2Byte <nybbles2b...@gmail.com> wrote:
>>>> If I restart cyrus with sieve commented out I still get the errors plus:

> where did you comment sieve out?

> --------------------------------------------------------------------------------
> M.Menge                                Tel.: (49) 7071/29-70316
> Universität Tübingen                   Fax.: (49) 7071/29-5912
> Zentrum für Datenverarbeitung          mail:  
> michael.me...@zdv.uni-tuebingen.de
> Wächterstraße 76
> 72074 Tübingen



-- 
 Nybbles2Byte                            mailto:nybbles2b...@gmail.com
----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Reply via email to