On Mon, Jan 08, 2001 at 12:49:55PM +0100, Heinrich Langos wrote:
> On Tue, Jan 02, 2001 at 11:23:25PM +0100, Nikolai Prokoschenko wrote:
> > Hi!
> > 
> > I'm sad - the detection of new mail is not working anymore :(( The worst thing is 
>- I can't even imagine, what might have
> > gone wrong. Can I somehow see, which mailboxes are being watched by Mutt? I have a 
>typical line "mailboxes `ls
> > /home/nikolai/Mail/Mails/*`" in my .muttrc, but still - new mails are not 
>detected. Can someone help? Ask for further info,
> > if you need it...
> > 
> > Best regards,
> > 
> > Nikolai.
> 
> similar problem here... new mails get detected .. but not allways.
> starting "mutt -y" may or may not show good results.
> so i've "set sort_browser=reverse-date" in my .muttrc
> this way i see when a mailbox has been changed last time and
> recent changes float on top. even if it isn't marked with that 
> nice "N".


found the reason in the manual:

-----snipp-----
3.11 Defining mailboxes which receive mail 
[...]
Note: new mail is detected by comparing the last modification time to
the last access time. Utilities like biff or frm or any other program
which accesses the mailbox might cause Mutt to never detect new mail
for that mailbox if they do not properly reset the access time. Backup
tools are another common reason for updated access times.
-----snipp-----

another mystery solved ...

-heinrich

-- 
                Heinrich Langos <[EMAIL PROTECTED]>
     pgp: http://wh9.tu-dresden.de/~heinrich/pub_pgp_key.asc
 _________________________________________________________________
|o| The reason we come up with new versions is not to fix bugs. |o|
|o| It's absolutely not. It's the stupidest reason to buy a new |o|
|o| version I ever heard. -- Bill Gates,  Microsoft Corporation |o|
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Reply via email to