Mark, Following is the telnet log with my custom content filter:
$ telnet 10.194.99.63 10030 Trying 10.194.99.63... Connected to ip-10-194-99-63.ec2.internal (10.194.99.63). Escape character is '^]'. 220 Hello HELO 250 Custom Java SMTP Server MAIL FROM:ashiiish.sha...@gmail.com 250 Ok RCPT TO: cp_u...@dev1.cpgtest.ostinet.net 250 OK DATA 354 send data now Testing from local . 250 message received Connection closed by foreign host. My custom content filter is able to support multiple transactions in a simple SMTP session. Also I changed the $notify_method and redirected it to the postfix, but I don't think it would have any impact on this whole setup. Still facing the same problem. Please help. My amavisd information is: Product name: amavisd-new Version: 2.6.4 Thanks in advance Ashish Sharma -----Original Message----- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Mark Martinec Sent: Thursday, April 08, 2010 10:04 PM To: postfix-users@postfix.org Subject: Re: amavis Delivery status notification(DSN) failing Ashish, > I have a postfix mail server over which I have deployed a custom content > filter written in java. > > Now I introduced amavisd (containing clamav and spamassassin) as content > filter such that the mail is passing in following manner: > > ===>mail from outside ===> Postfix ====> amavisd ===> custom content filter > > I referred the link(http://wiki.centos.org/HowTos/Amavisd) to setup > amavisd(containing clamav and spamassassin) > > Here my setup is running ok when amavisd is bypassed and mail is directly > being sent to custom content filter but I receive following error logs as > soon as I start passing my mails via amavisd: > > Apr 7 11:36:54 ip-10-194-99-63 > amavis[3264]: (03264-02) (!)rw_loop: leaving rw loop, no progress, > last event (select) 34.987 s ago Apparently your custom content filter is not responding with a SMTP greeting when amavisd tries to send a delivery notification to it. At log level 5 you can see what traffic is being passed on to the back-end server/scanner specified by $notify_method . Or do a packet capture on a loopback interface if using inet socket. Make sure your backend filter can handle multiple transactions within a single SMTP session. Btw, do you really want to send bounces too to the java filter? These could be sent directly to Postfix ($notify_method), while filtered messages could go to your filter ($forward_method). Mark
