On Wed, 20 Sep 2006 10:20:18 +0100, [EMAIL PROTECTED] wrote: >I'm using SA 3.1.1 and am calling it from a .procmailrc file as >suggested in http://wiki.apache.org/spamassassin/UsedViaProcmail, the >relevant lines are: > >:0 f >| formail -A"X-Procmail: Before SpamAssassin" > >:0fw: spamassassin.lock >* < 256000 >| /usr/bin/spamassassin > >:0 f >| formail -A"X-Procmail: After SpamAssassin" > > >I'm suffering from a portion of my mail not being scanned, I added the >two extra recipes to check that the SA recipe was being passed through >and in each case it is. I'm guessing it's to do with the lock file, if a >mail already has a lock then does the next mail come along just skip the >SA recipe or does it wait for the lock to become available? Can anyone >suggest what I can do to resolve this problem ?It's frustrating to get >spam which has apparently skipped the SA recipe.
There's a few things you could try; one is adding the flock key to your local.cf; another is to switch to MySQL based rather than flat file. I don't think SA waits, IIRC if the connection times out it passes the mail through unscanned. From http://spamassassin.apache.org/full/3.1.x/dist/doc/Mail_SpamAssassin_Conf.html >MISCELLANEOUS OPTIONS > >lock_method type > Select the file-locking method used to protect database files on-disk. By > default, SpamAssassin uses an NFS-safe locking method on UNIX; however, if > you are sure that the database files you'll be using for Bayes and AWL > storage will never be accessed over NFS, a non-NFS-safe locking system can be > selected. > > This will be quite a bit faster, but may risk file corruption if the files > are ever accessed by multiple clients at once, and one or more of them is > accessing them through an NFS filesystem. > > Note that different platforms require different locking systems. > > The supported locking systems for type are as follows: > >nfssafe - an NFS-safe locking system >flock - simple UNIX flock() locking >win32 - Win32 locking using sysopen (..., O_CREAT|O_EXCL).
