e modified to "_25".
After explicitely defining '%' as brokenchar, replication from the
command-line now works without problem and the
replication-'failed'-count has returned to 0.
The solution is to define
'mail_location = mdbox:%h/mdbox:BROKENCHAR=\%'
A
Hello,
after upgrading my two replicator-hosts from 2.3.18 to 2.3.19, I observe
'failed replication'-counts with "dovecot replicator status".
The failure seems to be linked to foldernames containing a
'percent'-sign ('%'):
"dovecot replicator status '*' | grep ' y'" now lists some users, wh
oop=0x563d01f73ed0) at
ioloop.c:762
#23 0x7f4e593a6a23 in master_service_run (service=0x563d01f73d30,
callback=) at master-service.c:863
#24 0x563d014e6922 in main (argc=, argv=out>) at main.c:124
--
Dr. Andreas Pip
Hello,
on my dovecot-replicator-backend I see lots of panic-messages "assertion
failed: (ctx->nested_parts_count > 0)", produced from a single user. I
assume that this is correlated with
https://github.com/dovecot/core/commit/a668d767a710ca18ab6e7177d8e8be22a6b024fb
How can I identify the in