vm-mail-check-interval for IMAP

[Uday Reddy]

It is reported that setting vm-mail-check-interval to a non-nil value causes freezes when IMAP servers are involved. Shouldn't this be happening in the background? Why the freezes?

[Uday Reddy (reddyuday)]

See Bug 726231 for background.

[Uday Reddy (reddyuday)]

Notes: vm-imap-check-mail is downloading the entire message map of the mailbox, which is quite unnecessary. Secondly, once it has found new mail, it doesn't need to check again for this folder. But it continues checking.

[mere user (emacs-user)]

this sounds like progress. I guess the most one would want to know in
the modeline is if there is mail, and possibly how many messages. E

On Wed, Mar 2, 2011 at 4:10 PM, Uday Reddy <email address hidden> wrote:
> Notes:  vm-imap-check-mail is downloading the entire message map of the
> mailbox, which is quite unnecessary.  Secondly, once it has found new
> mail, it doesn't need to check again for this folder.  But it continues
> checking.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/726543
>
> Title:
>  vm-mail-check-interval for IMAP
>
> Status in VM (View Mail) for Emacs:
>  Triaged
>
> Bug description:
>  It is reported that setting vm-mail-check-interval to a non-nil value
>  causes freezes when IMAP servers are involved.  Shouldn't this be
>  happening in the background?  Why the freezes?
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/vm/+bug/726543/+subscribe
>

[Uday Reddy (reddyuday)]

Backtrace of synchronization-data in vm-imap-folder-check-for-mail:

Debugger entered--returning value: [\28294 ...]
  vm-imap-retrieve-uid-and-flags-data()
  byte-code(... 12)
* vm-imap-get-synchronization-data()
  vm-imap-folder-check-for-mail(nil)
  vm-check-for-spooled-mail(nil t)
  vm-check-mail-itimer-function([t 19829 14645 484000 60 vm-check-mail-itimer-function (#0) nil])
  apply(vm-check-mail-itimer-function [t 19829 14645 484000 60 vm-check-mail-itimer-function (#0) nil])
  byte-code("\301\302H\303H\"\207" [timer apply 5 6] 4)
  timer-event-handler([t 19829 14645 484000 60 vm-check-mail-itimer-function (#0) nil])

[Uday Reddy (reddyuday)]

I am going to change this so that once new mail has been found, VM won't check again until after you have done get-new-mail.

The only problem with this is that if you have multiple mail clients open and you download your mail into another mail client. Then, theoretically, the Mail indicator should go OFF when the other mail client retrieves the mail. But this is a strange way of doing things and I think people can put up with the slight bit of inaccuracy.

[mere user (emacs-user)]

sounds good to me. I assume it's not possible to do this in the
background then? cheers, E

On Sat, Mar 12, 2011 at 2:33 PM, Uday Reddy <email address hidden> wrote:
> I am going to change this so that once new mail has been found, VM won't
> check again until after you have done get-new-mail.
>
> The only problem with this is that if you have multiple mail clients
> open and you download your mail into another mail client.  Then,
> theoretically, the Mail indicator should go OFF when the other mail
> client retrieves the mail.  But this is a strange way of doing things
> and I think people can put up with the slight bit of inaccuracy.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/726543
>
> Title:
>  vm-mail-check-interval for IMAP
>
> Status in VM (View Mail) for Emacs:
>  Triaged
>
> Bug description:
>  It is reported that setting vm-mail-check-interval to a non-nil value
>  causes freezes when IMAP servers are involved.  Shouldn't this be
>  happening in the background?  Why the freezes?
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/vm/+bug/726543/+subscribe
>

[Uday Reddy (reddyuday)]

mere user writes:

> sounds good to me. I assume it's not possible to do this in the
> background then? cheers, E

It does get done in the "background" (as much as it is possible in
Emacs Lisp). But I suspect that your freezes might have more to do
with your servers going down in quality. I have been running the
mail-check timer ever since you reported this. It runs ok without
noticeable freezes.

Cheers,
Uday

[mere user (emacs-user)]

On Sat, Mar 12, 2011 at 11:21 PM, Uday Reddy <email address hidden> wrote:
> mere user writes:
>
>> sounds good to me.  I assume it's not possible to do this in the
>> background then?  cheers, E
>
> It does get done in the "background" (as much as it is possible in
> Emacs Lisp).  But I suspect that your freezes might have more to do
> with your servers going down in quality.  I have been running the
> mail-check timer ever since you reported this.  It runs ok without
> noticeable freezes.

does "background" mean that while it's done, emacs can do other
things, or does it need to wait? Let me know if there is anything I
can do to help.

[Uday Reddy (reddyuday)]

Fixes committed in revisions 1110 (?), 1115 (?), 1147 and 1149.

[Uday Reddy (reddyuday)]

Eli, I am closing this bug report. Please follow up if you still have the problem.

[mere user (emacs-user)]

OK, I turned the notification off, so I'll turn it on again and let
you know if something exciting comes up.

On Sat, Apr 23, 2011 at 5:49 PM, Uday Reddy <email address hidden> wrote:
> Eli, I am closing this bug report.  Please follow up if you still have
> the problem.
>
>
> ** Changed in: vm
>       Status: Triaged => Fix Committed
>
> ** Changed in: vm
>    Milestone: 8.2.1 => 8.2.0a
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/726543
>
> Title:
>  vm-mail-check-interval for IMAP
>
> Status in VM (View Mail) for Emacs:
>  Fix Committed
>
> Bug description:
>  It is reported that setting vm-mail-check-interval to a non-nil value
>  causes freezes when IMAP servers are involved.  Shouldn't this be
>  happening in the background?  Why the freezes?
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/vm/+bug/726543/+subscribe
>