Hi Bron, Bron Gondwana wrote: > On Wed, Jul 20, 2011 at 10:38:24AM +0200, Luca Ceresoli wrote: >> Bron Gondwana wrote: >>> On Tue, Jul 19, 2011 at 05:16:57PM +0200, Luca Ceresoli wrote: >>>> This assertion comes from the cyrus-imapd code. It was introduced by: >>>> >>>> commit e88cfbdbe442cb10c71ae93a64610d505e57f05d >>>> Author: Bron Gondwana<brong@xxxxxxxxx> >>>> Date: Thu Jun 23 15:27:08 2011 +0200 >>>> >>>> mailbox: ensure appended GUID is not all zeros >>>> >>>> What is the guid, and who should set it? >>> Are you building without openssl? >> I am. >> >>> If it can't create >>> sha1s then that would cause null GUIDs. Hmm. Perhaps >>> this is a bogus commit. Feel free to build without it, >>> it won't break anything. >> Reverted it, and now it's working. Thank you very much! >> >>> It was put in to avoid the case where broken appends >>> were happening due to a bug in another part of the code, >>> but the bug has been fixed separately now. >> Is this going to be fixed in the official version? > Since it's causing problems, perhaps. I'd be interested in > seeing how you're getting zero GUIDs though, since they're > supposed to be the sha1 of the message file being spooled to > disk. Unless you've managed to find the magic message that > creates an all zero sha1! I have no idea. I don't know which piece of software generates a GUID nor how it is used. For your curiosity, I got the reported assertion failure with simple test messages sent via SMTP over TCP to exim. Exim then fed the messages to cyrus-imapd via LMTP over TCP (not lmtpunix). Luca ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
