>>>>>> On 05/31/12 11:06, Bulent Malik wrote: >>>>>> On 28/05/2012 22:03, Bulent Malik wrote: >>>>>> There is an info in UPGRADING; >>>>>> What does r348 mean ? my version v2.0.11a-debian . In that case, >>>>>> what is my revision ? >>>>> Unfortunately we can only support packages distributed on the >>>>>official >>>> site. If you installed policyd another way it's best to contact the >>>> packager/s and find out how to upgrade. >>>> >>>>> You are more than welcome to download the tar.gz from >>>>http://policyd.org/content/download and install it by following the >>>>instructions in the INSTALL file. From there we can identify the >>>> problem and resolve it.>Again - a detailed report on what you're >>>>experiencing will help us better understand what's going on. >>>> >>>>> - Robert >>>> What is revision ( r ) for Cluebringer-2.0.11 ? >>>> What does r348 mean ? >> r348 is the old subversion revision numbers. This is generally used for the >> development snapshot/versions of Policyd/Cluebringer. >>> I'm pretty sure you can ignore any upgrade statements that include rXXX >>> numbers. Unless you're upgrading from a very very old development snapshot. >> Ok then in the latest snapshot, there is an upgrading file >> >> UPDATE quotas_limits, quotas_tracking >> SET quotas_limits.CounterLimit = >> ceil(quotas_limits.CounterLimit / 1024), >> quotas_tracking.Counter = ceil(quotas_tracking.Counter / >> 1024) >> WHERE quotas_tracking.QuotasLimitsID = quotas_limits.ID >> AND quotas_limits.Type = "MessageCumulativeSize"; >> >> UPDATE session_tracking SET Size = ceil(Size / 1024); I am execute >> above . >> >> But my cluebringer version didn't update is still 2.0.11. am I to replace >> some files? >> Actually, is there a patch for upgrade ? >> >> >> I restarted the services (cluebringer and postfix ) but there is no change >> the situation. >> For exceeded limit mails if I select defer postfix rejects but i select hold >> postfix holds ( OK ) or i select discard postfix discard ( OK ). >> Namely the defer feature doesn't work. >> >Yes. You need to uninstall the previous version of Policyd and install the new >version by following the instructions in the INSTALL file. >The verdicts are literally passed through from the modules directly to >Policyd, so if you are experiencing this you're more than likely going to have >to log an issue on the devlabs site with the details I described in the >mail >below. >I've spun the attached patch for you, it will output where the verdict is >being set and what the modules return status is. This may give a bit of >indication where the issue lies. Pleae apply the patch before logging the >>issue below. >> For us to investigate this we need to reproduce it. With the sheer >> number of posts in the past week, this is going to take some time. We >> tend to prioritize issues which affect multiple users higher than >> those that affect fewer users. >> If you don't mind assisting us here, it would greatly speed things up. >> I would suggest if you can prove with logs that policyd is returning >> the incorrect verdict back to Postfix, is to maybe log all the steps >> you use to reproduce this as a issue on the devlabs site.
>> It makes it much easier and faster if we have a sql db dump of the >> policyd db you're using to test with, a copy of your Policyd config >> file, a copy of your Postfix config file (master & main). Details like >> which OS you're using is also helpful, which version of Policyd >> (stated in the full logs above when policyd starts). Then the logs >> showing the incorrect behavior with full debugging everywhere turned on. Ok i am following the intall file in the latest policyd source directory. When i execute "mysql -uroot -ppasswd cluebringer < policyd.mysql" i get an error like below; You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=InnoDB CHARACTER SET latin1 COLLATE latin1_bin' at line 12 _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
