Node.js port of Github's email_reply_parser
JavaScript PHP
Switch branches/tags
Nothing to show
#6 Compare This branch is 11 commits ahead of andreascreten:master.
Latest commit 007bc8d Apr 30, 2014 @mko Version bump for NPM
Failed to load latest commit information.
lib Fix detection of inline replies that contain replies. Add test. Apr 30, 2014
.DS_Store NPM prep, version bump Mar 29, 2013
.gitignore proper ignores and package update for NPM Apr 1, 2013
.npmignore proper ignores and package update for NPM Apr 1, 2013
LICENSE Initial commit Jul 3, 2012 Update the readme to show how to run the tests May 10, 2013
package.json Version bump for NPM Apr 30, 2014

Email Reply Parser

Node.js port of Github's EmailReplyParser, a small library to parse plain text email content.

Known Issues

(Taken from Github's version)

Quoted Headers

Quoted headers aren't picked up if there's an extra line break:

On <date>, <author> wrote:

> blah

Also, they're not picked up if the email client breaks it up into multiple lines. GMail breaks up any lines over 80 characters for you.

On <date>, <author>
> blah

Not to mention that we're search for "on" and "wrote". It won't work with other languages.

Possible solution: Remove "" lines...

Weird Signatures

Lines starting with - or _ sometimes mark the beginning of signatures:



Not everyone follows this convention:


Mr Rick Olson
Galactic President Superstar Mc Awesomeville

* Note: blah blah blah                                            *

Strange Quoting

Apparently, prefixing lines with > isn't universal either:



From: Bob []
Sent: Monday, March 14, 2011 6:16 PM
To: Rick

To run the tests

  • Install nodeunit npm install nodeunit
  • Run the tests: nodeunit test/email_reply_parser_test.js