I've seen posts and even bug reports (http://www.sogo.nu/bugs/view.php?id=27) about database errors resulting from overly large calendar or addressbook entries. In my case, this is typically caused by someone sending an invitation with a ridiculously large number of invitees, but sometimes, it might be just a large attached information section that causes the entry to exceed the allowed 255 characters.
While I do understand the reasoning behind letting the database provide the rejection error (as input could come from other non-SOGo clients--in my case, Lightning), the error is typically sufficiently cryptic such that it is many times difficult for the user to locate the offending entry. The error message that appears in Lightning is almost useless, and the SOGo logs are only a little better typically referencing the numerical version of the event (like 040000008200E00074C5B7101A82E0080000000090374827306FCD01000000000000000010000000A1C805A831C915419EA0337C4662D090.ics). This would be OK, it you could search for the event in the db, but, of course, since it can't be saved, it isn't there. I'm not sure if the database would even know more about the event, but is there a way it could tell us more such that the offending event can be flagged and deleted? Also, as much as I hate to accommodate software that allows the poor practices of users in the first place, given that SOGo needs to be able to accept foreign generated appointments, should this 255 character field be expanded? Steve -- [email protected] https://inverse.ca/sogo/lists
