Releases: arithmetric/aws-lambda-ses-forwarder
Releases · arithmetric/aws-lambda-ses-forwarder
v6.0.0
v5.1.0
- Updating documentation about using Node.js 16 or 18 AWS Lambda runtimes.
- Updating tests to support Node.js 16 and later.
v5.0.0
- Adding
allowPlusSignconfiguration flag that when enabled ignores suffixes
after a plus sign in email addresses. For example, an email addressed to - Adding support for a catch all mapping by using "@" as the key.
[email protected]is treated as if addressed to[email protected]. - Fixing handling of emails with less common header formats, such as where there
is no space in the header after the colon and before the value. - Updating aws-sdk dependency to match AWS Lambda environment.
v4.2.0
- Removing
Message-IDheader from messages to fixInvalidParameterValue: Duplicate header 'Message-ID'errors. - Fixing handling of multiline
Fromheaders to fixInvalidParameterValue: Extra route-addrerrors. - Updating documentation for SES endpoints.
- Updating aws-sdk dependency to match AWS Lambda environment.
v4.1.0
- Added
toEmailconfiguration for replacing theToheader recipient to a defined email address. - Changed AWS.S3() implementation to use signature version v4 for compatibility with S3 EU-based regions.
v4.0.0
- Updated for the Node.js 4.3 runtime.
- Refactored steps to use promises.
Upgrade Notes
- The Node.js 4.3 Lambda runtime is required for this version.
- The arguments for the handler function have changed to match the Lambda
runtime for Node.js 4.3 to include a callback function. If invoking the
handlerfunction, be sure to include the callback function provided in the
Lambda runtime environment. - Step functions that include asynchronous operations should return a promise,
and are no longer provided a callback function as an argument. Upon successful
completion of the step function, callPromise.resolve()with thedata
argument given to the step function. (Step functions that are synchronous should
return thedataargument.)
v3.2.0
- Added capability to specify an email forwarding mapping based on a mailbox name across all domains (i.e. forward mail sent to
foo@*). - Added documentation to resolve "Could not write to bucket" error.
- Updating aws-sdk dependency to match AWS Lambda environment and other dev dependencies.
v3.1.0
- Adding
subjectPrefixconfiguration for adding a prefix string to the subject
of forwarded email. - Updating regex match for the Reply-To header to be case insensitive to support
email sent with a Reply-to header. - Fixing how libraries are loaded to improve performance.
v3.0.0
- Adding capability to specify an email forwarding mapping that acts as a
wildcard or catch-all for a domain. - Converting the inbound recipient email address to lowercase before comparing
to the forwarding map to handle case variations. - Updating aws-sdk dependency to match AWS Lambda environment.
Upgrade Notes
- Email addresses and domain wildcard keys in the
forwardMappingconfiguration
object must be lowercase.
v2.3.0
- Adding configuration option for a static "From" email address.