From b11855435b9025437334d20f5ea0f491329f6b25 Mon Sep 17 00:00:00 2001 From: Stephanie Elliott <31225194+stephanieelliott@users.noreply.github.com> Date: Thu, 7 Nov 2024 17:18:11 -1000 Subject: [PATCH] Update docs/articles/expensify-classic/settings/Set-Notifications.md Co-authored-by: Rafe Colton --- docs/articles/expensify-classic/settings/Set-Notifications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/articles/expensify-classic/settings/Set-Notifications.md b/docs/articles/expensify-classic/settings/Set-Notifications.md index d729769d9ae0..255374d0fe03 100644 --- a/docs/articles/expensify-classic/settings/Set-Notifications.md +++ b/docs/articles/expensify-classic/settings/Set-Notifications.md @@ -64,6 +64,6 @@ The problem typically arises when our domain or one of our sending IP addresses ## What is the best way to ensure emails are not accidentally marked as Spam? -For server-level spam detection, it’s best to use DKIM and SPF verification rather than solely relying on the sender’s IP address. Expensify's emails are signed and encrypted to prevent spoofing. +For server-level spam detection, the safest approach to allowlisting email from Expensify is to verify DKIM and SPF, rather than solely relying on the third-party reputation of the sending IP address. {% include faq-end.md %}