[dev] Re: marking moved mail as new...

[Ruben van der Steenhoven]

Ruben van der Steenhoven wrote:
> 
> 
> Jan Schneider wrote:
> 
>> Zitat von Ruben van der Steenhoven <ruben_donotspamme at webmeesters.nl>:
>>
>>
>>> Jan Schneider wrote:
>>>
>>>> Zitat von Ruben van der Steenhoven <ruben_donotspamme at webmeesters.nl>:
>>>>
>>>>
>>>>
>>>>> Michael M Slusarz wrote:
>>>>>
>>>>>
>>>>>> More old e-mail...
>>>>>>
>>>>>> Quoting Ruben van der Steenhoven <ruben_donotspamme at webmeesters.nl>:
>>>>>>
>>>>>> | Since the introduction of Ingo a couple of months ago, any read
>>>>>
>>>>>
>>> items
>>>
>>>>>> | that are
>>>>>> | moved by Ingo to a folder are counted as New items, although they
>>>>>
>>>>>
>>>>> remain
>>>>>
>>>>>
>>>>>> | read.
>>>>>> | Result is, that i get warnings of new mail in folders where there
>>>>>
>>>>>
>>> are
>>>
>>>>> no
>>>>>
>>>>>
>>>>>> | new
>>>>>> | mails at all.
>>>>>>
>>>>>> Can't reproduce this.  If a message is marked as read, and then I
>>>>>
>>>>>
>>>>> filter,
>>>>>
>>>>>
>>>>>> the message appears as 'read' in the new mailbox.
>>>>>>
>>>>>
>>>>> Excuse the late reaction, was ill last week, anyway:
>>>>>
>>>>> you're right that the message appears 'read' in the new mailbox, 
>>>>> but it
>>>>> DOES get counted as new by IMP, that's exactly what struck me as very
>>>>> strange...
>>>>> So if you have new mail notification turned on on the folder the
>>>>
>>>>
>>> message
>>>
>>>>> was moved to, you'll get nagged by messages saying you have new 
>>>>> mail in
>>>>> that folder although you haven't.
>>>>
>>>>
>>>>
>>>> Ehm, you actually *have* new mail in that folder.
>>>>
>>>> Jan.
>>>>
>>>
>>> Sorry Jan,
>>>
>>> i must disagree with you on that. This mail is moved there and as such
>>> it is new, but as mike pointed out, the mail has an UNREAD-flag which is
>>> off.
>>
>>
>>
>> Yes, the \Recent and the \Seen flags are different.
>>
>>
>>> IMHO current behaviour is contra-intuitive, because new mail is reported
>>> in a folder that contains no unread mail, and what is more it is not
>>> consistent with behaviour of manually moving mail to another folder.
>>> when i move mail manually it doesn't get marked as new, (even the old
>>
>>
>>
>> What do you mean with "manually"?
> 
> 
> With Manually, i mean that i select a message in IMP, and then move it 
> to another folder. These messages do not get the \Recent flag set 
> whereas the messages moved by INGO *do* get it set.
> 
> It's just this inconsistency that strikes me as contra-intuïtive.
> I would suggest following behaviour:
> Any Message that has the \Seen flag off and gets moved would have the 
> \Recent flag on.
> Any Message that has the \Seen flag on and gets moved would have the 
> \Recent flag off.
> Anyway, behaviour of INGO should always be consistent with manually 
> moving messages, unless i use the switches in INGO that force the \Read 
> flag on (off isn't possible (yet)).
> 
> Does this clear things up a bit?
> 
>>
>>
>>> IMP-filters did not mark moved mail as new), but INGO does (as i pointed
>>> out before, this behaviour is new since the introduction of INGO as
>>> rule-processor).
>>> Hope anyone can help...
>>
>>
>>
>> As we move the messages through the IMAP server, *all* moved messages 
>> have
>> the \Recent flag. It might be possible that we catched these recent
>> messages with the old code, but this not that easy if the messages are 
>> move
>> outside of IMP (by Ingo).
>>
>> Jan.
By lack of of other input, i started thinking how this could be solved 
myself. as i told before, i am not an expert in horde nor PhP, but it 
seems to me that is you could create hooks to the standard IMP 'move' 
function, and INGO would tie to these hooks, the problem should be 
solved? Or am i oversimplifieing things here??

Ruben