Mark wrote: > Joshua.
>> Attached is a debug output from one message (I think) using >> /etc/init.d/amavis debug. > Sorry, this mailing list is stripping most attachments. > Either post in-line, or store on some server and provide URL. >> A couple troubling things catch my eye: >> >> Jun 27 16:49:49 mail.warbelows.com /usr/sbin/amavisd-new[32498]: (32498-01) >> lookup (debug_sender) => undef, "[EMAIL PROTECTED]" does not match >> >> But I have this line in my config file: @debug_sender_maps = ( >> ['[EMAIL PROTECTED]']); > Most strange. >> At line 193, there is this: >> Jun 27 16:49:49 mail.warbelows.com /usr/sbin/amavisd-new[32498]: (32498-01) >> calling SA parse, SA version 3.1.0 >> Jun 27 16:49:49 mail.warbelows.com /usr/sbin/amavisd-new[32498]: (32498-01) >> CALLING SA check >> Jun 27 16:49:51 mail.warbelows.com /usr/sbin/amavisd-new[32498]: (32498-01) >> RETURNED FROM SA check, time left: 30 s >> Jun 27 16:49:51 mail.warbelows.com /usr/sbin/amavisd-new[32498]: (32498-01) >> prolong_timer after spam_scan_SA: remaining time = 480 s >> Jun 27 16:49:51 mail.warbelows.com /usr/sbin/amavisd-new[32498]: (32498-01) >> spam_scan: score=0 tests=[none] >> >> So it called SA...but it gives no results from the call? >> I don't think it has to do with message size...even my small test messages >> aren't getting any headers. > You are right, the size is not a problem, nor is a bypass*. > Seems to be an issue with spamassassin. > When you were doing your experiments with a command-line 'spamassassin', > did you ensure the program was running under the same UID as amavisd runs > under? Something like the following is a common practice: > # su vscan -c 'spamassassin -t -D <test.msg' > If this does work correctly, then compare this SA debug output > with what is reported in the first couple of screenfulls > when you start amavisd as: amavisd debug-sa > Pay attention to correct paths/directories and possible > access violations to these directories. Check also that > the same version of Perl is in use, in case you have > more than one version installed. >> Amavisd-new 2.3.3 The Debian amavisd-new 2.3.3 package probably uses /etc/amavis/amavisd.conf if it is started with 'amavisd-new start' and it will use the files found in /etc/amavisd/conf.d/ if started with /etc/init.d/amavis start. This version of amavisd-new on Debian is a mess. What config files are you changing, and how are you starting amavisd-new? For the moment, to be consistent, start amavisd-new with '/etc/init.d/amavis start' and use /etc/amavis/conf.d/50-user as the file you change. Gary V ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ 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/
