Re: NFS Problem in Kernel 2.0.27: inode status not updated

> Strangely they for years worked for us. Only exim failed.
> Other MUAs might check the return code of the system calls instead.

Hmm -- as I understood it, PH10 ripped the code off from another system.
I assume that at least some other system has the same problem,
and I kind of assumed that return codes were checked -- I take it they are not
:-(((

> Exim is definitely going beyond POSIX specs here which is
> bad and I would consider Exim buggy not Linux.

Well, we know that Linux is being "fixed", and as I understand it PH10 is
re-doing exim as well, so whhich is "in the wrong" isn't important.