You can likely find the culprit user from the logs (ie., the incoming
request - you might also want to set SOGoDebugRequests to YES).
Once the user is found, identify its calendar table{s} from
sogo_folder_info (where c_path2 == username) and then look at the
quick table, c_startdate. A little bit of SQL kungfu won't hurt anyone.
Regards,
--
Ludovic Marcotte
[email protected] :: +1.514.755.3630 :: www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org)
This fixed the problem.
I found one with c_startdate=0!
Thanks,
Allen
--
[email protected]
https://inverse.ca/sogo/lists
