<<< Date Index >>>     <<< Thread Index >>>

Re: [Mutt] #3424: Mutt falsely detects its own mbox writes as new mail.



#3424: Mutt falsely detects its own mbox writes as new mail.
---------------------+------------------------------------------------------
  Reporter:  dvalin  |       Owner:  me                       
      Type:  defect  |      Status:  new                      
  Priority:  major   |   Milestone:  1.6                      
 Component:  mutt    |     Version:  1.5.20                   
Resolution:          |    Keywords:  false mail detection mbox
---------------------+------------------------------------------------------
Changes (by clsmall):

  * status:  closed => new
  * resolution:  worksforme =>


Comment:

 I'm reopening this because I believe the problem has not been completely
 investigated based upon the previous comment.

 In my case, the problem does not require a copy operation to another
 mailbox, but simply a delete operation in the current mailbox in order to
 trigger it.

 I am using mutt 1.5.20 and have the following set in .muttrc:
     set nocheck_mbox_size
     set   check_new
     set   mbox=+mbox
     set   mbox_type=mbox

 I don't have any setting for "mail_check_recent" and see no entry for it
 in the muttrc man page, so it has whatever the default setting happens to
 be.

 When I get new mail notification from the gnome inbox monitor (ver.
 2.6.2.1) I double-click on the icon and start up mutt in a pop-up xterm
 window looking at the mail in my inbox located under /var/mail.  The gnome
 inbox monitor animation stops.
 If I delete one or more messages and then resync the mailbox using '$',
 the gnome inbox monitor soon begins to report that there is new mail,
 regardless of whether mutt remains open or closed.  This requires that I
 exit mutt and restart it in order to get the gnome inbox monitor to stop
 thinking that there is new mail in the box.

 Whatever mutt is doing, it did not cause this problem when using version
 1.4 under the same gnome setup.  This is new behavior with version 1.5 and
 is extremely annoying.  I would greatly appreciate it if this could be
 fixed.  Please let me know if you require any additional information in
 order to better diagnose the problem.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3424#comment:4>
Mutt <http://www.mutt.org/>
The Mutt mail user agent