Hi Thomas,
The posted samples were actually from sogo.conf :-)
I just pasted the much smaller replies in between these requests.
See:
https://pad.ceph.com/p/response1
https://pad.ceph.com/p/response2
https://pad.ceph.com/p/response3
https://pad.ceph.com/p/response4
There has not been a larger reply during the whole sync day than the
samples above.
Do these reveil anything interesting..?
MJ
Op 10/6/20 om 11:46 PM schreef Thomas Führer (t...@aon.at):
Hi, the samples you provided don't really help, they just contain what
is requested by OL. You have to check what is logged in sogo.log
<http://sogo.log> when such requests are processed.
Regards, Thomas
---- mj schrieb ----
Op 10/6/20 om 8:59 PM schreef mj (li...@merit.unu.edu):
> I am currently reading this
>
(https://techcommunity.microsoft.com/t5/exchange-team-blog/under-the-hood-exchange-activesync-mailbox-log-analysis/ba-p/591224)
> to hopefully better understand what I am looking at.
On that page, it says:
"Typically you will see items being added to the device in the Sync
response. You can see detailed information including the sender and
subject if verbose logging has been enabled on the CAS servers."
It seems that compared to microsoft, SOGo's SOGoEASDebugEnabled mode is
very verbose, but still not verbose enough.
It would make our lives so much easier, of SOGo would also log things
like sender and subject...
MJ
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
