[ https://issues.apache.org/jira/browse/HUPA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer resolved HUPA-56. ------------------------------- Resolution: Fixed fix in trunk > Hupa throws Exception when get used with an IMAP Server which not support the > IDLE command > ------------------------------------------------------------------------------------------ > > Key: HUPA-56 > URL: https://issues.apache.org/jira/browse/HUPA-56 > Project: JAMES Hupa > Issue Type: Bug > Components: server > Affects Versions: 0.1 > Reporter: Norman Maurer > Assignee: Norman Maurer > Fix For: 0.1 > > > From javamail docs: > ****************************** > idle > public void idle() > throws MessagingException > Use the IMAP IDLE command (see RFC 2177), if supported by the server, to > enter idle mode so that the server can send unsolicited notifications without > the need for the client to constantly poll the server. Use a > ConnectionListener to be notified of events. When another thread (e.g., the > listener thread) needs to issue an IMAP comand for this Store, the idle mode > will be terminated and this method will return. Typically the caller will > invoke this method in a loop. > If the mail.imap.enableimapevents property is set, notifications received > while the IDLE command is active will be delivered to ConnectionListeners as > events with a type of IMAPStore.RESPONSE. The event's message will be the raw > IMAP response string. Note that most IMAP servers will not deliver any events > when using the IDLE command on a connection with no mailbox selected (i.e., > this method). In most cases you'll want to use the idle method on IMAPFolder. > NOTE: This capability is highly experimental and likely will change in > future releases. > The mail.imap.minidletime property enforces a minimum delay before > returning from this method, to ensure that other threads have a chance to > issue commands before the caller invokes this method again. The default delay > is 10 milliseconds. > Throws: > MessagingException - if the server doesn't support the IDLE extension > IllegalStateException - if the store isn't connected > Since: > JavaMail 1.4.1 > ****************** > So we should catch the MessagingException in this case -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org