On Thu, Nov 18, 2021 at 10:34:43AM -0500, Antoine Beaupré wrote:
let's put aside what caused that corruption (you should investigate this independently), but it seems that the header-less message triggers a code path meant for the MaxSize placeholders (which you don't use), which unsurprisingly leads to Bad Things Happening (TM). on the upside, the root cause is actually almost right at the crash site, so i don't think i'll need anything more to investigate this. you may even give it a shot yourself - it should be fairly simple.$2 = { data = 0x559f9c642e00 "X-TUID: GovLn9FNVKrB\n[placeholder] \n It is anticipated that there will eventually come a time where the\n third party ecosystem surrounding Python 3 is sufficiently mature\n for this recommendation t"..., len = 1388, date = 0, flags = 0 '\000'}Interestingly, it is *definitely* a corrupt message in the mailspool. It seems to have been truncated somehow:
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
