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

Leave a copy of the message causing reception issue #7

Open
jackoo opened this issue Jul 18, 2013 · 2 comments
Open

Leave a copy of the message causing reception issue #7

jackoo opened this issue Jul 18, 2013 · 2 comments

Comments

@jackoo
Copy link

jackoo commented Jul 18, 2013

Hello,

I'm using Roundcube 0.9.2 with latest pop3fetcher 1.5. There is a strange bug that only happen when the option "Leave a copy of the message on the server" is enabled. Actually, only 50% of the new messages are processed (enter in the inbox). I'm using an empty account to test. When sending the first email, it works no problem. The second mail I send doesn't work, the third one works, the fourth one doesn't work... and it continue like this.

To be able to reproduce the bug, don't send 4 messages one shot. Do it one by one by refreshing roundcube between each email sending.

By looking at the code (and by enabling debug), I can notice that the value of $i is sometimes equal to var $Count. When this happen, the code doesn't go further and the new message isn't grabbed. Is it possible for you to do some test and confirm this behavior? Thanks!

@stan86
Copy link

stan86 commented Mar 12, 2014

I think it's due a little error at line 104 in pop3fetcher.php $i=$j+1 is not needed, you can simply fix it using $i=$j.
I'm sending an email to the dev to make sure my solution is correct.

@theqkash
Copy link
Collaborator

theqkash commented Sep 3, 2016

Hello,

Is that problem still happening?
I've checked that by myself and I was not unable to reproduce it.

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

No branches or pull requests

3 participants