There’s no straightforward answer to this. Nothing is stopping an automated system reading the link and visiting it.
You could implement a two-step process.
One way is to have a link sent to the email, when clicked displays a page with the two yes/no links, and the user has to click on the buttons there (instead of from the email).
there is no option to prevent scanning or previewing links,
you have the option to set pre defined whitelist of an IP ranges to allow specific ip to trigger the hook in the IP restrictions text box
then you can see which user-agent is using by the email platform…
for example slack expanding urls which triggers the scenarios but in the header they use:
{
“name”: “user-agent”,
“value”: “Slackbot-LinkExpanding 1.0 (+https://api.slack.com/robots)”
},
then you can add a filter to ignore triggers that contains the header Slackbot-LinkExpanding
example:
I think this wouldn’t help. What op is looking for is more like a blacklist (exclusion list) instead of an inclusion list, provided you even know which IP addresses the “scanning” servers are on!