Hi!
It happens with any folder… in fact Trash is not the folder we would announce
in special-use as Trash… it’s just a normal folder really here…. It’s a
generally happening thing with rename of folders inside the own hierarchy
inside the own user… (don’t really know if a rename mailbox for
Hi,
I'm curious if this only happens for rename to trash, or for all renames
of subscribed folders. IMHO it makes no sense to automatically subscribe
to a folder in the trash. So perhaps the bug isn't in the replication
code but rather in the handling of rename to trash?
Am 10.07.19 um 11:11
Good morning,
In previous thread (with the title slightly incorrect) I talk about an issue
suffered some day with Sieve script and folder subscriptions. The Sieve part,
was related to the migration, so for the moment let’s forget about it (for me
at least) as it has never reproduced again
It would be better to just talk daemons IMHO…. That should work… but sometimes…
perhaps another things could be implied… so… the most clear way, should be to
just put as a normal client with a expect script for instance all the source
scripts to Cyrus… but using sieveshell… and not using files
The subject of this email is not properly set… it should be . Issues in
replication with folder subscription and Sieve
As I think I discovered something I reopen a new thread with the title properly
Egoitz Aurrekoetxea
Dpto. de sistemas
944 209 470
Parque Tecnológico. Edificio 103
48170
Le 09/07/2019 à 22:49:01+0200, Egoitz Aurrekoetxea a écrit
> By the way, for your case I would recommend doing a script that does a get
> from
> dovecot and a put to Cyrus instead of copying Sieve files directly… it’s a
> much
> more cleaner way…
Yes, it is what I did, before I try de sync I
Le 09/07/2019 à 22:44:19+0200, Egoitz Aurrekoetxea a écrit
Hi,
>
> If instead of -A you used -u for each of your users did it worked? Or did it
If I remember correctly (but I not sure) this is how I find out the
problem.
Try time -A, notice it crash,
so try -u first_user, notice it work
