5.3.5 (2024-04-12)
- deps: Bumped deps (0477e98)
5.3.4 (2024-02-23)
5.3.3 (2024-02-23)
- deploy: fixed git repo url (f8f788f)
5.3.2 (2024-02-23)
- deploy: fixed git repo url (2161a43)
5.3.1 (2024-02-23)
- deploy: include package-lock.json (8363bf4)
5.3.0 (2024-02-23)
- deploy: added autopublish (3e8109f)
- Fix base64 encoding for emoji bytes in encoded words
- Bumped libqp to get rid of
new Bufferwarnings
- Bumped deps
- Removed Travis config
- Added Github actions file to run tests
- Removed optional node-iconv support
- Bumped dependencies
- Updated Travis test matrix, dropped Node 8
- Replace jconv with more recent encoding-japanese
- Use jconv module to parse ISO-2022-JP by default
- Experimental support for node-iconv
- Maintenance release. Bumped deps
- Refactored decoding of mime encoded words and parameter continuation strings
- Updated encoded-word generation. Previously a minimal value was encoded, so it was possible to have multiple encoded words in a string separated by non encoded-words. This was an issue with some webmail clients that stripped out the non-encoded parts between encoded-words so the updated method uses wide match by encoding from the first word with unicode characters to the last word. "a =?b?= c =?d?= e" -> "a =?bcd?= e"
- Revert dot as a special symbol
- Quote special symbols as defined in RFC (surajwy)
- Fixed issue with special symbols in attachment filenames
- Changed handling of base64 encoded mime words where multiple words are joined together if possible. This fixes issues with multi byte characters getting split into different mime words (against the RFC but occurs)
- Fixed an issue with rfc2231 filenames
- Fixed an issue with base64 mime words encoding
- Fix base64 mime-word encoding. Final string length was calculated invalidly
- Replaced jshint with eslint
- Refactored file structure
Added support for emojis in header params (eg. filenames)
Added support for emojis in header params (eg. filenames)
Updated encoded word encoding with quoted printable, should be more like required in https://tools.ietf.org/html/rfc2047#section-5
Changed versioning scheme to use 1.x instead of 0.x versions. Bumped dependency versions, no actual code changes.
Updated unicode filename handling – only revert to parameter continuation if the value actually includes non-ascii characters or is too long. Previously filenames were encoded if they included anything besides letters, numbers, dot or space.
Fixed an issue with encodeWords where a trailing space was invalidly included in a word if the word
ended with an non-ascii character.
Do not use quotes for continuation encoded filename parts. Fixes an issue with Gmail where the Gmail webmail keeps the charset as part of the filename.