Sender Header behavior updates
- Phil Evans
What has changed?
The Sender address headers setting found in Profile > Project Mapping/Rule > Email Only Users.
Summary of changes:
Sender address headersare tested sequentially until a valid sender address is found (passingProfille > Included/Excluded Senderschecks)If no Sender Headers are configured it falls back to
FromthenReply-Torather than justFromIf a sender address matches both Included and Excluded Senders then it is deemed valid
Newly created Project Mappings and Rules will have Sender Headers set to
FromandReply-To
Am I affected?
You had no Sender Headers configured in your project mappings
Previous behaviour | New behaviour |
|---|---|
Falls back to use the | Falls back to using |
To replicate previous behaviour, set From in the Sender address headers setting.
You had Included Senders or Excluded Senders configured
Previous behaviour | New behaviour |
|---|---|
If an included sender is not found in the first configured Sender Header, message is immediately handled as per Profile Exclusion Action | If an included sender address is not found, subsequent Sender Headers (if present) will be tested against Included/Excluded Senders |
If an excluded sender is found in the first configured Sender Header, message is immediately handled as per Profile Exclusion Action | If an excluded sender address is found, subsequent Sender Headers (if present) will be tested against Included/Excluded Senders |
To replicate previous behaviour, use a Scripting feature such as Script Field Processor.
JavaScript snippet example of enforcing an outcome based on a single header value
The JavaScript example below is related to Exclusions and From header ( if you require Reply-To change to Reply-To). To instead check for inclusions invert the isHeaderExcluded condition check.
Script
const headerValue = message.getHeader('From').toString();
const isHeaderExcluded= headerValue.match('.*@excludeme.com');
if (isHeaderExcluded) {
setOutcome('DROP','Because matches .*@excludeme.com regex');
}