Forum Home

Replying to a message from: Synametrics Support

Jim,

DMARC is a combination of DKIM and SPF. The root cause of this failure is SPF.

The SPF record for rts.kijiji.ca returns the following:

v=spf1 mx a a:rtsmail.kijiji.ca a:rtsmailix5.kijiji.ca a:rtsmailesh.kijiji.ca ip4:195.78.85.112/28 ip4:91.195.49.144/28 ip4:195.78.84.62 include:spf.ecgmail.cloud include:mailgun.org ~all

Any IP address not mentioned in the above SPF will be rejected. Now consider the following message flow:

  • You receive a message from someone@rts.kijiji.ca, and you have a rule to forward this message to your.account@gmail.com
  • When the message is forwarded, the sender's address remains someone@rts.kijiji.ca
  • Google's SMTP server sees a message coming in for rts.kijiji.ca but from an IP that is not authorized to send and, therefore, puts it in the junk folder.
  • Forwarding it manually works because the sender is no longer someone@rts.kijiji.ca, but your email.

Using Xeams to solve this problem

  • Xeams has a feature called Distribution List (DL).
  • Although this feature is meant to expand a single email to multiple recipients, you can use it to your advantage using the following steps.
    • Create a new DL with the following values: List Address should be your.email@yourcompany.com, and the Forward To field should have your.account@gmail.com
  • When Xeams forwards the message to Gmail, it will automatically change the MAIL FROM value in SMTP envelope to yourcompany.com
  • Therefore, when Google gets the message it will look at the SPF record for yourcompany.com rather than rts.kijiji.ca, and the message won't be considered spoofed.