On Tuesday 24 March 2009, Nigel Kukard wrote: > > I installed vanilla amavisd from amavisd-new-2.6.1.tar.gz and still get > > the same error: > > > > Mar 23 14:09:51 smailx amavis[30222]: (30222-02) > > (!)policyd/process_policy: Failed to parse in queue id from received line > > '1' > > > > I enabled --debug on cbpolicyd and ran it in the foreground: > > > > [2009/03/23-14:09:49 - 9423] [CORE] INFO: Starting "1" children > > [2009/03/23-14:09:49 - 9434] [CORE] INFO: 2009/03/23-14:09:49 CONNECT TCP > > Peer: "127.0.0.1:50715" Local: "127.0.0.1:10031" [2009/03/23-14:09:49 - > > 12261] [CORE] DEBUG: Child Preforked (12261) [2009/03/23-14:09:49 - > > 12261] [CBPOLICYD] DEBUG: Starting up caching engine [2009/03/23-14:09:49 > > - 9434] [POLICIES] INFO: [ID:1/Name:Default]: Source matching result: > > matched=1 [2009/03/23-14:09:49 - 9434] [POLICIES] INFO: > > [ID:2/Name:Default Outbound]: Source matching result: matched=1 > > [2009/03/23-14:09:49 - 9434] [POLICIES] INFO: [ID:3/Name:Default > > Inbound]: Source matching result: matched=0 [2009/03/23-14:09:49 - 9434] > > [POLICIES] INFO: [ID:4/Name:Default Internal]: Source matching result: > > matched=0 [2009/03/23-14:09:49 - 9434] [POLICIES] INFO: > > [ID:5/Name:kosmosisland dot com]: Source matching result: matched=1 > > [2009/03/23-14:09:49 - 9434] [POLICIES] DEBUG: [ID:5/Name:kosmosisland > > dot com]=>(group:domain_kosmosisland_com): Destination group result: > > matched=1 [2009/03/23-14:09:50 - 9437] [CORE] INFO: 2009/03/23-14:09:50 > > CONNECT TCP Peer: "127.0.0.1:50716" Local: "127.0.0.1:10031" > > [2009/03/23-14:10:30 - 9423] [CORE] INFO: Killing "1" children > > [2009/03/23-14:10:30 - 9436] [CBPOLICYD] DEBUG: Shutting down caching > > engine (9436) > > > > My cluebringer.conf is in an earlier post in this thread. > > Try the attached patch.
Thank you, Nigel. It doesn't look like the error changed: Mar 26 08:55:47 smailx amavis[32061]: (32061-01) (!)policyd/process_policy: Failed to parse in queue id from received line '1' The patch was successful and I opened it with vi to see that it was. I rechecked my installation and rebuilt my database from the install scripts and reconfigured policyd just to be sure I did not miss something. Regards, David Koski [email protected] _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
