bummer. it looks like procmail uses username$LOCKEXT
while my pop daemon uses .username.pop
sigh, this is getting silly. is there a way to do it so it also uses the dot?
this is qpopper 4.0.3, which supposedly also supports flock()
plus this is (i hear) the most widely used linux pop daemon, so im depressed
why this shows up for me, and nobody else. maybe the problem lies elsewhere...
so, just to double-check, i hope no one minds (i just dont want to
mess with a production system), i will create an /etc/procmailrc
(there is none yet) that has nothing else but:
:0: .$LOGNAME.pop
or should that be :0: /var/spool/mail/.$LOGNAME.pop?
that ok?
You're probably actually better off defining $LOCKEXT. Defining a recipe with
no conditions and no action probably won't work, and since you're just chaning
the extension, not the whole lock file name, this should do what you need.
Just make an /etc/procmailrc with
LOCKEXT=.pop
in it. Thus you're not mucking with the path to the file.
--
Andrew Edelstein - andrew(_at_)pure-chaos(_dot_)com
http://andrew.pure-chaos.com
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail