hMailServer B2425 Anti-spam Whitelisting Failure
Posted: 2019-06-21 06:09
I just recently Whitelisted *@fedex.com under the Anti-spam tree option in hMailAdmin.
1. I received an email from 'TrackingUpdates@fedex.com' (no quotes) which was marked as SPAM by hMailServer due to the SPAM Threshold Mark level being met.
2. Whitelisting is supposed to cause the Anti-spam processing to not be performed.
3. Checking the hMailServer Logs, I see where the Anti-spam processing took place.
a. hMailServer checked the Blacklists.
b. SPF and DKIM tests were performed and the DKIM Test failed generating a SPAM Score of 5 for the failure.
c. As per the current Help Documentation these tests were not to be performed due to '*@fedex.com' being Whitelisted.
4. I can see one possibility for hMailServer performing the SPAM Tests.
a. The Return Path in the Message Headers was 'prvs=4073a73a4e=bounce@nds.fedex.com'. hMailServer I believe examines the Message that it receives without examining the originating Sender's Email ID. This would
cause the Anti-spam tests to be performed.
b. As per the current Help Documentation for Whitelisting when specifying the Whitelisted Email ID or Domain for the IP Range specified if 'Forwarding Relay' is specified then hMailServer will use the Received Headers of the
email to determine the originating Email Id which in this case should have been 'TrackingUpdates@fedex.com'.
'•If you have selected "Forwarding relay" in the IP range the sender is connecting from, hMailServer will use the Received-headers of the email to determine the originating email IP address.'
c. I have looked at the Whitelist record information and the 'Forwarding Relay' specification does not appear in the Whitelist record as an available entry to be made.
Can anyone advise where the 'Forwarding Relay' selection is as this would appear to be the reason why the Anti-spam processing was not bypassed?
1. I received an email from 'TrackingUpdates@fedex.com' (no quotes) which was marked as SPAM by hMailServer due to the SPAM Threshold Mark level being met.
2. Whitelisting is supposed to cause the Anti-spam processing to not be performed.
3. Checking the hMailServer Logs, I see where the Anti-spam processing took place.
a. hMailServer checked the Blacklists.
b. SPF and DKIM tests were performed and the DKIM Test failed generating a SPAM Score of 5 for the failure.
c. As per the current Help Documentation these tests were not to be performed due to '*@fedex.com' being Whitelisted.
4. I can see one possibility for hMailServer performing the SPAM Tests.
a. The Return Path in the Message Headers was 'prvs=4073a73a4e=bounce@nds.fedex.com'. hMailServer I believe examines the Message that it receives without examining the originating Sender's Email ID. This would
cause the Anti-spam tests to be performed.
b. As per the current Help Documentation for Whitelisting when specifying the Whitelisted Email ID or Domain for the IP Range specified if 'Forwarding Relay' is specified then hMailServer will use the Received Headers of the
email to determine the originating Email Id which in this case should have been 'TrackingUpdates@fedex.com'.
'•If you have selected "Forwarding relay" in the IP range the sender is connecting from, hMailServer will use the Received-headers of the email to determine the originating email IP address.'
c. I have looked at the Whitelist record information and the 'Forwarding Relay' specification does not appear in the Whitelist record as an available entry to be made.
Can anyone advise where the 'Forwarding Relay' selection is as this would appear to be the reason why the Anti-spam processing was not bypassed?