[Dovecot] Upgraded to Dovecot-1.2.16 and Sieve-1.1.8 but Still No Sieve Parameters

[Jay Welch]

So I originally installed Dovecot-1.0.7 on Centos 5.5 using yum. 
Everything was working great but I didn't have server-side filtering.

I downloaded 1.1.20 from your site and upgraded dovecot with no errors. 
Then I downloaded and installed Sieve-1.1.8 from your site with no errors.

Looking at in /usr/local/libexec/dovecot....I do have sievec and sieved 
as well. I just don't see the parameters for the sieve plug-in in the 
dovecot-example.conf. Do I need to enter that manually?

Also, do I need Managesieve to use sieve? I really don't need 
Managesieve. I just need to configure a few global filters.

Thanks




On 4/12/2011 2:34 PM, Timo Sirainen wrote:
> Then it sounds like the Dovecot version you're running hasn't been patched with managesieve support. I don't actually see you mention how you upgraded, from source or from some binary package (and in what OS/distro).
>
> Note that with v1.x if you install Dovecot + Sieve you do get both of them, but it doesn't automatically mean that Managesieve is installed. You need to patch Dovecot for that (sieve is not managesieve!)
>
> On 13.4.2011, at 0.17, Jay Welch wrote:
>
>> It is managesieve.
>>
>> protocol managesieve {
>>   # Specify an alternative address:port the daemon must listen on
>>   # (default: *:2000)
>>    listen = localhost:2000
>>
>>   managesieve_logout_format = bytes ( in=%i : out=%o )
>> }
>>
>> I just did a cut and paste into the conf file.
>>
>> On 4/12/2011 2:14 PM, Timo Sirainen wrote:
>>> On 13.4.2011, at 0.09, Jay Welch wrote:
>>>
>>>> Starting Dovecot Imap: Error: Error in configuration file /etc/dovecot.conf line 676:
>>>> Unknown protocol name (section changed in /etc/dovecot.conf at line 674)
>>> Unfortunately it doesn't say here what the name is.
>>>
>>>> The protocol on line 674 is the Manageseive protocol. Not sure where I am going wrong with this? Any help is much appreciated.
>>> Is it Managesieve or managesieve? The case matters here..
>>>
>>>
>> -- 
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.