Re: pykolab.log is empty
Eric Chaput <[email protected]> Fri, 16 Jun 2023 09:05:16 -0400
| Newsgroups | gmane.comp.kde.devel.kroupware |
|---|---|
| Message-ID | <e10c36ab-e64e-077e-1c85-4b153c67c65d__20338.9775984519$1686920796$gmane$org@ftd.idms.com> |
Hi Johannes, Some mysql table fields were too short and causing deliverability issues with long email addresses. I've had to modify the DB schema a bit: alter table policy_result modify sender varchar(255); alter table policy_result modify recipient varchar(255); Alternatively: https://git.kolab.org/rP6107a8a7bfba971e4abcbd551b3d689250d91ac3 Regarding the pykolab.log issue, I have no clue, still not fixed Thanks Eric On 2023-06-16 08:14, Johannes Ranke wrote: > Dear Kolab users, > > I have the same problem described below, also on a stretch system that was > previously running buster. > > Any hints would be appreciated. > > Johannes > > Am Dienstag, 6. Juni 2023, 20:44:05 CEST schrieb Eric Chaput: >> Hi Everyone, >> >> after an upgrade from Debian Stretch to Buster I've been troubleshooting >> issues with kolab_smtp_access_policy.py and when trying to find the logs >> for it, I noticed that my pykolab.log is empty. What's strange is that >> the timestamp / last modified time on the file changes from time to time >> but it stays empty. >> >> Any idea what could be wrong with the kolab logging? >> >> Thanks >> >> Eric >> _______________________________________________ >> users mailing list >> [email protected] >> https://lists.kolab.org/mailman/listinfo/users > _______________________________________________ > users mailing list > [email protected] > https://lists.kolab.org/mailman/listinfo/users