Open brong opened 4 years ago
reconstruct already has this:
https://github.com/cyrusimap/cyrus-imapd/blob/c1e0fb0cb7f2c30543f15ae66f9c6ce643bfed74/imap/reconstruct.c#L471-L489
Should we be chucking one of the "*ERROR:" prefixes onto those messages, so our log monitoring notices them? Which one? What about stderr output?
Replication has this:
https://github.com/cyrusimap/cyrus-imapd/blob/c1e0fb0cb7f2c30543f15ae66f9c6ce643bfed74/imap/sync_support.c#L2758-L2767
and this (which is the opposite of a clash: a uniqueid that changed):
https://github.com/cyrusimap/cyrus-imapd/blob/c1e0fb0cb7f2c30543f15ae66f9c6ce643bfed74/imap/sync_support.c#L2799-L2813
reconstruct already has this:
https://github.com/cyrusimap/cyrus-imapd/blob/c1e0fb0cb7f2c30543f15ae66f9c6ce643bfed74/imap/reconstruct.c#L471-L489
Should we be chucking one of the "*ERROR:" prefixes onto those messages, so our log monitoring notices them? Which one? What about stderr output?
Replication has this:
https://github.com/cyrusimap/cyrus-imapd/blob/c1e0fb0cb7f2c30543f15ae66f9c6ce643bfed74/imap/sync_support.c#L2758-L2767
and this (which is the opposite of a clash: a uniqueid that changed):
https://github.com/cyrusimap/cyrus-imapd/blob/c1e0fb0cb7f2c30543f15ae66f9c6ce643bfed74/imap/sync_support.c#L2799-L2813