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

Add Net::IMAP::IgnoredResponse #3

Merged
merged 1 commit into from
Mar 9, 2021

Conversation

c-leroy
Copy link
Contributor

@c-leroy c-leroy commented Jul 24, 2020

Zimbra server can send an untagged response "* NOOP\r\n" in order to
keep alive connection during long-running requests. These responses are
not syntactically correct, but can be safely ignored.

Add Net::IMAP::IgnoredResponse, and use it for this case.

Fixes #2

Zimbra server can send an untagged response "* NOOP\r\n" in order to
keep alive connection during long-running requests. These responses are
not syntactically correct, but can be safely ignored.

Add Net::IMAP::IgnoredResponse, and use it for this case.

Fixes ruby#2
@c-leroy
Copy link
Contributor Author

c-leroy commented Jul 24, 2020

I have opened a ticket on Ruby redmine : https://bugs.ruby-lang.org/issues/17049

@shugo shugo merged commit b311483 into ruby:master Mar 9, 2021
@shugo
Copy link
Member

shugo commented Mar 9, 2021

@c-leroy Thank you. It looks fine and I've merged it.

@Nestorfish Nestorfish deleted the untagged_response_noop branch March 11, 2021 22:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

NOOP untagged response sent by Zimbra
2 participants