Guy wrote: > UPDATE: > > 2009/3/31 Guy <[email protected]>: > >> Hi Nigel, >> >> 2009/3/30 Nigel Kukard <[email protected]>: >> >>> Could you enable all amavisd debugging, it should spit out alot more >>> policyd info then, lets look at that and take it from there. >>> >> I'm seeing two things at the moment: >> Mar 31 11:34:40 aardwolf amavis[28109]: (28109-08) >> policyd/process_policy: Starting >> Mar 31 11:34:40 aardwolf amavis[28109]: (28109-08) >> policyd/process_policy: Getting session data from queue ID >> '92EED33006A' >> Mar 31 11:34:40 aardwolf amavis[28109]: (28109-08) [TRACKING] DEBUG: >> Retreiving session data for triplet: >> 92EED33006A/131.111.8.130/[email protected] >> Mar 31 11:34:40 aardwolf amavis[28109]: (28109-08) (!!)[TRACKING] >> ERROR: No session data >> Mar 31 11:34:40 aardwolf amavis[28109]: (28109-08) >> (!)policyd/process_policy: No session data found >> >> And: >> Mar 31 11:44:17 aardwolf amavis[28679]: (28679-15) >> policyd/process_policy: Starting >> Mar 31 11:44:17 aardwolf amavis[28679]: (28679-15) >> policyd/process_policy: Getting session data from queue ID >> 'D4E1D3301AA' >> Mar 31 11:44:17 aardwolf amavis[28679]: (28679-15) [TRACKING] DEBUG: >> Retreiving session data for triplet: >> D4E1D3301AA/62.128.157.69/[email protected] >> Mar 31 11:44:17 aardwolf amavis[28679]: (28679-15) [POLICIES] INFO: >> [ID:1/Name:Default]: Source matching result: matched=1 >> Mar 31 11:44:17 aardwolf amavis[28679]: (28679-15) (!)custom >> process_policy error: Can't use string ("62.128.157.69") as a HASH ref >> while "strict refs" in use at /usr/lib/policyd-2.0/cbp/policies.pm >> line 314, <GEN24> line 8191. >> > > I had a stupid. One of my policies was set to the incorrect source and > destination. Once that was corrected the second > error stopped coming through. The first one about "No session data > found" is still occurring but there is data in the session_tracking > table. > This would happen if you are permitting traffic before the first policyd check in RCPT stage. Please paste your postfix restrictions.
Regards Nigel
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
