Re: [Dovecot] Sieve file permission problem

Thanks for the answer, I'm not sure what you mean by the additional permission details. Here is a quick example: /var/mail/domainname.hu/zolcsi chmod: 700, owner: vmail:mail After I set the initial sieve filters, the following file and directory gets created: /var/mail/domainname.hu/zolcsi/sieve (directory) chmod: 700, owner: vmail:mail /var/mail/domainname.hu/zolcsi/.dovecot.sieve (symlink to the sieve/sieve.sieve file) chmod: 600, owner: vmail:mail

After these two are created then the webmail can't modify them unless I delete the files manually.

I looked in the mail.log and mail.err files, but couldn't find anything related to this. Perhaps if I set the log level to a higher value?

Or is it possible to connect via telnet to port 2000 and issue some commands to see the actual answers of the ManageSieve server?

Best regards, Zoltan

On 2013. June 19., Wednesday at 18:40, Daniel Parthey wrote:

Please provide permission details of the affected directories and files and possibly error messages from dovecot logfile.

Regards Daniel

Zoltan Lippai schrieb:

...

Hi folks,

I am using dovecot 2.1.7 with the ManageSieve plugin which works great. Recently I set up Afterlogic webmail on my server (the community version) and it has a nice UI to manage the sieve settings. It uses port 2000 to communicate with dovecot via the ManageSieve plugin. Also, dovecot uses Maildirs to store the messages.

The problem is that the permissions on the files that store the sieve rules are to strict. I am talking about the "sieve" directory and the .dovecot.sieve file. The sieve folder has a chmod 700 and the .dovecot.sieve is chmod 600. Both are owned by vmail:mail

If I delete these two items, then the rules can be saved via the web interface. Then these files are created but for some reason the ManageSieve plugin can't modify them.

Here is the output of dovecot -n: http://pastebin.com/4eqyBKCA

Can you help me out on this?

Thanks a lot! Zoltan