search for: mbox_storage_nam

...at a backend with MAIL_STORAGE_CLASS_FLAG_OPEN_STREAMS unset and MAIL_STORAGE_CLASS_FLAG_BINARY_DATA set is expected by the plugin. Technically, this would thus exclude the mbox backend, since its flag configuration seems to be exactly the opposite: struct mail_storage mbox_storage = { .name = MBOX_STORAGE_NAME, .class_flags = MAIL_STORAGE_CLASS_FLAG_MAILBOX_IS_FILE | MAIL_STORAGE_CLASS_FLAG_OPEN_STREAMS | MAIL_STORAGE_CLASS_FLAG_HAVE_MAIL_GUIDS, [...] Is this a correct interpretation? If yes, what is the rationale? I couldn't find any info related to such a limitation in the docs; the RE...