-
Notifications
You must be signed in to change notification settings - Fork 181
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
Error processing command: End of stream Command should be '<tag> IDLE'
after updating to v1.6.5
#413
Comments
Error processing command: End of stream Command should be '<tag> IDLE'
after updating to v1.6.5
@ceisele-r Thanks for the report. Would you be able to provide a debug log (depends on how you start greenmail: standalone |
@apinske sorry for the late response. I will try to gather the debug logs for |
@apinske here is the exception part with verbose log activated and the most recent logging from greenmail before that (last imap and last smtp block):
Let me know if you need more - as the log is pretty huge, I tried to extract only the last parts. |
@ceisele-r Sorry for the late reply. Were you updating to 1.6.5 from 1.6.4 or a version before that, i.e. were you using IMAP IDLE (introduced in 1.6.4) successfully before? It seems that node-imap (which version are you using, btw?) uses polling if IDLE is not supported. Unfortunately, I still have no idea, what could be the problem. Is there no line after Does it only ever work for the first mail, and then the error occurs for the second one? Or is ist after a certain amount of time? Could you attach the missing log between |
@apinske no worries. We are using Unfortunately, the log from my original message was deleted meanwhile so I have to create a new log with debug logging enabled. I will do that and post check if there's such a line as you mentioned in there.
Unfortunately, I don't know. The error occurs while/after executing several hundred unittests. I will try if I can isolate it somehow. |
@apinske I received an email regarding a new comment by you ("you might have reproduced the problem") but it seems this comment is missing in this thread here on GH. Did you delete it again? I just want to clarify whether you could reproduce this issue or whether I can still help trace it by producing the logs. |
Two years late, but I encountered a similar situation, and the problem was the result of failing to close my To reproduce, just have an |
After updating to greenmail v1.6.5, the following exception is logged at the end of our test executions:
This probably happens during something being shut down (probably the connection by
imap
).If you need more information, please let me know.
The text was updated successfully, but these errors were encountered: