SPF, DKIM, and DMARC are checked by the receiving domain, so if someone sends email from that domain to that domain, (i.e. from inside the company), then they automatically pass because the domain has checked that they are who they say they are. If the sender is from another domain from the company (recipient) domain, then that company domain is responsible for checking the SPF, DKIM and ultimately the DMARC. Most sites have it set to quarantine or discard the email if they don't pass, but the important thing is that if they don't pass, they are marked as such and my code checks those parms to make sure the sender passed. If not, the email is discarded and an automation event is created that can be handled in several ways (message, email, delete ID, etc.) that is up to the site to decide which they want to do.
The security part of this is fairly solid and aside from deciding what to do with IDs that try to use it and aren't authenticated, it's up to the site to decide what they want me (meaning the software) to do about handling those events. What I'm looking for is things that I might have missed beyond security. I am pretty confident in the security side of this. Brian On Tue, 25 Aug 2026 17:14:09 +1000, Andrew Rowley <[email protected]> wrote: >On 25/08/2026 3:14 pm, Brian Westerman wrote: >> The intent is not really to allow email addresses from GMAIL or hotmail. >> For the most part, I think the email addresses would be the ones the company >> running the automation software assigns. Theoretically, they would be >> sending it from their company server. > >Is that true though? If they use services like e.g. Atlassian or >Salesforce they may have it set up to use the company domain for >outgoing email. SPF, DKIM and DMARC authorise the sender to send from >the domain but aren't really designed to authenticate the "from" id. You >probably trust those companies and the administrators who set the email >id used, but it's not really intended to work that way. > >A Gmail id is probably pretty safe, Google are strict about >authenticating senders and their SPF, DKIM and DMARC so it's probably >safer than from a company domain. > >-- >Andrew Rowley >Black Hill Software > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
