Als Weitern Schritt habe ich in der EWS Konfig die Debug-Logs aktiviert und diese mit den Konsolen-Logs aus Thunderbird Claude zum Analysieren gegeben.
Ja, ich bin mit dessen Bewusst, dass die Gefahr besteht das ich euch mit KI Slop belästige. Allerdings befinde ich mich mit einem Problem auf einer Stufe die jenseits meiner Fachkompetenz liegt. Daher musste ich KI zu Rate ziehen.
Jedenfalls hat mir Claude angegeben das 2 Bugs vorhanden sind - einer im Exquilla Add-on der Andere in der EWS-Integration von Grommunio. Ich habe Claude um einen Bug Report gebeten.
Kann mir jemand von euch, welche das nötige Fachwissen hat, mir Bestätigen das dies tatsächlich ein Fehlverhalten von Grommunio ist?
Ich danke euch für eure Hilfe!
EWS: FindFolder response missing RootFolder element when folder has no subfolders
Summary
When a FindFolder request with Traversal="Deep" is issued against a folder that has no subfolders (e.g. sentitems), Gromox returns a successful response but omits the RootFolder element entirely. According to the EWS specification, a real Exchange server always includes a RootFolder element, even when the result set is empty. This causes EWS clients such as Exquilla to fail when processing the response.
Environment
Gromox version: 3.7.129.me37a10c-1+7.1
Client: Mozilla Thunderbird 150.0.2 with Exquilla plugin
Triggered by: CreateItem MessageDisposition="SaveOnly" followed by FindFolder on sentitems
Steps to Reproduce
Configure Thunderbird with Exquilla against a Gromox server
Send an email
Exquilla issues CreateItem MessageDisposition="SaveOnly" to save a copy to sentitems — this succeeds
Exquilla then issues FindFolder Traversal="Deep" on sentitems to discover subfolders
Observe the Gromox response
Actual Gromox Response
xml<m:FindFolderResponseMessage ResponseClass="Success">
<m:ResponseCode>NoError</m:ResponseCode>
<!-- RootFolder element is completely absent -->
</m:FindFolderResponseMessage>
Expected Response (as returned by real Exchange)
xml<m:FindFolderResponseMessage ResponseClass="Success">
<m:ResponseCode>NoError</m:ResponseCode>
<m:RootFolder IndexedPagingOffset="0"
IncludesLastItemInRange="true"
TotalItemsInView="0">
<t:Folders/>
</m:RootFolder>
</m:FindFolderResponseMessage>
Impact
EWS clients that rely on the RootFolder element being present (as per the Exchange specification) will fail when processing this response. Exquilla throws the following error:
Error in updateFolderWithListener (Failed to discover subfolders)
Error in copyFileMessage: [Exception... "Failed to updated destination folder on copy"
nsresult: "0x80004005 (NS_ERROR_FAILURE)"]
Additional Notes
The FindFolder call itself is not wrong — sentitems has no subfolders, so an empty result is correct
The issue is solely the missing RootFolder wrapper element, which violates the EWS specification
The same behaviour can likely be reproduced on any folder with no subfolders
A separate but related issue exists in the native Thunderbird EWS integration: CreateItem SendOnly does not return an ItemId and no streaming notification is fired for the saved copy, meaning sent messages never appear in Thunderbird's local folder view
