[SOLVED] Mail delivery issues for POP/IMAP in latest Grommunio releases

morbificagent

Yes, we have identified another case in the meantime, hang tight.

GeneralProbe @jengelh can you please comment on this?

I don't follow the fourm—there is just too much noise in it.
Current hypothesis is that notifications are getting emitted too early, and midb/imap tries to read a message right then before the message data has made it to the database. All per-mbox operations were previously serialized, but have gained read concurrency in 2.30.

workaround: gromox.cfg: exmdb_force_write_txn=1

@jengelh
yes that helps, thank you!

Here it didn't helped for some reason. Not sure if it's like that because I'm on the dev gromox version at the moment but anyway... Waiting for a general fix which hopefully comes in some days

have you removed your settings?

Yes, i tried it with and without the midb_reload_interval change via config, was rebooting the services and the whole server and decided to wait for the fix ;-)

I tested it again right now, it still works as expected.
Maybe it is stable vs. dev?

OK. My fault. I had entered exmdb_force_write_txn=1 not in the gromox.cfg. Because I was editing the midb.cfg so often I put it there.

Now I'm testing with the right settings at the right place ;-)

Hm... Don't know what I'm doing wrong. It's in the /etc/gromox/gromox.cfg now... Restarted... Doesn't help...

Downgraded gromox to version gromox-2.33.30.g4a6189a... Still with the exmdb_force_write_txn=1... Doesn't help... It stays the same. One or two new mails are visible via imap, and silence after that.

Back to my contab restart imap services every few minutes and waiting for better days.

Many thanks, now it's working here too