Description of Problem: Send -annotate is using fcntl(fd, F_SETLK,..) to lock a message before annotating it. Since the default is to disable mandatory file locking (and in fact it seems to be the strongly recommended setting) fcntl fails with ENOLCK (No locks available) Version-Release number of selected component (if applicable): How Reproducible: set your mail directory to a nfs mounted directory, add send: -annotate to your mh_profile, and with a current message avalilable do run repl. after the message is sent, (say about 20 seconds later) you will get the message send: unable to lock and open 172: No locks available, continuing... (with 172 replaced by current message number) Actual Results: while I didn't recompile the program to see which defines are set, running strace on the repl shows: fcntl64(0x3, 0x6, 0xbffe5c60, 0x3) = -1 ENOLCK (No locks available) which would imply that in sbr/lock_file.c FCNTL_LOCKING defined, KERNEL_LOCKING defined LOCKF_LOCKING not defined FLOCK_LOCKING not defined. Seems like it should be built with the old standby DOT_LOCKING defined which works everywhere