Sometime around Wed, Jun 07, 2000 at 01:35:44AM +0300, Mikko H?nninen said:
> timestamps. This usually means that some program or another has read
> the folder file since new mail was delivered into it, which makes the
> accessed time later than the modified time.
I use fetchmail to get the mail and Procmail to deliver it. so I dont
think its the second one i.e its probably not an NFS problem. And also
in some cases after I check the mail in spool folder, typing "c<space>"
actually works. i.e it gives me the name of the next folder like "=fslc"
or something like that, that has new mail, but in most cases it does not
work. Also in the rare case where it does work, it does not recognise the
other mailing list folders where there is new mail. I have xbiff, but I
doubt that its even running when I am in console, plain text terminals.
In anycase, I dont think it would check mail in folders other than spool
without me explicitly setting it up to do so. (which I have not)
> We can't really tell why the file timestamps change on your system, but
> possivbe reasons (that I have seen) include:
> 1) the folder has been opened before with Mutt or another email program
> 2) problems with timestamps for files served over NFS (but if you're
> using NFS I strongly recommend Maildir format anyway)
> 3) new mail notifiers which scan the folder and don't reset the last
> accessed timestamp
> 4) backup programs which read the folder files
It would be great if you also added what the most common remedies to
this were (based on what you read, that is) :-) and what were the most
probable reasons for this to happen.. ie. what are the programs that you
think can check mail before mutt does and change that timestamp.
Thank you,
Aravind
