My understanding is that SPF, DKIM and DMARC are more about who is authorised to send email at the domain level rather than authenticating an address. That might include external organizations, e.g. marketing and might be wider than you really want for security. Also email is usually delivered quickly but can be delayed, so there is some danger that a message is received hours or even days later.

Responding to an event sounds a more likely prospect than unsolicited automation actions. Then you could e.g. have a random key in the email to include in a reply to authenticate it. Make it time limited and single use. Responding via SMS might be more useful - maybe you already offer that?

On 24/08/2026 4:14 pm, Brian Westerman wrote:
I keep a table information from the last 1,000 emails that were processed and 
do several checks on them to make sure things are secure, but the most 
important part of security is the email address that has to be pre-approved on 
the mainframe side that they use and that it is the one attached to the site 
that we allow requests from and that they also passed the SPF, DKIM and DMARC 
tests which make it unlikely that they were bogus.

Brian

--
Andrew Rowley
Black Hill Software


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to