I get the same issue with W22

Which account are you using POP or IMAP?

I'm on IMAP. POP doesn't support flagging mails as read on the server, does it?

I have 2 thunderbird clients, webmail and modest.  Assuming that modest is
offline, I get a new email and read it in any of the other clients.  Any of the
other clients _will_not_ give me an alert because the mail has been read. 
Launching modest, I will then get a new mail notification for the read email.

Thanks

any movement on this?

Comment 5 Andre Klapper 2008-10-02 13:38:07 UTC

Chris: Private IMAP server (if so, which product and version? UW IMAP, Courier,
Cyrus, Dovecot?) or a public one?

A debug log of the connection to the mail server might help (well - even if it
only shows that Modest recognizes the mail as UNREAD)
Please start a X Terminal window and enter
    export "CAMEL_DEBUG"="all"
to enable the debug mode of the mail library. After that, enter
    /usr/bin/maemo-summoner /usr/bin/modest.launch showui > log 2>&1
to start the email application. Then connect to the mail server. Attach the
logfile named "log" here (please check for confidential data before attaching).

My mail server is a private one, running exim and dovecot. I will try and get a
debug log.  However, doesn't IMAP have a "Seen" flag, which might be more
appropriate for this?  That way, if I have thunderbird running on my desktop
and it receives the mail, I won't get alerted on the n800 even if I've not read
it?  Maybe this could be configurable?

*** This bug has been confirmed by popular vote. ***

Well, the bug was confirmed automatically for my vote, but I was going to
confirm it manually.

This bug is easy to trigger, and I am suffering it too. Not a big problem
because I know the emails I have read, but it's a bug anyway.

I'll upload a log this afternoon.

I'm using GMail with IMAP and Modest version 1.0-2008.35-1

Because if it wasn't clear as trigger the bug, I am going to explain it:

1) Put Modest to receive mails automatically every X minutes.
2) Close Modest
3) Send a new mail from another account.
4) Before receive this new mail in Modest, read it with another client.
5) Wait until the next time when Modest search for new mails.
6) Modest show a notification (led + icon in the Task Navigator) with the new
mail though this mail is read.

If you have Modest open, it sees the new mail as read, and then there isn't the
cool notification.

Created an attachment (id=1060) [details]
Log receiving a read mail with Modest open

The log is get with: /usr/bin/maemo-summoner /usr/bin/modest.launch showui >
log 2>&1

It launches Modest and when the read mail is received, all is OK. Here, the bug
doesn't happen.

Created an attachment (id=1061) [details]
Log receiving a read mail with Modest closed

This log was got with: /usr/bin/maemo-summoner /usr/bin/modest.launch > log
2>&1

When the read mail is received, the notification is shown.
The part of the log where the mail is received is very similar. 

My assumption is that Modest notify always that there is a new mail in the
INBOX and doesn't look the state of the mail. But I could be wrong, so I'll
have to look the code ;)

Created an attachment (id=1062) [details]
patch fixing the bug

With the attached patch, Modest only shows the notification when an mail isn't
read.
If there is more than one, the notification only shows the unread ones.

Really the code is only 4 lines, but in the patch it seems more because I am
using an "if" and I have indented the code down of the "if" to follow with the
structure of the rest of the code.

Created an attachment (id=1063) [details]
patch fixing the bug

Sorry for spamming, I uploaded a bad patch, this is the right ;)

Committed fix for this in modest git master 07e4d11...

Instead of using the patch (thanks Daniel for the effort anyway!), I've took a
different approach, that should also avoid blinking leds for already seen
messages, and be valid for all the platforms and not platform specific.

Setting TM to be fremantle

Comment 15 Andre Klapper 2009-07-14 13:38:16 UTC

Fix should be included in Fremantle SDK beta 2 hence updating Target Milestone.
If you are the reporter of this bug: Feel free to verify the fix if possible.

Marking patches of interest to Diablo (Maemo4) community updates, please excuse
the noise.