That was it, apparently DCC 1.3.15 and amavisd-new built without that compile time optin still worked, but in later versions it has to be there, I just added it to the spec file, rebuilt it, and it now works.
./configure --with-uid=amavis Thank you very much for the fix! Gary V <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 08/24/2006 05:57 PM To [email protected] cc Subject Re: [AMaViS-user] Dcc 1.3.42 and amavisd-new 2.4.2 CRivera wrote: > I've searched through the archives and cant seem to find the answer I > need. Is there something specific I need to do to get DCC to work with > amavisd-new? I've been using 1.3.15 until now without any issues, and I > used my same spec file to build the 1.3.42 and its not reporting as a > test/hit in amavisd-new, but it works with 1.3.15. When I check > spamassassin with 1.3.42 it looks good... > I welcome any sugestions, thx. > [EMAIL PROTECTED] spamassassin]# su amavis -c 'spamassassin --lint -D' > [30039] dbg: dcc: dccifd is not available: no r/w dccifd socket found > [30039] dbg: util: executable for dccproc was found at /usr/bin/dccproc > [30039] dbg: dcc: dccproc is available: /usr/bin/dccproc > [30039] dbg: info: entering helper-app run mode > [30039] dbg: dcc: opening pipe: /usr/bin/dccproc -H -x 0 < > /tmp/.spamassassin30039EpEFANtmp > [30045] dbg: util: setuid: ruid=10000 euid=10000 > [30039] dbg: dcc: got response: X-DCC--Metrics: orion 1074; Body=7289 > Fuz1=21860 Fuz2=9018939 > [30039] dbg: info: leaving helper-app run mode > [30039] dbg: dcc: listed: BODY=7289/999999 FUZ1=21860/999999 > FUZ2=9018939/999999 Am I misunderstanding, or does this not show it is working? If it seems to be working here, but not when amavisd-new is running: The amavisd-new executable could be using a different set of spamassassin config files (even different that the ones the amavis user is using when you run commands at the shell prompt). See if you have more than one v310.pre file on your system. I'm thinking there could be another one that does not have the DCC plugin enabled. In amavisd.conf, I set $sa_debug = '1,config'; and run amavisd in debug mode (not debug-sa). It then tells me where it looks for spamassassin config files. BTW, I compile DCC with ./configure --with-uid=amavis && make && make install You might also try 'amavisd debug-sa' to get a truer picture of whether it is actually functioning when the amavisd-new daemon is used. Gary V ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/ ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
