- Mate Wierdl <[EMAIL PROTECTED]>:
| Now, I ran some tests indicating that at least one mail
| client (mailx) on an IRIX 6.2 box I have available, and it appears to
| use dotlocking and to ignore flock-style locks.
|
| Is not it a problem too that he is delivering to symlinks?
No, he doesn't. He delivers to real files, but the path of the files
happen to contain symlinks: Delivery to /var/mail/USER where
/var/mail is a symlink to /usr/mail. But /usr/mail/USER is a proper
file. There should be no problem with this.
Exept with procmail: it deletes a symlink and it tries to create a
file named BOGUS.
This is described in its man page---and mentioned in INSTALL.mbox.
| If course, with vanilla qmail, this strategy loses badly.
|
| How can then mail be lost?
User runs mailx, reads all his mail and quits. Mailx moves
all the read messages to ~/mbox and truncates the incoming mbox.
Just before the latter activity qmail adds a new message. Poof.
I see. Is there a solution? Cannot setlock from serialmail be used in
a mailx wrapper?
We have an Irix box here (I do not know the version). How could one
test something like this?
Mate
