We recently had our own email system block a campaign email as a phishing attempt. Our IT department investigated and found the combination of the trk.klclick.com and xxxxxx.cloudfront.net addresses in the message triggered the block (xxxxxx being a seemingly random combo of letters… didn’t know if it was sensitive or not).
I searched and found the directions for setting up our own custom click tracker domain to replace trk.klick.com, but could find nothing about the cloudfront.net address. If we replace trk.klick.com will that be enough to avoid the phishing block? If cloudfront.net is also contributing to blocks and spam designations, is there a workaround for it as there is for trk.klick.com?
Best answer by David ToView original