Unfortunately, with all of this settings, I see this warnings: [Warning] Aborted connection some days more and some days less.
[SOLVED] Mail delivery issues for POP/IMAP in latest Grommunio releases
gromox-2.31-40-gc6173b2c3
Does anyone had success with the update?
On my first try, it did not help, so I reverted back to stable.
- Edited
So yes, with the above mysql tuning, errors still come, just later.
What bugs me is that I also get mysql connection errors from chat, which makes me think that all connections must be exhausted at one point:
2024-09-02 15:17:30 1909819 [Warning] Aborted connection 1909819 to db: 'grommunio' user: 'grommunio' host: 'localhost' (Got an error reading communication packets)
2024-09-02 15:17:30 1909815 [Warning] Aborted connection 1909815 to db: 'grochat' user: 'grochat' host: 'localhost' (Got an error reading communication packets)
2024-09-02 15:17:30 1909805 [Warning] Aborted connection 1909805 to db: 'grochat' user: 'grochat' host: 'localhost' (Got an error reading communication packets)I've just installed @jengelh 's suggested gromox-2.31.40.gc6173b2-lp155.17.1.x86_64 (along with all other current git updaes) on my personal email server and removed the mysql tuning in order to have proper environment.
Rebooted, and now wait to see.
I'll report later this day if I still have any mysql timeouts.
- Edited
So it's been 7 hours, no mysql errors shown on my updated server.
Still, I get some sporadic delayed POP/IMAP mail. I'm quite sorry that the mysql stuff didn't resolve all the issues, but it's still better.
When POP/IMAP delays happens, I sometimes get the following error, perhaps this is related:
sept. 02 22:17:52 email gromox-midb[1505]: > sqlite3_exec(UPDATE folders SET sort_field=0 WHERE folder_id=13) inside a readonly TXN
sept. 02 22:17:52 email gromox-midb[1505]: > sqlite3_exec(DELETE FROM messages WHERE message_id=218710) inside a readonly TXN
sept. 02 22:17:47 email postfix/qmgr[1866]: A951E2F4A8: removed
sept. 02 22:17:47 email postfix/qmgr[1866]: A65212F4A7: removedIt looks like the first message always is delivered instantly, and later messages get delayed for POP/IMAP clients.
Anyway I still need the midb_reload_interval=3minutes setting in hope to see my mails appear at least every 3 minutes.
As a quick side question, does gromox trigger midb when a mail is received ?
Is there a way to debug log this ? I've tried to set midb_log_level=6 in /etc/gromox/midb.cfg but it doesn't add any more info to the logs.
ozy Still, I get some sporadic delayed POP/IMAP mail. I'm quite sorry that the mysql stuff didn't resolve all the issues, but it's still better.
YES, IT DIDN'T! 
ozy As a quick side question, does gromox trigger midb when a mail is received ?
Thats the actual problem i'm guessing but haven't got any response in my ticket for it...
And that other thread you already know about 
.
- Edited
Thats the actual problem i'm guessing but haven't got any response in my ticket for it...
And that other thread you already know about
Hmmm... I'm a Grommunio "peasant", I have two community instances, so no access to any fancy tickets or service 
Would appreciate if you keep me updated. This is bugging me because although I use MAPI & ActiveSync for my devices, I do have a pop retriever which usually is much delayed.
I noticed this problem only recently (didn't have any use for POP/IMAP prior to a few weeks). For how many time did you notice the problem ? Was it always there or has there been a working previous release ?
Thanks ^^
ozy I noticed this problem only recently (didn't have any use for POP/IMAP prior to a few weeks). For how many time did you notice the problem ? Was it always there or has there been a working previous release ?
I first noticed July slightly but didn't even realize how serious the difference is for an IMAP user at first because i only used my client and only occasionally looked into the web-app.
And no it wasn't always there..
I had a smooth ride since ~spring '22 with Claws-Mail and only had a little issue here and there which wasn't serious and was fixed pretty quick IIRC.
I currently only use it to move server mails in a subfolder because that isn't fun in the webapp with like ~200-1000 mails and as an RSS-Reader
I hope someone _/me *squints* at @jengelh _ will get a handle on it rather sooner than later as e.g Ticketsystems and alike are also affected. Some even could use EWS but the main focus for it on this point was Outlook for MAC and other EWS Clients aren't reallly working. (At least i haven't seen one..). Enough of it..
Fingers crossed, most people should be back from the summer vacation so we can only hope.
@crpb I created a ticket a while ago and linked some threads from the forum into it.
But the response time is quite slow.
8 days later
Nothing new on the topic?
A customer using IMAP told me: Last weekend's "supported update" fixed this.
But, big question, which code change in grommunio introduced this issue?
well, it is not fixed on my side.
Rocky Linux 9 - Aarch64 - up to date supported release
Same here, issue still persists
Debian 12 - Supported Repo
gromox 2.30.85.4d271dc-1+2.1 amd64
- Edited
- Edited
I updated to the latest Cummunity Edition today. Now I also have the problem with the massively delayed IMAP synchronization. :-(
EDIT:
Grommunio appliance (SuSE iso) on Proxmox/qemu vm with 16G RAM
gromox 2.32.0.ge7685dd-lp155.12.1
grommunio-imapsync 2.264-lp155.1.1