On Thu, Jun 24, 2010 at 02:57:05PM +0100, Chris G wrote:
> If one writes a message to an mbox file then the size changes and (if atime is
> enabled) the modification time will be after the access time. So mutt
> *has* to say there's new mail in the mailbox.
Ah, then it is possibly only the immediate message in the status line at
the bottom of the window, which is new.
Since the erroneous [1] behaviour isn't user correctable, instead of
saving messages for later action to !, I'll save them to "todo", then.
Since that folder will never receive real new mail, it'll be clear that
the status line message from mutt does in fact not relate to new mail.
Since the emails will no longer be in !, I'll need something to prompt
me to go into the "todo" mail folder e.g. after the next boot. A trivial
script can cat an empty email to the file, on every login, to flag the
folder for reading. I wonder if there is a more elegant way than
cluttering the folder with piffle?
> It gets it right to the extent that the 'new' mail isn't marked as
> such in the index if it's not really new but I can see no way that
> mutt could act otherwise regarding seeing the mailbox as having new
> mail in it.
[1]
If mutt knows not to flag the transferred email as new, then it also
knows enough not chuck up the erroneous "New mail" message. The logic
used for the message flags is different from that used for confusing
the user with a false message, it appears.
Many thanks for the explanation.
Erik
--
"Further north on Queensland's Gold Coast, a company constructing a new
apartment block on low-lying ground was ordered to install emergency
moorings for rescue boats on the building's first floor because of
concerns over the possible impact of climate change."
- http://news.bbc.co.uk/2/low/asia-pacific/8542355.stm
