On Monday 01 Mar 2004 05:23, Ricardo Castanho de Oliveira Freitas wrote: > On Sunday 29 February 2004 16:55, Derek Jennings wrote: > > Tks, Derek! but ONE more question! > (see below, pls) > > > On Sunday 29 Feb 2004 19:40, Ricardo Castanho de Oliveira Freitas wrote: > > > Hi! > > > I've been using spamassassin for a while, but.... I must have missed > > > some detail on the config process! > > > > It is not spamassassin setting the lock file. it is procmail > > Any procmail recipe that starts with > > > > :0 > > > > will not create a lock file. You do not need a lock file when piping your > > mails through spamassassin. The lock file is there simply to stop > > procmail and kmail trying to use a mail spool file at the same time. You > > only need to set it when actually writing to a mail spool file. > > > > A procmail recipe starting with > > > > :0 : > > > > will use the default lockfile. > > The default lockfile name will be the same as the mail folder used with a > > leading '.' > > > > A procmail recipe in the form > > > > :0 : lockfilename > > Can I use: > :0: /home/user/some_dir/.lock_file ? > > or it has to use the default mail box (~/Mail) for kmail? > > > derek > > TIA > > Ricardo Castanho
The lockfile can be called anything you like so long as the 'other' application using the mail spool knows its name, or else there is no point using a lock file at all. In the Kmail account setup for local mail spool accounts you can define the name of the lockfile in use. derek -- www.jennings.homelinux.net http://twiki.mdklinuxfaq.org
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
