EWS hangs while gromox-http stays active

souverain · 2026-05-22T08:31:39+00:00

Hello, We encountered a temporary issue with EWS access on a grommunio/gromox server. The webmail was working, but Apple Mail on macOS could no longer conn...

mwilliams

souverain

I don't know what you expect more than a development build is provided within very few days for verification. expect updates in community/supported very soon.

souverain

mwilliams Yes, I will be patient and wait, but I am hopeful!

souverain

mwilliams In the last 48 hours, I updated to:

gromox-3.7.264.me562232-lp156.55.1
grommunio-web-3.18.11.gd77b7ffbc-lp156.485.1
grommunio-admin-api-1.19.17.m2b84604-lp156.8.1
grommunio-admin-web-5.0.0.37.0d35a44-lp156.176.1

I am now testing whether the EWS / macOS exchangesyncd bandwidth issue is still reproducible with this newer gromox version.

dneuhaeuser

could this parameter perhaps reduce these problems?

/etc/gromox/gromox.cfg
istore_standalone=1

I think there was a discussion about this in the recent webinar.
If I remember correctly, some race condition can lead to these hangups of gromox-http process.
I think the parameter set to 1, splits the tasks in additional processes or threads, so the problem should occur less likely!?

Duese6

I came across @WalterH’s comment regarding the brotli setting in this thread:
https://community.grommunio.com/d/2710-outlookprobleme-nach-update-25052026/36

I tested again with the devel version 3.7.345 and disabled brotli in nginx by adjusting
/usr/share/grommunio-common/nginx/brotli-params.conf (set "brotli off;" for testing).

The memory growth in nginx seems to be gone now.

However, the Apple Mail client still feels somewhat sluggish. Everything else appears to be working normally at first glance.

WalterH

souverain gromox-3.7.264.me562232-lp156.55.1

You need the 3.7.345 from devel. download.
https://download.grommunio.com/devel/openSUSE_Leap_15.6/gromox-3.7.345.xd02abaf-lp156.37.1.x86_64.rpm

souverain

WalterH After installing gromox-3.7.345.xd02abaf-lp156.37.1 and restarting gromox-http, the situation looks much better.

At first, after resuming macOS exchangesyncd and opening Apple Mail, I still saw a few EWS responses around 0.58–1.01 GiB, but I no longer see the previous huge 20–48 GiB responses.

The last large EWS response in the reverse proxy log was at 11:08:01, and after waiting more than 30 minutes, no new huge EWS response appeared.

So, for now, gromox-3.7.345 seems to strongly improve or possibly fix the issue. I will keep monitoring, but the behaviour is clearly much better than before.

thank you very much !

souverain

WalterH hello, as you can see, it still isn't working :-(

souverain

Update: yesterday I thought the situation had improved for a while after testing the newer gromox package, because the traffic seemed to calm down.

However, the issue is still present.

Today, I received new bandwidth alerts again, and the reverse proxy logs still show a very large EWS response from Apple ExchangeSync:

35.89 GiB [14/Jun/2026:08:18:43 +0200] user=user@example.tld status=200 user-agent="AppleExchangeWebServices/835 ExchangeSync/2007"

So even after updating/testing the newer gromox version, the abnormal EWS bandwidth usage is still reproducible.

The traffic still appears to come from:

/EWS/Exchange.asmx
AppleExchangeWebServices/835 ExchangeSync/2007

At this point, the problem is not fully resolved.

BusinessTux

I tested gromox-3.7.345 on my own system and had to revert back to gromox-3.7.256.

No sooner had I installed 3.7.345 than my email client, which connects via IMAP, went offline. The authentication was no longer valid.

After installation I've restartet the following services:
systemctl restart gromox-http gromox-zcore gromox-imap gromox-pop3 gromox-delivery gromox-delivery-queue

Error Message in em Client:
17:05:09.402|018| eM Client 10.4.5326+97a2e75a43 (Windows) 17:05:09.416|03C| Account's UID is 6e372bcf-b1df-4489-8689-8dd943283247 17:05:09.417|03C| AccountBase.ChangeOnlineState : State changed to ONLINE due User 17:05:09.419|03C| Folder /Posteingang [Inbox] is now watched 17:05:09.420|03C| >>> FolderActivated(folder: /Posteingang [Inbox]): 17:05:09.437|03C| >>> Starting account synchronization 17:05:09.513|03C| 01: Connecting to exc.edvnet-uk.com:993 with TLS ... 17:05:30.648|03C| 01: TLS stream established with Protocol: Tls13, NegotiatedCipherSuite: TLS_AES_256_GCM_SHA384, CipherAlgorithm: Aes256, HashAlgorithm: Sha384 17:05:30.676|03C| 01: * OK [CAPABILITY IMAP4rev1 XLIST SPECIAL-USE UNSELECT UIDPLUS IDLE LITERAL+ LITERAL- ENABLE MOVE ESEARCH SEARCHRES LIST-EXTENDED LIST-STATUS STA] Service ready 17:05:30.681|03C| 01: A1 LOGIN "info@edvnet-uk.com" <Parameter wurde aus Datenschutzgründen entfernt.> 17:05:30.715|03C| 01: A1 BAD command not supported or parameter error 17:05:33.819|03C| >>> ConnectionPoolEntry.CloseAsync(): Failed to connect: MailClient.Accounts.AuthenticationAbortedException: Authentifizierung abgebrochen 17:05:33.819|03C| at MailClient.Protocols.Imap.ConnectionPoolEntry.<ConnectInternalAsync>g__ThrowNotOKServerResponseReacquireCredentialsFailed|58_6() 17:05:33.819|03C| at MailClient.Protocols.Imap.ConnectionPoolEntry.ConnectInternalAsync(CancellationToken cancellationToken) 17:05:33.819|03C| 01: A2 LOGOUT 17:05:33.852|03C| 01: * BYE logging out 17:05:33.853|03C| 01: A2 OK LOGOUT completed 17:05:33.853|03C| 01: --- RECEIVE CANCELLED 17:05:33.853|03C| 01: Connection 1 was closed, deliberate = True 17:05:33.854|03C| >>> AUTH ABORTED MailClient.Accounts.AuthenticationAbortedException: Authentifizierung abgebrochen 17:05:33.854|03C| at MailClient.Protocols.Imap.ConnectionPoolEntry.<ConnectInternalAsync>g__ThrowNotOKServerResponseReacquireCredentialsFailed|58_6() 17:05:33.854|03C| at MailClient.Protocols.Imap.ConnectionPoolEntry.ConnectInternalAsync(CancellationToken cancellationToken) 17:05:33.854|03C| at MailClient.Protocols.Imap.ConnectionPoolEntry.ConnectInternalAsync(CancellationToken cancellationToken) 17:05:33.854|03C| at MailClient.Protocols.Imap.ConnectionPool.AcquireConnectionAsync(Folder mailFolder, Boolean noSelect) 17:05:33.854|03C| at MailClient.Protocols.Imap.ConnectionContext.CreateContextAsync(ImapAccount account, Folder folder, Boolean noSelect) 17:05:33.854|03C| at MailClient.Protocols.Imap.ImapMailSynchronizer.<>c__DisplayClass26_0.<<SynchronizeMessagesAsync>g__CreateConnectionContextAsync|0>d.MoveNext() 17:05:33.854|03C| --- End of stack trace from previous location --- 17:05:33.854|03C| at MailClient.Protocols.Imap.ImapMailSynchronizer.SynchronizeMessagesAsync(IItemSynchronizeContext1 synchronizeContext, Folder folder, Boolean fast, CancellationToken cancellationToken)
17:05:33.854|03C| at MailClient.Protocols.Imap.ImapMailSynchronizer.Synchronize(IItemSynchronizeContext1 synchronizeContext, Folder folder, CancellationToken cancellationToken) 17:05:33.854|03C| at MailClient.Protocols.Common.ItemSynchronizer2.<>cDisplayClass37_2.<EnqueueSynchronize>b6(WorkerStatus status, CancellationToken ct)
17:05:33.854|03C| at MailClient.Protocols.Imap.ImapActionCommand.<>cDisplayClass11_0.<.ctor>b0(WorkerStatus ws, CancellationToken ct)
17:05:33.854|03C| at MailClient.Protocols.Imap.ImapActionCommand.ExecuteInternalSync(WorkerStatus status)
17:05:33.854|03C| at MailClient.Protocols.Imap.ImapActionCommand.Execute(WorkerStatus status)
17:05:33.855|03C| >>> Account synchronization finished
17:05:33.855|03C| AccountBase.GoOfflineAsync : State changed to OFFLINE due LoginCanceled
17:05:33.855|03C| AccountBase.GoOfflineAsync : State changed to OFFLINE due BrokenConnection
17:05:33.856|03C| AccountBase.ChangeOnlineState : State changed to OFFLINE due BrokenConnection
17:05:33.858|03C| >>> FolderDeactivated(folder: /Posteingang [Inbox]): `

After reverting to version 3.7.256, the IMAP connection started working again.

WalterH

It's crazy that you use eM Client, a perfect EWS client, as an IMAP client! Thunderbird in IMAP4 mode works perfectly with version 3.7.345.

BusinessTux

WalterH Yes, it is. Because Grommunio only supports S/MIME, not PGP. So I can't send emails with PGP-Part via EWS via Grommunio.

It seems that version 3.7.345 cannot process one of these special characters:
" + ' & ^ #
`

Now that I've changed my password, I can use 3.7.345 as well.

WalterH

By the way, version 3.7.345 implements IMAP4 rev2 (RFC 9051).

WalterH

BusinessTux I guess it is " or ' . I know that the $ and ! characters work in the password.

BusinessTux

WalterH And why this special chars are functionally in gromox-3.7.256?

It's only a hint for the devs. For me I can go forward to test the developer version.

WalterH

souverain Open a support ticket.

souverain

WalterH Do you know that I'm in community mode and therefore can't open a ticket?

Duese6

Since this morning I am seeing some strange gromox-http log messages on a third customer system:

[ews#evt] unordered_map::at: Failed to process notification

I also saw at least one gromox-http crash:

Main process exited, code=dumped, status=11/SEGV

This system is running the latest community version 3.7.266.

WalterH

Duese6 Update to gromox-3.7.345 this version, contains some fixes for this problem.

Duese6

I did some more testing together with my customer.

With 3.7.345, Apple Mail updates can take around 10 to 15 minutes here.
With 3.7.266, the same updates feel almost immediate in comparison.

With 3.7.345, I have not seen any further SEGVs or repeated
[ews#evt] unordered_map::at: Failed to process notification
messages so far.

The only thing I still notice there are startup warnings in gromox-http like:

*** config key "istore_standalone" has no default and was not set either; yielding 0

WalterH

Duese6 *** config key "istore_standalone" has no default and was not set either; yielding 0

Then, set the following parameter: /etc/gromox/gromox.cfg:istore_standalone=0. The message will disappear.

« Previous Page Next Page »