SharmaBiswadev

yes, both time seq number are same, searchResults we have not printed, as this issue we are facing in deployed server. Seq number we have printed and both are logging...

Also from the logs, I notice, ``` self.imap.on('mail', function (id) { self.dbg('mail event : %s', id); q.push({name: 'scan', id : id}, function(err) { self.dbg('finished processing scan '+id); }); }); ```...

> If you insert a log statement right inside your `'message'` event handler, does it show up the correct number of times for your search? That will allow us to...

This mail event is not bound to imap, its in global scope which I have used to listen in my server in another file Imap is bound to **self.imap =...

Also I got this error twice. ``` 2019-11-25T05:42:18.599Z - debug: imap Message uid 440 Error: Encoding not recognized: 'ISO-2022-JP' (searched as: 'iso2022jp') at Object.getCodec (/code/server/node_modules/iconv-lite/lib/index.js:106:23) at Object.getDecoder (/code/server/node_modules/iconv-lite/lib/index.js:127:23) at Object.decode...

Ok, for MailParser I raise issue requests.For mail event, could you suggest any solution? I was thinking to store seq number/message id in the database, and not to process duplicate...

While searching using SINCE criteria it still reads mail from older date, as you can see below I have used Nov 27, but when I marked one mail dated Nov...

> Can you post the resulting output when you set `debug: console.log` in your connection config object along with the debug output you already have? Perhaps the two together will...