Am 20.06.2013 10:16, schrieb Zoltan Lippai:
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
Try if you can modify your sieve script when connecting with Thunderbird Sieve Extension to your MANAGESIEVE port 4190 or 2000.
Can Afterlogic webmail be configured to use MANAGESIEVE protocol or does it write directly to the filesystem from the webserver user (which might be different from vmail, e.g. apache)
Regards Daniel
Dipl.-Inf. Daniel Parthey System Engineer Metaways Infosystems GmbH Pickhuben 2, D-20457 Hamburg
E-Mail: d.parthey@metaways.de Web: http://www.metaways.de Tel: +49 (0)40 317031-537 Fax: +49 (0)40 317031-937
Metaways Infosystems GmbH - Sitz: D-22967 Tremsbüttel Handelsregister: Amtsgericht Lübeck HRB 4508 AH Geschäftsführung: Hermann Thaele, Lüder-H.Thaele