Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / nodemailer/mailparser issues and pull requests
#277 - Attachments Broken
Issue -
State: closed - Opened by DiegoMajluf about 4 years ago
- 1 comment
#276 - Version history?
Issue -
State: open - Opened by thenitai about 4 years ago
- 3 comments
#275 - html=false with 3.0.0
Issue -
State: closed - Opened by ghost about 4 years ago
- 3 comments
#274 - Attachments broken with stream input
Issue -
State: closed - Opened by andreme about 4 years ago
- 6 comments
#273 - Fix #272: Throw TypeError for invalid input.
Pull Request -
State: closed - Opened by dipasqualew about 4 years ago
- 1 comment
#272 - Fails mysteriously if `simpleParser` input is null/undefined.
Issue -
State: closed - Opened by dipasqualew about 4 years ago
- 1 comment
#271 - Fix unhandled exception due to invalid punycode in address strings
Pull Request -
State: closed - Opened by cwill about 4 years ago
- 1 comment
#270 - EXIM bounce messages, content part containing original message not parsed
Issue -
State: closed - Opened by eBulldog over 4 years ago
- 3 comments
#269 - TypeError: __webpack_require__.i(...) is not a function
Issue -
State: closed - Opened by Oussama-Abderrahim over 4 years ago
- 1 comment
#268 - Fix invalid date checking
Pull Request -
State: closed - Opened by andrejewski over 4 years ago
- 3 comments
#267 - How the parse the Replied message i receive and segregate properly
Issue -
State: closed - Opened by chetanpatel6 over 4 years ago
- 1 comment
#266 - Add config option to specify whether carriage returns should be prese…
Pull Request -
State: closed - Opened by UsamaAshraf over 4 years ago
- 2 comments
#265 - add and use new config option to specify whether carriage returns should be preserved in text and html parts, or not
Pull Request -
State: closed - Opened by UsamaAshraf over 4 years ago
#264 - Parsing message/global-delivery-status as attachment
Issue -
State: closed - Opened by DemChing over 4 years ago
- 3 comments
#263 - MailParser block forever with email multipart / rfc822 when bad closing mutli part boundary
Issue -
State: closed - Opened by acemtp over 4 years ago
- 10 comments
#262 - Performing extremely slowly on average messages
Issue -
State: closed - Opened by cuuupid over 4 years ago
- 3 comments
#261 - [bug] Error: Incomplete character sequence (decoding `Iconv` issue)
Issue -
State: closed - Opened by niftylettuce over 4 years ago
- 1 comment
#260 - Is there harm in calling release() early?
Issue -
State: closed - Opened by nickzelei over 4 years ago
- 1 comment
#259 - Err (Node.js) extension is not a function
Issue -
State: closed - Opened by Bluetoothbrot over 4 years ago
- 1 comment
#258 - Double encoded messages
Issue -
State: closed - Opened by tajinder over 4 years ago
- 4 comments
#257 - UTF encoded name is parsed wrong
Issue -
State: closed - Opened by spech66 over 4 years ago
- 1 comment
#256 - How can I parse individual header values?
Issue -
State: closed - Opened by aguynamedben over 4 years ago
- 1 comment
#255 - Strange characters output in HTML
Issue -
State: closed - Opened by mattgaspar almost 5 years ago
- 1 comment
#254 - simpleParser should handle the 'error' event emitted by MailParser
Issue -
State: closed - Opened by deepakprabhakara almost 5 years ago
- 1 comment
#253 - "input.once is not a function"
Issue -
State: closed - Opened by iv-med almost 5 years ago
- 2 comments
#252 - Not parsing multipart email properly
Issue -
State: closed - Opened by yashgandhi32 almost 5 years ago
- 1 comment
#251 - Attachments with uuencode transfer encoding not being decoded
Issue -
State: closed - Opened by tajinder almost 5 years ago
- 2 comments
#248 - optional mailparser for browser
Issue -
State: closed - Opened by nutphi almost 5 years ago
- 2 comments
#244 - Misdecoded Content-Disposition header
Issue -
State: closed - Opened by dynamicnet almost 5 years ago
- 2 comments
#243 - When is HtmlToText used
Issue -
State: closed - Opened by jspruyt almost 5 years ago
- 3 comments
#237 - Mailparser consistently leaks memory
Issue -
State: closed - Opened by grzegorzj about 5 years ago
- 3 comments
#222 - possible optimized version of simpleParser by optionally skipping readable and read only headers
Issue -
State: closed - Opened by ciekawy over 5 years ago
- 2 comments
#221 - Backward incompatible changes introduced in v2.7.0
Issue -
State: closed - Opened by f-w over 5 years ago
- 5 comments
#141 - Outlook .msg attachment corrupted after passing by mailparser
Issue -
State: closed - Opened by melimanrique over 8 years ago
- 13 comments
#86 - Text of email is not properly decoded
Issue -
State: closed - Opened by mbrio over 10 years ago
- 4 comments