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
Receiving NPE in Utility.toMessageSet after MOVE command is issues #477
Comments
Hi @nikowitt , can you provide a test case to provoke the issue? This is the current test for MOVE-with-COPYUID, if it helps: I will try to reproduce ~ this weekend. |
Yes, I will try to do this today. |
… the behaviour in production
Guess I am on the right track, please check testFolderMoveMessagesBasedOnUid. I guess it is related to the fact that in our code, we rely on picking references to messages based on the UID. Maybe this helps tracking down the issue.
|
Seems to work fine with 1.6.11, thanks! |
Good to hear & appreciate the feedback! |
Hi there,
I am currently trying to update GreenMail 1.6.5 to 1.6.10. With 1.6.6, the MOVE capability was implemented. This breaks my tests and I am currently wondering if it is a regression in GreenMail or if our MOVE implementation is flawed. Maybe you can give me a hint:
Test case: 2 Mails are put on an IMAP servers. Mail 1 is processed and then moved (or copied and deleted if MOVE is not supported) to another folder, then the same happens for mail 2:
GreenMail 1.6.5 output:
Here we can see that mails are read, copied to the MOVED TO folder and are deleted from the inbox. * 1 FETCH (UID 2) is issued, following by a body.peek.
GreenMail 1.6.7 output that uses the MOVE command (but also valid for 1.6.10):
Here, B13 UID FETCH 2 (UID) is issued, but the next body.peek is simply missing. This results in a
Does this behaviour ring any bells? Thanks in advance!
Regards, Niko
The text was updated successfully, but these errors were encountered: