Ken Hornstein writes:
What it doesn't mention is that the resulting train wreck can mangle other
sequences in the .mh_seq file as well. Also, should we change that text
to say do not use rcvstore without an external locking mechanism'? It's
perfectly save to use it from procmail with unseen
So are you saying that I don't need to specify locking in my procmail
recipes any more?
Sadly ... David is right in that you still do need to do that. The sequence
file won't get corrupted anymore, but we'd need to lock the whole file during
message receive to make it work right. It occurs to
