When you setup a custom domain email and forward it thorugh KaiMail, it DOES break DKIM of the sender since we're adding headers, through our own custom headers and the hops. The question is: Will it matter within the scheme of email authentication?
The key point here is ARC (Authenticated Received Chain) sealing: This is usually the hardest part of email forwarding. When we send out the email, we sign it with our own key for DKIM and then also sign it for ARC. From the recipient's point of view, the email is authenticated, is not tampered with along the way and was proven to originate from where it says it came from. You can read more about ARC on our blog here.
Kafkai
How do you guys will handle spam especially for webhooks? Congrat on the launch btw.
Kafkai
@koditi Thanks. Spam comes with the territory when you deal with emails unfortunately, and we currently have a roadmap for this. There are already established best-practices within the industry that help with this problem such as checking for DKIM, ARC or SPF records which can be implemented on the SMTP level, that is where we will work on first. Those alone can stop a bulk of the spam, but beyond that will require a more dedicated filtering system, which requires reading the contents of the email. Due to the nature of the topic, it will be unwise to divulge more than that at this point.