Re: Re: [evolution-patches] Possible fix for #322016

[<karllinuxtest relton ntlworld com>]

> 
> From: Jeffrey Stedfast <fejj novell com>
> > 
> > Fundamentally the only way I can see to truely fix these
> > is for the notifications to be sent after a 'fetch mail'
> > operation, i.e. when brand new mail truely arrives into
> > Evolution.
> 
> The problem is that new mail can arrive more than just after a 'fetch
> mail' op. For example, new mail can arrive at any time for IMAP and
> possibly other remote mail providers.
> 

Right - I see what you mean. Presumably though there is
a place in the code where the newly arrived mail (from
whatever source) is 'added' to the system (e.g. the
message-id will be recorded somewhere). If that is a single
place in the code, that might be a better place to
trigger the notifications.

The problem with the folder update code I have been
looking at is that there seems no way of knowing if
it is truely new mail into the system, or just the user
shuffling messages from one folder to another. Therefore
no amount of checks or flags will eliminate all false
notifications.

Obviously I'm totally new to the code, so I'm making a few
wild-ish guesses ...

Karl

-----------------------------------------
Email sent from www.ntlworld.com
Virus-checked using McAfee(R) Software 
Visit www.ntlworld.com/security for more information