Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message List fills up with duplicate messages when checking for recent mails #2334

Closed
rcubetrac opened this issue Aug 14, 2009 · 11 comments
Closed

Comments

@rcubetrac
Copy link

@rcubetrac rcubetrac commented Aug 14, 2009

Reported by rosali on 14 Aug 2009 05:04 UTC as Trac ticket #1486044

Steps to reproduce:

  • Select a folder other than INBOX which contains at least one message
  • Click on "Check for new messages"

-> Result: Message List is duplicated

IMAP-Server: hMail 5.2
Browser: IE 6-8 / Firefox

This bug was reported in the Forum several times. But I never was able to reproduce until I noticed that this behaviour occurs only on folders other than INBOX.

Migrated-From: http://trac.roundcube.net/ticket/1486044

@rcubetrac
Copy link
Author

@rcubetrac rcubetrac commented Aug 14, 2009

Comment by Lazlo on 14 Aug 2009 08:35 UTC

Can't reproduce it with Dovecot and Firefox. I think this is a hMail issue.

@rcubetrac
Copy link
Author

@rcubetrac rcubetrac commented Aug 16, 2009

Comment by @vbenincasa on 16 Aug 2009 00:37 UTC

Can't reproduce this bug here with Dovecot 1.2.1 / RC trunk 2814 / Firefox 3.5.2

@rcubetrac
Copy link
Author

@rcubetrac rcubetrac commented Aug 18, 2009

Comment by rosali on 18 Aug 2009 07:58 UTC

Issue Topic @ hmailserver forum:

http://www.hmailserver.com/forum/viewtopic.php?f=7&t=15978&p=92323#p92323

@rcubetrac
Copy link
Author

@rcubetrac rcubetrac commented Aug 19, 2009

Comment by rosali on 19 Aug 2009 08:47 UTC

Please review hMailServer Forum topic @ http://hmailserver.com/forum/viewtopic.php?f=7&t=15978&p=92443#p92443

hMailServer Developer claims that RoundCube method for checking for new messages is not fail safe.

@rcubetrac
Copy link
Author

@rcubetrac rcubetrac commented Aug 19, 2009

Comment by knafve on 19 Aug 2009 14:24 UTC

.. for a bunch of different reasons.

In short, the IMAP RFC allows IMAP servers to set the \Recent flag on messages even if they are not recent. It's against the recommendation, but not forbidden. Hence, an IMAP client can't expect all \Recent messages to be recent. The client need to compare the UID's of the messages with the already received UID's as well, to prevent duplicates.

Second, the IMAP RFC does not explictly specify what "recent" means. It could mean a lot of different things.

Third, neither GMail nor Mercury32 seems to set the \Recent flag on new messages so in these the "Check for new mail" doesn't appear to work. MailEnable doesn't reset it when the client is logged out, so when using MailEnable duplicate messages will appear.

@rcubetrac
Copy link
Author

@rcubetrac rcubetrac commented Nov 15, 2009

Comment by Cube8 on 15 Nov 2009 00:38 UTC

So, why doesn't is happen in the Inbox folder?

@rcubetrac
Copy link
Author

@rcubetrac rcubetrac commented Nov 21, 2009

Comment by richard scott on 21 Nov 2009 20:41 UTC

I get this happening in 3.0.1 in my inbox if (and only if) i tick the "check for messages in all boxes" option

@rcubetrac
Copy link
Author

@rcubetrac rcubetrac commented Dec 21, 2009

Comment by @alecpl on 21 Dec 2009 14:35 UTC

hMailServer's users need update to version 5.3 Build 362. Others should try with svn-trunk version.

@rcubetrac
Copy link
Author

@rcubetrac rcubetrac commented Dec 21, 2009

Status changed by @alecpl on 21 Dec 2009 14:35 UTC

new => closed

@rcubetrac rcubetrac closed this Dec 21, 2009
@rcubetrac
Copy link
Author

@rcubetrac rcubetrac commented Dec 21, 2009

Comment by richard scott on 21 Dec 2009 14:46 UTC

but I don't have a "hMailServer"
I have a courier-imap server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.