All Collections
SigParser for Developers
Email Parsing APIs
Email Parsing - CLI Executable (Win64 and Linux)
Email Parsing - CLI Executable (Win64 and Linux)
Updated over a week ago

To invoke the executable via the command line you’ll need either a JSON file, EML or an MSG file.

Tip: It’s better to pass multiple files at once to this assembly than to submit one a a time. If you submit one email at a time then it takes about 6 - 10 seconds to process a single email. But the second email in a batch will process in 300 - 500 milliseconds.

Help

Use --help to get help documentation for the various options exposed by the

Invoke Executable

Then call the executable like so:

Parse Email Signature

SigParserEmailUtils signature --filename example.json --filename example.msg --filename example.eml --licensekey 33333-333333-333333-33333

Response Structure

{
"subject": "Re: Great seeing you yesterday",
"from_address": "john@example.com",
"from_name": "John Smith",
"htmlbody": "<body>Hi there, <br/> great seeing you yesterday. <br/>John Smith<br/>Vice President<br/>Mobile 818-334-3433<br> 999 Grand Ave, San Diego, CA, United States<br/>Our mission is to deliver customer satisfaction!</body>",
"plainbody": "Hi there,\r\ngreat seeing you yesterday.\r\nJohn Smith\r\nVice President\r\nMobile 818-334-3433\r\n999 Grand Ave, San Diego, CA, United States\r\nOur mission is to deliver customer satisfaction!",
"date": "2017-01-01T00:00:00",
"to": [
{
"name": "Mark Rogers",
"emailAddress": "mark.rogers@xyz.com"
}
],
"cc": [
{
"name": "Mark Rogers",
"emailAddress": "mark.rogers@xyz.com"
}
],
"options": {
"OutputCleanedEmailHtmlDepth": 0
},
"headers": {
"additionalProp1": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}
}

Split Email

SigParserEmailUtils cleanedemail --filename example.json --filename example.msg --filename example.eml --licensekey 33333-333333-333333-33333

Response Structure

You'll receive an array of objects. The structure of the objects depend on which action you invoked. The model for each object are very similar to our web API but include the filenames. You can optionally have the output written to a file which you can then consume.

Below is an example for splitting two emails.

[
{
"CleanedBodyPlain": "Hi Tony,\r\n\r\nWe getting shawarma tomorrow? \r\n\r\n",
"CleanedBodyHtml": null,
"IsSpammyLookingEmailMessage": false,
"IsSpammyLookingSender": false,
"EmailTypes": [
"NormalEmail"
],
"Emails": [
{
"CleanedBodyPlain": "Hi Tony,\r\n\r\nWe getting shawarma tomorrow? \r\n\r\n",
"CleanedBodyHtml": null,
"Subject": null,
"Date": "2019-01-01T00:00:00",
"FromEmailAddress": "scott.lang@avengers.com",
"FromName": "Scott Lang",
"To": [
{
"Name": "Tony Stark",
"EmailAddress": "tony.stark@avengers.com"
},
{
"Name": "Natasha Romanoff",
"EmailAddress": "natasha@avengers.com"
}
],
"Cc": [
{
"Name": "Bruce Banner",
"EmailAddress": "bruce.banner@avengers.com"
}
]
}
],
"Filename": "example.json",
"Index": 0
},
{
"CleanedBodyPlain": "Hi John,<\\/p>\\r\\n\\r\\n\r\n\r\nLet\\'s get coffee tomorrow.<\\/p>\\r\\n\\r\\n\r\n\r\n",
"CleanedBodyHtml": "<p>Hi John,<\\/p>\\r\\n\\r\\n<p>Let\\'s get coffee tomorrow.<\\/p>\\r\\n\\r\\n<p>",
"IsSpammyLookingEmailMessage": false,
"IsSpammyLookingSender": false,
"EmailTypes": [
"NormalEmail"
],
"Emails": [
{
"CleanedBodyPlain": "Hi John,<\\/p>\\r\\n\\r\\n\r\n\r\nLet\\'s get coffee tomorrow.<\\/p>\\r\\n\\r\\n\r\n\r\n",
"CleanedBodyHtml": "<p>Hi John,<\\/p>\\r\\n\\r\\n<p>Let\\'s get coffee tomorrow.<\\/p>\\r\\n\\r\\n<p>",
"Subject": null,
"Date": "2019-01-01T00:00:00",
"FromEmailAddress": "mary.johnson@fake.com",
"FromName": "Mary Johsnon",
"To": [],
"Cc": []
},
{
"CleanedBodyPlain": null,
"CleanedBodyHtml": null,
"Subject": null,
"Date": "2019-08-29T16:50:00",
"FromEmailAddress": "taylor.ryan@example.com",
"FromName": "Taylor Ryan",
"To": [],
"Cc": []
}
],
"Filename": "example2.json",
"Index": 1
}
]

Did this answer your question?