Re: kolab_smtp_access_policy and tables policy_result
Christoph Erhardt <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kroupware |
|---|---|
| Message-ID | <11858537.dzNys4cyA2__4437.47117319635$1529403992$gmane$org@delle> |
Hi Jan, it looks like you have hit an artefact from the upgrade 3.4 -> 16. You probably missed step 6 in the upgrade guide: https://docs.kolab.org/upgrade-guide/kolab-16.html The table schema is declared in Python using the SQLAlchemy mapper; you can find it here: https://git.kolab.org/diffusion/P/browse/master/bin/ kolab_smtp_access_policy.py;5ec8788dd436b342f160ad3dfcca634e68e65112$87 Since the policy_result table contains only temporary data, it should be safe to drop it. The table will then be recreated automatically with the correct schema. Best regards, Christoph P.S.: There is an open bug related to the width of the address strings in the policy_result table (https://git.kolab.org/T2274). The bugfix will probably drop the table every time the pykolab package gets updated. On Tuesday, 19 June 2018 11:49:57 CEST Jan Kowalsky wrote: > Hi all, > > while activating the cache_uri in kolab.conf > > [kolab_smtp_access_policy] > # cache_uri = mysql://kolab:[email protected]/kolab > > I get allways: 451 4.3.5 Server configuration problem; while sending. > > and something like this: > > Jun 19 11:37:35 mx0 postfix/submission/smtpd[17533]: warning: premature > end-of-input on private/submission_policy while reading input attribute name > Jun 19 11:37:35 mx0 postfix/submission/smtpd[17533]: warning: problem > talking to server private/submission_policy: Connection reset by peer > > in mail.log > > I found, I missed the column data in the table policy_result, so I > created it. But the problem continues. But maybe my database structure > is still false. I can't find which setup process is responsible to > create the strukture and neigher an sql file in /usr/share/docs where > other kolab components store their initial sql queries for creating tables. > > Unfortunately there is nothing in pykolab.log even If I start it with > > user=kolab-n argv=/usr/lib/postfix/kolab_smtp_access_policy > --verify-sender --verify-recipient -d 9 > > any idea? > > Kind regards > Jan > _______________________________________________ > users mailing list > [email protected] > https://lists.kolab.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://lists.kolab.org/mailman/listinfo/users
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEwp5/nkNlccrQ2UKH4yzDBS9Gs8IFAlso2sQACgkQ4yzDBS9G s8IwFg/+M8VBEHg/KOA2VBKxB+XQiSdH/sh2UC7/83PIc0dyay2ATkaM+x2LGA7g qQsYm3D4v5zFW1mHEZs4VFH2M7S9egg2uqX5NIlGPLYAm1v2S/uEVND40q9cvp4S 0RyNifXM5cxkLRBzQO1lP/yWr+aAtAqUlHK1vFGFizJbi1MJ/wxf69UVZMTHOrtb PIIi04KySbpYJSTAPkV2aET0qlhLSDxXvSulEJvtRpn9Qaai3XRCQ9L0ung8+KTE puUPNC/jykMl61LnYFbD7nLPEBwLXN5KjvoDmy6GGplCUo5badkmWSFuW1TWG3ZP nrk4NpwyfvKjU/Ny9RC5WUPMbXfNZaW0HgX2OfhUKfeGW4GVa76mhqaTgy/lLBtP vRACneWVFqrJI6KJIOe++3XdsSVdQq/2snswqAaQA2VeninUAzMh3U/WFmzAh5i0 /PXjwRjF7MkBfmGAxSVkDHmS4UOPEzJpykQyICvReTe6Hpt4JB/Hqpdey1HLsl+O SnrCNPmP7gIAyhbWadjemxojx+rI5ZSRrPokc4lcOMt53dcZdeg4oZLPzd8yb593 uKIj3AKIyQJCV85yRPBinbE+KdffYuPV/k5ETZWWjSAwlMcQ5B4nIPZKqjvc37II G+HtZgY4MuKqtbjExJpj1VQWFjhDMiA0IxjQV6E+IabFQj2uvYQ= =Ah84 -----END PGP SIGNATURE-----