Some emails from sfPMS go to the recipient’s SPAM folder. Can I reduce the odds of that happening?
There is no perfect solution. The easiest is to have the recipients add your sending domain to their safe-senders list—that way, all the emails from your organization are “safe” (not just the ones from sfPMS). But this solution is one-to-one. It does nothing to help with the next recipient.
To reduce the probability that your emails are treated as SPAM and therefore increase the odds that the message is seen by the intended recipients, you should implement SPF and/or DKIM for your SMTP domain.
Back in 2015, these protocols were somewhat optional. More recently we have observed that Office 365 treats nearly every email without either SPF or DKIM authentication as SPAM.
SPF and DKIM are not specific to sfPMS and not covered under support. Contact your implementer for a Work Authorization if you would like additional assistance.
Neither SPF nor DKIM are a panacea. Both tend to reduce a given email’s evaluated SPAM risk score, whereas attachments, links, and sfPMS tracking keys tend to increase the evaluated SPAM risk score.
KBA-01604; Last updated: June 6, 2019 at 15:23 pm;
Keywords: SPAM filter, SPAM detection, sender authentication