OK, I changed the $socket_name to 127.0.01:10024 and I can now connect to the amavisd-new daemon. But when I execute the command:
# amavisd-release spam-2zAVsTgWNieU.gz my logs show the output below (this is with log_level = 5) and appears to be hung. Can anybody explain to me what I am doing wrong here? thanks, mike Dec 6 07:42:09 ren0406 amavis[30448]: loaded base policy bank Dec 6 07:42:09 ren0406 amavis[30448]: lookup_ip_acl (inet_acl): key=" 127.0.0.1" matches "127.0.0.1", result=1 Dec 6 07:42:09 ren0406 amavis[30448]: prolong_timer after new request - timer reset: remaining time = 480 s Dec 6 07:42:09 ren0406 amavis[30448]: process_request: suggested_protocol="" on TCP Dec 6 07:42:09 ren0406 amavis[30448]: (30448-01) SMTP> 220 [127.0.0.1] ESMTP amavisd-new service ready Dec 6 07:42:09 ren0406 amavis[30448]: (30448-01) idle_proc, 4: was busy, 5.7 ms, total idle 0.000 s, busy 0.006 s Dec 6 07:42:09 ren0406 amavis[30448]: (30448-01) idle_proc, 5: was idle, 0.4 ms, total idle 0.000 s, busy 0.006 s Dec 6 07:42:09 ren0406 amavis[30448]: (30448-01) prolong_timer after reading SMTP command: remaining time = 480 s Dec 6 07:42:09 ren0406 amavis[30448]: (30448-01) SMTP< request=release\r\n Dec 6 07:42:09 ren0406 amavis[30448]: (30448-01) SMTP: 500 5.5.2 Error: bad syntax; PENALIZE: request=release\r\n Dec 6 07:42:14 ren0406 amavis[30448]: (30448-01) SMTP> 500 5.5.2 Error: bad syntax Dec 6 07:42:14 ren0406 amavis[30448]: (30448-01) idle_proc, 6: was busy, 5004.1 ms, total idle 0.000 s, busy 5.010 s Dec 6 07:42:14 ren0406 amavis[30448]: (30448-01) idle_proc, 5: was idle, 0.1 ms, total idle 0.001 s, busy 5.010 s Dec 6 07:42:14 ren0406 amavis[30448]: (30448-01) prolong_timer after reading SMTP command: remaining time = 475 s Dec 6 07:42:14 ren0406 amavis[30448]: (30448-01) SMTP< quar_type=Z\r\n Dec 6 07:42:14 ren0406 amavis[30448]: (30448-01) SMTP: 500 5.5.2 Error: bad syntax; PENALIZE: quar_type=Z\r\n Dec 6 07:42:19 ren0406 amavis[30448]: (30448-01) SMTP> 500 5.5.2 Error: bad syntax Dec 6 07:42:19 ren0406 amavis[30448]: (30448-01) idle_proc, 6: was busy, 5003.9 ms, total idle 0.001 s, busy 10.014 s Dec 6 07:42:19 ren0406 amavis[30448]: (30448-01) idle_proc, 5: was idle, 0.1 ms, total idle 0.001 s, busy 10.014 s Dec 6 07:42:19 ren0406 amavis[30448]: (30448-01) prolong_timer after reading SMTP command: remaining time = 470 s Dec 6 07:42:19 ren0406 amavis[30448]: (30448-01) SMTP< mail_id=2zAVsTgWNieU\r\n Dec 6 07:42:19 ren0406 amavis[30448]: (30448-01) SMTP: 500 5.5.2 Error: bad syntax; PENALIZE: mail_id=2zAVsTgWNieU\r\n Dec 6 07:42:24 ren0406 amavis[30448]: (30448-01) SMTP> 500 5.5.2 Error: bad syntax Dec 6 07:42:24 ren0406 amavis[30448]: (30448-01) idle_proc, 6: was busy, 5003.9 ms, total idle 0.001 s, busy 15.018 s Dec 6 07:42:24 ren0406 amavis[30448]: (30448-01) idle_proc, 5: was idle, 0.1 ms, total idle 0.001 s, busy 15.018 s Dec 6 07:42:24 ren0406 amavis[30448]: (30448-01) prolong_timer after reading SMTP command: remaining time = 465 s Dec 6 07:42:24 ren0406 amavis[30448]: (30448-01) SMTP< mail_file= spam-2zAVsTgWNieU.gz\r\n Dec 6 07:42:24 ren0406 amavis[30448]: (30448-01) SMTP: 500 5.5.2 Error: bad syntax; PENALIZE: mail_file=spam-2zAVsTgWNieU.gz\r\n Dec 6 07:42:29 ren0406 amavis[30448]: (30448-01) SMTP> 500 5.5.2 Error: bad syntax Dec 6 07:42:29 ren0406 amavis[30448]: (30448-01) idle_proc, 6: was busy, 5003.9 ms, total idle 0.001 s, busy 20.021 s Dec 6 07:42:29 ren0406 amavis[30448]: (30448-01) idle_proc, 5: was idle, 0.1 ms, total idle 0.001 s, busy 20.021 s Dec 6 07:42:29 ren0406 amavis[30448]: (30448-01) prolong_timer after reading SMTP command: remaining time = 460 s Dec 6 07:42:29 ren0406 amavis[30448]: (30448-01) SMTP< \r\n Dec 6 07:42:29 ren0406 amavis[30448]: (30448-01) SMTP: 500 5.5.2 Error: bad syntax; PENALIZE: \r\n Dec 6 07:42:34 ren0406 amavis[30448]: (30448-01) SMTP> 500 5.5.2 Error: bad syntax Dec 6 07:42:34 ren0406 amavis[30448]: (30448-01) idle_proc, 6: was busy, 5003.9 ms, total idle 0.001 s, busy 25.025 s ---------- Forwarded message ---------- From: Mike Kenny <[EMAIL PROTECTED]> Date: Dec 6, 2007 6:52 AM Subject: amavisd-release and /var/ To: amavis-user@lists.sourceforge.net Hi, we are using amavisd-new-2.3.3-17.2 on SuSE 10. It is configured to use INET, not UNIX, sockets as this was considered to provide more flexibility in a multi-server environment. Now we want to start using amavisd-release to release false positives. This is reporting: Can't connect to UNIX socket /var/amavis/amavisd.sock: No such file or directory at /usr/sbin/amavisd-release line 191. The path referred to above does not appear anywhere in our configuration file, nor should it as we are using INET port 10024 for amavis. What do I need to change to enabel this functionality? Bearing in mind that we will want to execute the release from a remote server. Is this a configuration issue? Or can it be addressed on the command line? (I can find not documentation on amavisd-release and my PERL was rusty 10 years and has not improved) mike ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
