The previous behaviour relied on managesieve copying over the .dovecot.sieve file into the user's directory. I found this to be particularly fragile. For instance, re-deploying roundcube without dovecot could overwrite the .dovecot.sieve symlink and break managesieve. A better approach is to use the global sieve configuration that roundcube provides and not mess with dovecot's files directly.
|
|
||
29 |
|
29 |
|
30 |
|
30 |
|
31 |
|
31 |
|
32 |
|
|
|
33 |
|
|
|
34 |
|
|
|
35 |
|
|
|
|
||
29 |
|
29 |
|
30 |
|
30 |
|
31 |
|
31 |
|
32 |
|
|
|
|
32 |
|
|
33 |
|
33 |
|
34 |
|
34 |
|
35 |
|
|
|
|
35 |
|
|
36 |
|
36 |
|
37 |
|
37 |
|
38 |
|
38 |
|
|
|
||
17 |
|
17 |
|
18 |
|
18 |
|
19 |
|
19 |
|
|
20 |
|
|
|
21 |
|
|
|
22 |
|
|
20 |
|
23 |
|
21 |
|
24 |
|
22 |
|
25 |
|