On 15.02.2020 14:45, Tobias Kirchhofer wrote:
> On 15 Feb 2020, at 12:27, Armin Schindler wrote:
> 
>     On 15.02.2020 12:16, Tobias Kirchhofer wrote:
>     ...
> 
>         the sieve part seems to be very tricky.
>         My test is now working with a public folder and I have a
>         "sieve_before" script in place which works for rules of the
>         private namespace.
> 
>         But when the rule shall "fileinto" a public folder, the mail isn't
>         filtered (moved) and syslog says
>         dovecot: lmtp(.): Error ... sieve...: Mailbox doesn't exist.
> 
>         After some tests I found out it always looks in the private (or
>         shared)
>         namespace for that specfied folder.
>         Do I miss a config option to let dovecot sieve "fileinto" a public
>         namespace folder?
>         I use dovecot version 2.2.13.
> 
>         We „fileinto“ in this manner :
> 
>         |fileinto „Namespace/folder“; |
> 
>     This is what is not working for me.
> 
>     Your procedure below is good and maybe I will use parts of it, thank
>     you. But this part is working for already. The incoming mail
>     is sent to dovecot (postfix virtual alias working) and the
>     match in sieve script is correct too.
>     The problem is that dovecot (sieve) refuses to
>     fileinto "Namespace/folder"
>     because it seems it wants to store the mail
>     in private namespace with "folder1/folder2" instead.
>     The first part of the fileinto path isn't used as
>     namespace name.
>     Is there a config option for this behaviour?
...

> Are you sure the ACL are correct? Can be that the error message „Mailbox
> doesn't exist“ is misleading and the permissions are not correct.

You are correct. The message is misleading. And even worse, if I used
  fileinto :create "...."
the folder was created in private namespace then.

The shared and public folders need of course the
 anyone post
right to let fileinto work.

Now it works. Thank you Tobias.

Armin

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to