Deleting doesn't really delete

[jeb218]

I am calling the message delete function, which returns successful, and the message doesn't show in the inbox anymore when I log into the mail interface. Although the unread message counter still shows (1) for a supposedly empty inbox.

The main problem is that inbox.getNextMessage still grabs the deleted message. So now I have a phantom email in the inbox that I can't delete through code, or the interface.

[atiertant]

hi, do you have a piece of code ? could you write a tests ?

[jeb218]

Hi, that occurred when using the code directly on the npm mailx docs page. I was using the version of the code that uses the "recursiveRcpt()" function.

Inside of the "inbox.getNextMessage" function, I added a call to message.delete, which returns successfully, but really does what I mentioned in the first comment.

I switched my code to use the other example, which calls "store.getInboxMessages", and then deletes the last message. This code sample results in an error about "No mailbox is currently selected", which another issue marked as closed also reported.

Is there a way to fix the "No mailbox is currently selected" error? I would prefer to use that block of code if there is a way to get it working.

Thanks in advance for your assistance,
Jared

[atiertant]

are you using pop or imap protocol ?
if you got this error, this is maybe because connection to server is already closed...
do function in inbox.done already called when you try to delete?

[jeb218]

I am using imap.

I get that error with the other version of the code. See attached for the runkit code, and output.

[atiertant]

need to write a store.on('error', function(err) {}) event and mocha tests for delete.
maybe client or server disconnect before delete is called...

[jeb218]

It tells me that store.on is not a function

[atiertant]

yes, this need to be implement