- Fixed
setEnvelope
. Parse properfrom
andto
addresses from the input instead of storing the input unmodified
- Added new method
setRaw
- Bumped nodemailer-fetch version
- Bumped nodemailer-fetch version
- Fixed an issue with handling
Date
andReferences
header
- Added
prepared
option for the value argument of setheader/addHeader methods
- Reverted setHeader array value handling. Pass array as array for setHeader
- Bumped nodemailer-shared and addressparser versions
- Allow arrays for the
value
argument ofsetHeader
(uses the last element in the array) andaddHeader
(adds all values as separate rows) - Exposed
messageId
method that generates and returns Message-Id value
- Bumped nodemailer-shared version
- Locked dependency versions
- Do not silently swallow errors, instead emit an error event for the stream and stop further processing
- Replaced needle with nodemailer-fetch
- Replaced jshint with eslint
- Removed format=flowed support, uses 7bit for short lines and QP for long lines of plaintext ASCII
- Replaced hyperquest with needle. Bumped major version as needle might behave a little bit different than hyperquest
- Add non-standard name param to content-type header, otherwise non compliant clients like QQ do not understand file names
- Bumped libmime version to get emoji support in filenames
- Fixed a bug where ascii html content was not properly handled
- Updated buildmail for stricter quoted printable encoding
- Only use format=flowed with text/plain and not with other text/* stuff
- Maintenace release, bumped dependency versions
- Maintenace release, bumped libqp which resolves an endless loop in case of a trailing <CR>
- Maintenace release, fixed a test and bumped dependency versions
- Allow functions as transform plugins (the function should create a stream object)
- Bumped libmime version to handle filenames with spaces properly. Short ascii only names with spaces were left unquoted.
- Added new method
getAddresses
that returns all used addresses as a structured object - Changed version number scheme. Major is now 1 but it is not backwards incopatible with 0.x, as only the scheme changed but not the content