VM

action-labels need seeding

Bug #515124 reported by Uday Reddy on 2010-01-31
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VM
Low
Uday Reddy

Bug Description

If one does a vm-flag-message in a new mail folder, it gets ignored. The problem seems to be that \flagged is regarded as an "action-label" and it is added only if it is declared in the folder header. Adding other labels seems to work ok. Puzzling behaviour!

Uday Reddy (reddyuday) on 2010-01-31
Changed in vm:
status: New → Triaged
importance: Undecided → Low
assignee: nobody → Uday Reddy (reddyuday)
Uday Reddy (reddyuday) on 2010-02-24
tags: added: imap
Uday Reddy (reddyuday) on 2010-02-27
Changed in vm:
milestone: none → 8.1.1-devo
Uday Reddy (reddyuday) wrote :

In one instance, flagging a message didn't work even though there were other messages with \\flagged in the folder. (For an IMAP folder.) A debug trace showed this failure.

Debugger entered--returning value: nil
  intern-soft("\\flagged" [0 0 0 0 ! 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0])
* vm-add-or-delete-message-labels("\\flagged" 1 t)
* (let ((labels ...)) (vm-add-or-delete-message-labels "\\flagged" count (not ...)))
* vm-flag-message(1)
  call-interactively(vm-flag-message)

Evidently, the vm-label-obarray doesn't have \\flagged. It looks like vm-startup-apply-labels didn't do its job somehow.

Uday Reddy (reddyuday) on 2010-03-24
Changed in vm:
status: Triaged → In Progress
Uday Reddy (reddyuday) on 2010-05-09
Changed in vm:
milestone: 8.2.0-devo → 8.1.91a
Uday Reddy (reddyuday) wrote :

Found an instance today, where the X-VM-Labels header didn't have \flagged and some other labels as well. So, the problem must be that wrong X-VM-Labels header is being written out somewhere.

Uday Reddy (reddyuday) on 2011-01-20
Changed in vm:
milestone: 8.2.0b → 8.2.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers