> On 24 Feb 2017, at 21.28, Mark Moseley wrote:
> Attached. No claims are made on the quality of my code :)
>
With recent dovecots you probably should not use set_host_weight( server, '0’ )
to mark backend
down but instead should use director commands HOST-DOWN and HOST-UP in
combination wi
On 2017-02-27 10:40, Sami Ketola wrote:
On 24 Feb 2017, at 21.28, Mark Moseley wrote:
Attached. No claims are made on the quality of my code :)
With recent dovecots you probably should not use set_host_weight(
server, '0’ ) to mark backend
down but instead should use director commands HOST-D
I upgraded to 2.2.28 and started seeing this logged:
indexer-worker(dluke): Panic: file mailbox-list.c: line 1158
(mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path,
strlen(root_dir)) == 0)
indexer-worker(dluke): Error: Raw backtrace:
2 libdovecot.0.dylib
Hi,
I've updated the archive key for the Xi archive. So, when updating, you
will initially get a key error.
To fix this, either upgrade the debian-dovecot-auto-keyring package
(preferred), or update your key manually from the archive.key located in
the repository root.
Regards,
Stephan.
Hey guys,
overall I have an working dovecot replication between 2 servers running on
amazon cloud. Sadly I had some messages that my server ran out of memory.
After investigating a little bit further I realized that some mails didn't
got replicated, but I'm not sure if this was related to the memo
Glad I poked around on the list today!
Thanks to all for the suggestions about integration with dspam.
I'll definitely have to look into this, as I rely on moving messages
to a specific folder with various IMAP clients to retrain dspam false
positives and negatives.
A quick pair of questions:
Dovecot builds just fine, but fails the tests in src/lib-index.
Note that reverting this commit fixes the issue:
https://github.com/dovecot/core/commit/dfa4b048ec9a174a42d6668e94501db2fb70793a
$ make check
for bin in test-mail-index-map test-mail-index-modseq
test-mail-index-sync-ext test-mail-in
