On 06/11/2013 20:03, Steffen Wegner wrote: > Hi Nigel, > the logs regarding amavis from mail.log when sending an email are as follow: > > -------------------------------/var/log/mail.log------------------------------------------------- > Nov 6 20:48:31 server1 amavis[2312]: No decoder for .zoo tried: zoo > Nov 6 20:48:31 server1 amavis[2312]: No decoder for .lha > Nov 6 20:48:31 server1 amavis[2312]: No decoder for .doc tried: ripole > Nov 6 20:48:31 server1 amavis[2312]: Found decoder for .cab at /usr/bin/cabextract > Nov 6 20:48:31 server1 amavis[2312]: No decoder for .tnef > Nov 6 20:48:31 server1 amavis[2312]: Internal decoder for .tnef > Nov 6 20:48:31 server1 amavis[2312]: Found decoder for .exe at /usr/bin/arj > Nov 6 20:48:31 server1 amavis[2312]: Using primary internal av scanner code for ClamAV-clamd > Nov 6 20:48:31 server1 amavis[2312]: Found secondary av scanner ClamAV-clamscan at /usr/bin/clamscan > Nov 6 20:48:31 server1 amavis[2312]: Creating db in /var/lib/amavis/db/; BerkeleyDB 0.49, libdb 5.1 > Nov 6 20:48:43 server1 amavis[2316]: (02316-01) (!)policyd/process_policy: Failed to parse in queue id from received line '' > Nov 6 20:48:45 server1 amavis[2316]: (02316-01) Passed CLEAN, [195.30.107.16] <[email protected]> -> <[email protected]>, Message-ID: <[email protected]>, mail_id: cWESOPxci3le, Hits: -0.002, size: 380, queued_as: 745DE340077, 1978 ms > ------------------------------------------------------------------------------------------------- > > The Problem seems to be here: > Nov 6 20:48:43 server1 amavis[2316]: (02316-01) (!)policyd/process_policy: Failed to parse in queue id from received line '' > > In 'amavisd-policyd.pm' I do have the following database configuration: > > -------------------amavisd-policyd.pm------------------------------ > ... > my $DB_dsn = "DBI:mysql:database=policyd;host=localhost"; > my $DB_user = "amavisuser"; > my $DB_pass = "**********"; > my $DB_prefix = ""; > ... > ----------------------------------------------------------------- > > I do not now what $DB_prefix is. So I left it empty. Could that cause the problem?
The policyd debug log shows you what policyd is doing, plus the version you are running and the policy matching taking place. It is impossible to speculate what the issue could be. See http://wiki.policyd.org/#troubleshooting , section "how to ask for help". > Please enable full debugging in policyd and check over the logs for the > BCC verdict being sent. -- -N
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
