Is this module released under a license?

Hello guys,

How could I close the connection after all the emails has been read ?

The connection stops without being caught either by "end" or "error" events.

Debug log:

mailnotifier no new mail in INBOX +0ms
imap => 'IDLE IDLE' +0ms
imap <= '+ idling' +71ms
imap [connection] Closed +30s
mailnotifier imap close : errored +1ms

Maybe add
self.emit('end');
in self.imap.once('close') ?

After losing a connection (catching 'end' event) I try to reconnect in 30 seconds.
Then the connection established, I get not one but two, three or more connections to imap server.
This happens because of not disconnecting imap after 'end' or 'error'.
I try to stop before each start of notifier but it not works, because notifier checks self.connected, so I removed this check from Notifier.prototype.stop and all works fine for me.
Can you fix this, or give an example how to reconnect to server after losing or some another ending of connection.

HI,
Not exactly an issue, but is there a way to save the mail object to eml file.
Basically the raw data from the email object.

Hi,
I'm getting some error recently, it may be connected with imap module, but I'm putting the issue here. I'm getting such message very often while I'm trying to connect to my mailbox:

2013-03-26 1424:31.855 :: 'mail-noitifier' module started
Error: Unable to connect. Reason: Error: connect ECONNREFUSED
    at Socket.errorHandler ([my_project_path]/node_modules/mail-notifier/node_modules/imap/imap.js:139:15)
    at Socket.EventEmitter.emit (events.js:96:17)
    at Socket._destroy.self.errorEmitted (net.js:329:14)
    at process.startup.processNextTick.process._tickCallback (node.js:245:9)
2013-03-26 1424:31.861 :: Error: connect ECONNREFUSED
Error: connect ECONNREFUSED
    at errnoException (net.js:770:11)
    at Object.afterConnect [as oncomplete] (net.js:761:19)

If I'll run the app the second or the third time, everything works fine, but it quite annoying. Any ideas?

Hi Team,

Can we use gmail auth token in mail-notifier module

I am running this node module at version "^0.4.1", and I am getting the "Type Error: mime.extension is not a function" issue on some emails. I have reinstalled the dependancy since the fix for Issue #43 was applied, but I am able to reliably recreate the issue when I receive a calendar update/invite from Google Calendar, due to the formatting of their emails.
Any help on this would be greatly appreciated!

I had error leading to page informing about wrong password or username:

But when I logged in by browser using the same username and password I have seen e-mail from google about suspicious login try. More info on page:

https://support.google.com/accounts/answer/2506340?authuser=5&p=sign_in_prevented_csa2&hl=en&authuser=5&visit_id=636746614951011840-2742808467&rd=1

Unusual sign-in location detected
Why you must complete an additional step to sign in

We've detected that you're signing in from a different location than you normally do, and we want to make sure that someone else isn't trying to access your account.
If you can’t provide the information requested

If you can’t verify your identity by providing the information requested, you can also access your account by resetting your password.
How this additional step protects your account

The additional step at sign in is designed to prevent an unauthorized person who does not know you from accessing your account, even if they've obtained your username and password. While this won't necessarily stop people who know you from accessing your account (for that, try 2-step verification), it's an important measure to keep hijackers who have a long list of passwords from doing malicious things with your account, such as creating spam or accessing and deleting valuable data.
Examples of additional steps

Below are some examples of the additional steps we’ll ask you to complete in order to help verify your identity. Depending on the recovery options you’ve previously set up, some examples might not be applicable to your account.

    Answering your secret question
    Verifying your phone number
    Entering a code we’ll send you via SMS or voice message
    Verifying your recovery email address
    Verifying a previous location from where you’ve signed-in

 

If you think you should not have been asked to complete this step or have other comments for us, please send us your feedback.

How to prevent occurring this error?

Hi,

There seems to be a disconnect between the version you have here and the one published on npm (https://www.npmjs.org/package/mail-notifier).

Can you please push your changes to npm?

Thank you.

What is the suggested version for usage?

Reason why I suggest this is that right now, mail-notifier may try to fetch over 1000 emails at a time depending on your search query, which often overloads a server, meaning that the server will return an invalid command, as it's unable to process that many emails.

Considering how the code is written, you could split up the uid list into smaller lists and only fetch the emails assigned those uids and process those before moving onto the next set of uids.

Setting the version to "0.2.5" in package.json and running npm install throws an error: "No compatible version found: [email protected]". I'm currently using Node version 0.10.26 and npm version 3.5.1. Could you maybe give me a heads up?

Receive only new email will be good to have feature, now when I start its looping through all the mails.

i want to read unread mails from multiple mail accounts with some interval times. how can i do please help.

/var/www/vhosts/chattet.de/maiwell-mail.chattet.de/node_modules/mail-notifier/index.js:117
2|simple-m | Notifier.prototype.dbg = function (...args) {
2|simple-m | ^
2|simple-m | SyntaxError: Unexpected token .
2|simple-m | at Module._compile (module.js:439:25)
2|simple-m | at Object.Module._extensions..js (module.js:474:10)
2|simple-m | at Module.load (module.js:356:32)
2|simple-m | at Function.Module._load (module.js:312:12)
2|simple-m | at Module.require (module.js:364:17)
2|simple-m | at require (module.js:380:17)
2|simple-m | at Object. (/var/www/vhosts/chattet.de/maiwell-mail.chattet.de/node_modules/mail-notifier/sample/simple-mail-notifier.js:1:78)
2|simple-m | at Module._compile (module.js:456:26)
2|simple-m | at Object.Module._extensions..js (module.js:474:10)
2|simple-m | at Module.load (module.js:356:32)

Hi. I use the imap and mailparser modules in my code. I just tried cutting and pasting the sample code in the documentation for mail-notifier. I changed the parameters in the imap variable to use the correct email configuration (same params that work in my existing code). Every time I run this I get:

Error: Connection timed out
at ImapConnection._fnTmrConn (/Users/rich/source/node/notifier/node_modules/mail-notifier/node_modules/imap/imap.js:898:11)
at timer._onTimeout (timers.js:210:16)
at Timer.listOnTimeout as ontimeout

I looked in the node_modules directory and you are using imap 0.3.2. The current version is 0.8.9. That's a pretty big gap. I took a look at your source code and it doesn't look all that hard to upgrade. I don't have time today but I could take a shot at doing the upgrade if you'd like?

In five or ten minutes after run the script mail-notifier does not check any new emails

Is there any way to set a timeout?
Also, I want to disconnect after checking for mails (if there's mail, after getting them, if there's not after checking). Is there any option to do this?

Thanks.

There are sometimes up to a few minutes until received mail is acknowledged.

Is there a way to speed it up?

EDIT: There is nothing to do with the code block below (with if(mail.attachments), it has problem without it as well)

I basically try the code on #16

notifier(imap)
  .on('mail', mail => {
    console.log(mail);
    if(mail.attachments) {
        mail.attachments.forEach(function(attachment){
          console.log('attachment.generatedFileName',attachment.generatedFileName)
            var bufferStream = new stream.Transform();
            bufferStream.push(attachment.content);
            var output = fs.createWriteStream('/tmp/' + attachment.generatedFileName);
            bufferStream.pipe(output);
        });
    }
  })
  .start();

I try an email with a basic image attachment and I got this error:

/Users/yasin/dev/maildeneme/node_modules/mail-notifier/node_modules/mailparser/lib/mailparser.js:1407
        defaultExt = mime.extension(contentType);
                          ^

TypeError: mime.extension is not a function
    at MailParser._generateFileName (/Users/yasin/dev/maildeneme/node_modules/mail-notifier/node_modules/mailparser/lib/mailparser.js:1407:27)
    at MailParser._processStateHeader (/Users/yasin/dev/maildeneme/node_modules/mail-notifier/node_modules/mailparser/lib/mailparser.js:309:61)
    at MailParser._process (/Users/yasin/dev/maildeneme/node_modules/mail-notifier/node_modules/mailparser/lib/mailparser.js:227:22)
    at runCallback (timers.js:800:20)
    at tryOnImmediate (timers.js:762:5)
    at processImmediate [as _immediateCallback] (timers.js:733:5)

Not sure what's happening. Just using the normal example code, and it's marking my mail as read. Any way to fix this?

Hi,

Good day.
Just wanted to inform that we encountered a security issue on one of mail-notifier dependency for its version 0.5.0:

Dependency: semver
Version: 5.3.0

It is raised under this CVE ID: CVE-2022-25883

If this was already discussed and resolution was already delivered. Let us know.
Thank you.

I'm getting these errors logged when receiving certain emails.

Error: Encoding not recognized: 'UTF-32LE' (searched as: 'utf32le')
    at Object.getCodec (.\node_modules\iconv-lite\lib\index.js:106:23)
    at Object.getDecoder (.\node_modules\iconv-lite\lib\index.js:127:23)
    at Object.decode (.\node_modules\iconv-lite\lib\index.js:40:25)
    at convertIconvLite (.\node_modules\encoding\lib\encoding.js:91:26)
    at convert (.\node_modules\encoding\lib\encoding.js:51:22)
    at Object.decodeBase64 (.\node_modules\mimelib\lib\mimelib.js:257:16)
    at Object.decodeMimeWord (.\node_modules\mimelib\lib\mimelib.js:330:25)
    at Object.module.exports.decodeMimeWord (.\node_modules\mimelib\lib\mimelib.js:64:41)
    at MailParser.<anonymous> (.\node_modules\mail-notifier\node_modules\mailparser\lib\mailparser.js:1395:24)
    at String.replace (<anonymous>)

Hi there,

Updated to 0.2.0 and now it doesn't work anymore. Changed the secure to tls with tlsoption and at least now it can sign in to email again but not into the mailbox (it that makes any sense).

0.2.0 shows:
Express server listening on port 3000
28 Mar 16:35:42 - no new mail in INBOX

0.1.1 shows:
Express server listening on port 3000
28 Mar 16:35:41 - successfully opened mail box
28 Mar 16:35:42 - no new mail in INBOX

0.1.1 successfully fetches emails and parses them where as 0.2.0 does nothing. No erros anywhere to be seen.

I'm trying to do something when the connection is establish, but the event don't seem to work for me. I'm recieving my mails but this event won't work.

Alternative :

`
var notifier = require('mail-notifier');

var imap = { // your configs ...}

notifier = notifier(imap);

notifier.on('mail', function(mail) { // do something.. }

notifier.start();

notifier.imap.on('ready', function() { // You are now connected! });

`

const imap = {
user: "yourimapuser",
password: "yourimappassword",
host: "imap.host.com",
port: 993, // imap port
tls: true,// use secure connection
tlsOptions: { rejectUnauthorized: false }
box:['INBOX','SPAM'] // is it correct ?
};

i was trying to read the body but when i check the
message: mail.text && mail.text.replace(/\s/g,'').length > 0? mail.text : 'No Message body',
it syas that mail.text is undefined and thus automaticly says no message body. please help

If markSeen is equal to false and i have 5 unread emails and a new email comes in, it triggers the on mail function 6 times, 5 for the existing unread emails and once for the new email.

Is this a feature or a bug... bug for my use case anyway

I was trying to get the list of sent emails by changing box option to [Gmail]/Sent Mail, but i didn't get any response,
on the other hand INBOX works fine

if u have any suggestions or corrections, i need your help
thanks

i'm using the module to check an exchange mail box, but on 1000/1200 messages received per day, i've got more than 100/150 duplicates notifications.
anyone the same issue ?
thanks

If I have an error event attached, it somehow doesn't seem to trigger. All I'm getting is the "normal" error message, but I can't catch the error.

Am I doing this wrong?

notifier(imap_notifier).on('mail', function(mail){
    // Get the to address
    var _to = mail.to[0].address;
    // Call method to fetch and parse messages
    _connectMe(_to);
}).start();

notifier(imap_notifier).on('error', function(err){
     log.error('There is an error connecting to the IMAP server. Please check your setting!', err);
});

Does this library support OAuth (Azure MSAL) to access a specific email?

For instance, given the email [email protected] I can't connect directly with username and password but I need to obtain a JWT Token using client ID/client secret (already given) and then insert the token into the header of each request.

More info:
https://www.npmjs.com/package/@azure/msal-node
https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-v2-libraries

I am trying to implement, email notifier for outlook IMAP. As soon as the IMAP server receives an email, my nodejs code need to process that.

This is how I am listening to mail event.

imap.openBox('INBOX', false, function (err, box) {
if (err) {
console.log("Error oppening inbox");
} else {
imap.on('mail', function (numNewMsgs) {
console.log("messages has arrived");
fetchMessages(imap);
});
}
});

// This is the code to fetch new email which is unseen and has recent flag
function fetchMessages(imap) {

var query = imap.search(['UNSEEN', 'RECENT'], function (error, results) {
if (error) { console.log("ERROR imap.search"); throw err; }

  if (results.length <= 0) return;

  var fetchQuery = imap.fetch(results, { bodies: '', markSeen: true });

  fetchQuery.on('message', function (msg, seqno) {
     // parseMessage(msg, seqno);
     console.log('New mail received.');

     var uid, flags;

     msg.once('attributes', function (attrs) {
        uid = attrs.uid;
        flags = attrs.flags;
     });

     var mp = new MailParser();
     mp.once('end', function (mail) {
        mail.uid = uid;
        mail.flags = flags;
        console.log("new email from mail parser");
        //self.emit('mail', mail);
        //self.dbg('found mail '+mail.headers["message-id"]);
     });

     msg.on('body', function (stream, info) {
        stream.pipe(mp);
     });

     msg.once('end', function () {
        // console.log(prefix + 'Finished');
     });
  });

  fetchQuery.once('error', function (err) {
     console.log('Fetch error: ' + err);
  });

  fetchQuery.once('end', function () {
     console.log('Done fetching all messages');
     imap.end();
  });

});
}

My problem is, the first time when I start my node js server, I am able to receive the "mail" event, but after that, I see I don't get any mail notification. It requires me to restart the node js server.

Based on my speculation I found, fetch query "end" event never gets fired.

I tried IMAP.seq.fetch query example from the git hub which works fine, I see end event, but here with imap.fetch I don't get end event.

Note: I am testing this on Outlook IMAP. (Gmail IMAP is working fine for me.)
Please let me know what I am doing wrong. Thanks in advance.

throw er; // Unhandled 'error' event
^

Error: socket hang up
at TLSSocket.onHangUp (_tls_wrap.js:1135:19)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:111:20)
at TLSSocket.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1055:12)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)

It seems strange how this project is handling the releases, the current version is 0.5.0 where some commits that currently resides in the master branch are not there, like emitting an end when a connection is closed. this is a critical fix IMO, so adding this by repo gives a version of 0.4.1 which is really strange.

Anyone has an idea about the versioning control in this project ?

I'm looking to be able to trigger a message when successful connection to the IMAP server occurs. This is something the outdated mail-listener2 module provided. Is there anyway to get this out of the existing implementation? If not, any plans to add this? I can take a look at creating a PR I just don't have time to dig through the code at the moment.

Thanks!

I have two unread mail in mail box but the mail event triggered 4 times.

I was wondering if there is a method that gets triggered or ways to loop over all mails once all email/attachments have been read so an external process can start?

I am getting ReferenceError: self is not defined error when i use stop()

EDIT:
i think because the npm package is not updated, the github & the npm version is different

https://github.com/jcreigno/nodejs-mail-notifier/blob/master/index.js#L106 in not included on the npm version

please update npm and close this issue
thanks

It would be better to set connected to false before emitting 'end' event and checking if imap is connected before emitting 'error' event.

I've been using mail-notifier for testing email delivery in some e2e tests using protractor. In general the library is working as expected; however, I am noticing when I try to run three listeners at once I am running into issues in that all the listeners throw, 'Error: LOGIN failed.'; however, two listeners appear to be working fine. Below is my sanitized code for my email util. I am starting the mail listeners before the execution of my test cases and simply checking the arrays in my test cases. Any help is appreciated!

const temp00Notifier = require('mail-notifier');
const temp01Notifier = require('mail-notifier');
const temp02Notifier = require('mail-notifier');

const temp00RecievedEmails: Array<object> = [];
const temp01RecievedEmails: Array<object> = [];
const temp02RecievedEmails: Array<object> = [];

export async function startTemp00MailListener() {
  const imap = {
    user: '[email protected]',
    password: 'Password',
    host: 'sampleHost.com',
    port: 993,
    tls: true,
    tlsOptions: { rejectUnauthorized: false },
  };
  await temp00Notifier(imap).on('mail', (mail: any) => temp00RecievedEmails.push(mail)).start();
}

export async function startTemp01MailListener() {
  const imap = {
    user: '[email protected]',
    password: 'Password',
    host: 'sampleHost.com',
    port: 993,
    tls: true,
    tlsOptions: { rejectUnauthorized: false },
  };
  await temp01Notifier(imap).on('mail', (mail: any) => temp01RecievedEmails.push(mail)).start();
}

export async function startTemp02MailListener() {
  const imap = {
    user: '[email protected]',
    password: 'Password',
    host: 'sampleHost.com',
    port: 993,
    tls: true,
    tlsOptions: { rejectUnauthorized: false },
  };
  await temp02Notifier(imap).on('mail', (mail: any) => temp02RecievedEmails.push(mail)).start();
}

export async function getTemp00RecievedEmails() {
  return temp00RecievedEmails;
}

export async function getTemp01RecievedEmails() {
  return temp01RecievedEmails;
}

export async function getTemp02RecievedEmails() {
  return temp02RecievedEmails;
}

How would i have to go about downloading attachments in new emails if they exist when i get notified of a new email

{ Error: read ECONNRESET at _errnoException (util.js:1019:11) at TCP.onread (net.js:608:25) code: 'ECONNRESET', errno: 'ECONNRESET', syscall: 'read', source: 'socket' }

I see those constantly. What's causing it?

I understand that mail-notifier is using mailparser under the hood but the option of streamAttachments is not exposed in this module that would allow for streaming of attachments rather than giving us buffers which can be a headache.