At 10:25 2002-01-25 +0100, Nick Wilson did say:
I'm having some trouble, Some of my recipes are failing. I've noticed
Here is a relevant section of the logfile
A relevant section of the recipe would also help, for those who are not
psychic. Your problem is pretty glaring, really, but it should be even
more so if you compared the recipe that is failing against those which are not.
procmail: Assigning "INCLUDERC=/home/nick/.Procmail/known_spammers.rc"
procmail: Match on "^From.*pm0.net"
procmail: Locking "~/Mail/Other/spam.lock"
procmail: Error while writing to "~/Mail/Other/_yn.urQU8.localhost.localdoma"
Procmail cannot create the uniquely named lockfile (which it will symlink
to spam.lock). For a brief description of the dot lock process, see:
<http://www.rosat.mpe-garching.mpg.de/mailing-lists/procmail/1999-05/msg00186.html>
Then, check 'man procmail' and note that an explanation for "Error while
writing to" is conveniently listed there, in of all places, the man pages.
Now, with that in mind, should you really be using '~' in your recipe,
instead of $HOME ? Do the other recipes successfully write to a dir with ~
in it, or are they writing to $MAILDIR (i.e. no path portion specified
whatsoever), to a $MAILDIR relative path, to something using $HOME, or an
absolute path?
procmail: [2546] Fri Jan 25 08:36:22 2002
procmail: Locking "~/Mail/Other/spam.lock"
procmail: Error while writing to "~/Mail/Other/_yn,urQU8.localhost.localdoma"
procmail: [2546] Fri Jan 25 08:36:30 2002
Note that those (and all the other timestamps you showed) are 8 seconds
apart. That's the default (compiled-in) dot-lockfile sleep time.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail