expunge function does not call its callback if it is called after the end() call.

[Dzenly]

Tested with imap.yandex.ru mail.

    imap = new Imap(imapConfig);

    var myExpunge = function () {
      console.log('HERE'); / ok.
      return new Bluebird(function (resolve, reject) {
          imap.expunge(function (err) {
          console.log('HERE1'); // Never meet if the mail box is empty.
          // My poor promise will never be resolved or rejected. :(
          if (err) {
            reject(err);
          }
          resolve(true);
        });
      })
    }

Such a behavior kills a normal flow of any async actions.

[mscdex]

Can you set debug: console.log in the config and show the relevant output for the EXPUNGE request so a test can be written?

[Dzenly]

Thank you, I found a glitch in my code. I used imap.expunge() after imap.end():

        imap.end();
        console.log('BEFORE EXPUNGE CALL');
        imap.expunge(function (err) {
        })

And had such a debug log (no any mention of expunge in the log):

...
=> 'A6 LOGOUT'
BEFORE EXPUNGE CALL
<= '* BYE IMAP4rev1 Server logging out'
<= 'A6 OK LOGOUT completed'
[connection] Ended
[connection] Closed

When I removed imap.end() before imap.expunge() - the callback started to invoke.

But, I think it is useful to invoke the callback with an error (or throw some exception) in similar case (invalid object state), and not just ignore such a call.
Without this it would be too hard to debug anything in async code.