| Summary | Toggle junk flags |
| Queue | IMP |
| Queue Version | Git master |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | jan (at) horde (dot) org |
| Requester | jan (at) horde (dot) org |
| Created | 09/12/2012 (4802 days ago) |
| Due | |
| Updated | 10/02/2012 (4782 days ago) |
| Assigned | |
| Resolved | 10/02/2012 (4782 days ago) |
| Milestone | 6 |
| Patch | No |
State ⇒ Rejected
Assigned to Jan Schneider
Milestone ⇒ 6
having both the $Junk and $NotJunk flags set. This could happen in
real life scenarios, if the user accidentally reports a message a
spam, and then wants to revert this action by reporting them as not
spam.
set at any given time, e.g.:
$imp_message->flag(array('$junk'), $indices, true);
$imp_message->flag(array('$notjunk'), $indices, false);
have certain semantics that need to be enforced (no different than the
$Forwarded flag, for example).
You shouldn't be seeing both $Junk and $NotJunk though. If we are not
clearing one when flagging with the other, this is a bug.
State ⇒ Feedback
Type ⇒ Enhancement
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Toggle junk flags
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Feedback
both a spam and ham, and end up with messages having both the $Junk
and $NotJunk flags set. This could happen in real life scenarios, if
the user accidentally reports a message a spam, and then wants to
revert this action by reporting them as not spam.