Re: How do I prevent lock files
Hitete, could you please stop posting new questions by replying to threads? You may not know it, but any decent client, including your IMP, puts information about that in the message and any other decent client will use that information for threading so one gets several topics cluttered in one thread. If you want to reply hit "Reply". If you want to ask a question hit "New message". Thanks, Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de & http://msie.winware.org
RE: How do I prevent lock files
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, November 05, 2004 1:06 PM > To: users@spamassassin.apache.org > Subject: Re: How do I prevent lock files > > > First of all thanks for answering. Then I'm sorry I have to > write back but I'm not sure Ii understand : > > > > :0fw:spamassassin.lock > > ^^ > > Actually, you remove this part. A second colon on a line > indicating > > the start of a procmail recipe tells procmail to use a > lockfile- which > > will be named as indicated if you include a lockfile name as you've > > got here. > > Do you mean that I only have to put : > > :0fw > blablabla > > ? That's correct. > > > :0: > > > * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\* > > > /dev/null > > > > You can remove the second colon here; no need to lock > /dev/null for > > writing. > > What is second colon ?. Don't quite see what it is ?. > > Dpo I have to write : > > :0 instead of :0: ?. > > What is the difference ?. That's really a question about Procmail. I'd suggest you read the procmailrc "man page" to find out more about what you're actually telling procmail to do. But, the short answer is that the second colon (:) tells procmail to use a lock file. It's probably a good idea to actually find out what your procmail recipes are doing if you're just copying them from another website or using recommendations from here or elsewhere.
Re: How do I prevent lock files
First of all thanks for answering. Then I'm sorry I have to write back but I'm not sure Ii understand : > > :0fw:spamassassin.lock > ^^ > Actually, you remove this part. A second colon on a line indicating the > start of a procmail recipe tells procmail to use a lockfile- which will > be named as indicated if you include a lockfile name as you've got here. Do you mean that I only have to put : :0fw blablabla ? > > > :0: > > * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\* > > /dev/null > > You can remove the second colon here; no need to lock /dev/null for > writing. What is second colon ?. Don't quite see what it is ?. Dpo I have to write : :0 instead of :0: ?. What is the difference ?. -- What are lockfiles for anyway ?. I read a bit and I think I understood that mails are sent back . Am I wrong ?. Maybe I didn't understand well /Hitete
Re: How do I prevent lock files
[EMAIL PROTECTED] wrote: > What do I have to add in procmailrc to stop spamassassn from trying > to create a lock file ?. > > here is my procmailrc : > > LOGFILE=/var/log/procmail.log > DROPPRIVS=yes > > :0fw:spamassassin.lock ^^ Actually, you remove this part. A second colon on a line indicating the start of a procmail recipe tells procmail to use a lockfile- which will be named as indicated if you include a lockfile name as you've got here. > :0: > * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\* > /dev/null You can remove the second colon here; no need to lock /dev/null for writing. -kgd -- Get your mouse off of there! You don't know where that email has been!
How do I prevent lock files
How do I prevent lock files from being "used" ? I get these errors in the logs : - procmail: Couldn't determine implicit lockfile from "/usr/bin/spamc" procmail: Lock failure on ".lock" - What do I have to add in procmailrc to stop spamassassn from trying to create a lock file ?. here is my procmailrc : LOGFILE=/var/log/procmail.log DROPPRIVS=yes :0fw:spamassassin.lock * < 256000 | /usr/bin/spamc -f :0: * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\* /dev/null :0: * ^X-Spam-Status: Yes $HOME/SPAM == /Hitete
