As title suggests, when opening via pop3 an account with thunderbird, the latter complains about not being able to open a message.
When checking the server logs, I get the following from midb:
mai 06 19:48:42 email midb[1635]: E-2394: read_message(/var/lib/gromox/user/domain.tld./mailbox_name,2134742) EXRPC failed
mai 06 19:48:42 email midb[1635]: E-2394: read_message(/var/lib/gromox/user/domain.tld./mailbox_name,2134741) EXRPC failed
mai 06 19:48:42 email midb[1635]: E-2394: read_message(/var/lib/gromox/user/domain.tld./mailbox_name,2134740) EXRPC failed
I also get the following message from gromox-pop3:
mai 02 14:46:26 email pop3[1636]: rhost=[::ffff:192.168.201.1]:37154 user=mailbox_name@domain.tld failed RW I/O with midb server
mai 03 14:08:48 email pop3[1636]: E-1469: imapfile_read /var/lib/gromox/user/domain.tld./mailbox_name/eml/1746261985.22279.email.server.tld failed
mai 03 14:12:53 email pop3[1636]: E-1469: imapfile_read /var/lib/gromox/user/domain.tld./mailbox_name/eml/1746261985.22279.email.server.tld failed
[...]
The specified file does indeed not exist.
I've run gromox-mbck and sqlite3 checks against exchange.sqlite3 and midb.sqlite3 without any troubles found.
How can I "repair" the pop3 database ?
I do have that same file in the var/lib/gromox/user/domain.tld./mailbox_name/ext
folder, but of course it's only a json file without the actual mail content.
Any ideas perhaps ?