Skip to content

GH-3017: Expose cancel-idle-interval XML attribute #3034

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

Closed
wants to merge 2 commits into from

Conversation

artembilan
Copy link
Member

Fixes #3017

  • Expose also a ImapIdleChannelAdapterSpec.cancelIdleInterval() option
  • Deprecate useless ImapMailInboundChannelAdapterSpec.cancelIdleInterval()

@@ -434,6 +433,10 @@ Leaving it up to you also means that you are less likely to end up with unintend
NOTE: When configuring a polling email adapter's `should-mark-messages-as-read` attribute, you should be aware of the protocol you are configuring to retrieve messages.
For example, POP3 does not support this flag, which means setting it to either value has no effect, as messages are not marked as read.

In case of silently dropped connection, an idle cancel task is run on background periodically (a new IDLE will usually immediately be processed).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the case of a silently... run in the background....

Fixes spring-projects#3017

* Expose also a `ImapIdleChannelAdapterSpec.cancelIdleInterval()` option
* Deprecate useless `ImapMailInboundChannelAdapterSpec.cancelIdleInterval()`
@artembilan
Copy link
Member Author

Doc has been fixed.
Thanks

@garyrussell
Copy link
Contributor

Merged as ca8377d with minor doc polishing.

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

Successfully merging this pull request may close these issues.

Add cancelIdleInterval to IMAP mail adapter XSD and parsers
2 participants