crisp-oss / email-reply-parser

🔎 Node library for parsing plain text email content.

Email Reply Parser

Email Reply Parser is a node library to parse plain-text email replies and extract content

This library supports most email replies, signatures and locales.

😘 Maintainer: @baptistejamin

Who uses it?

Crisp

👋 You use this library and you want to be listed there? Contact us.

Installation

Install the project using NPM:

npm install --save email-reply-parser

Features

This library is used at Crisp everyday with around 1 million inbound emails. Over the years, we improved this library so it can work with most emails.

• Strip email replies like On DATE, NAME <EMAIL> wrote:
• Supports around 10 locales, including English, French, Spanish, Portuguese, Italian, Japanese, Chinese.
• Removes signatures like Sent from my iPhone
• Removes signatures like Best wishes

Usage

var EmailReplyParser = require("email-reply-parser");

var email =  new EmailReplyParser().read(MY_EMAIL_STRING);

console.log(email.getVisibleText());

Contributing

Feel free to fork this project and submit fixes. We may adapt your code to fit the codebase.

You can run unit tests using:

npm test

Credits

• GitHub
• William Durand [email protected]
• Crisp IM

License

email-reply-parser is released under the MIT License. See the bundled LICENSE file for details.

email-reply-parser's Issues

Signature in replies seems to creep in

Happens in different contexts and I could help reproduce. Any general suggestions on how to fix this?

Ping

pong

Issue with parsing Samsung reply

When trying to parse this:

This is pretty awesome, nice work!Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From...

(I excluded the quoted reply, but it is there)

I would expect the output to be:

This is pretty awesome, nice work!

But instead I get the whole text.

I'm not sure what you can do about the Sent from... part because you probably don't want to cut off sentences that just happen to start with "Sent from". But I think you can add optional spaces to the regex and remove the end of line requirement like so:

/^-{1,10} ?Original message ?-{1,10}/

To at least handle the reply.

Request: fragments should have clear body and sender information

Summary

Fragments have a content property. It would be great to have these broken into body and the sender information

Test issue

Test issue

getting invalid ELF header error in amazon lambda

I am deploying a super simple lambda function using serverless.
When I am invoking the function, I get the following error:

{
    "errorType": "Error",
    "errorMessage": "/var/task/node_modules/re2/build/Release/re2.node: invalid ELF header",
    "trace": [
        "Error: /var/task/node_modules/re2/build/Release/re2.node: invalid ELF header",
        "    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1144:18)",
        "    at Module.load (internal/modules/cjs/loader.js:950:32)",
        "    at Function.Module._load (internal/modules/cjs/loader.js:790:12)",
        "    at Module.require (internal/modules/cjs/loader.js:974:19)",
        "    at require (internal/modules/cjs/helpers.js:101:18)",
        "    at Object.<anonymous> (/var/task/node_modules/re2/re2.js:3:13)",
        "    at Module._compile (internal/modules/cjs/loader.js:1085:14)",
        "    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)",
        "    at Module.load (internal/modules/cjs/loader.js:950:32)",
        "    at Function.Module._load (internal/modules/cjs/loader.js:790:12)"
    ]
}

Any idea, how I can resolve the issue as email-reply-parser is the only library is using the re2.node

Thanks in advance

Improve regexes?

Hi I noticed that your regexes use "{0,1}" which is the equivalent to "?" - Is there any reason on why to use this notation instead of a "?"?

Update re2 for node 18

Hi there! Node 18 becomes the LTS version today. Could re2 please be updated to support node 18? The pinned version used by this library doesn't have a version built for node 18