We're Locking Down Our Email to Fight Phishing

As part of our ongoing commitment to security, we're announcing a significant upgrade to our email defenses.

On November 17th, we will be moving our DMARC policy to p=reject.

In simple terms, what does this mean?

This change makes it much, much harder for spammers and scammers to impersonate our email address (@scrive.com).

DMARC is an email security standard. Our new "reject" policy tells receiving email servers (like Gmail, Outlook, etc.) to completely block any email that claims to be from us but fails strict authentication checks.

This means fraudulent messages—like phishing attempts or fake invoices—won't just go to your spam folder; they'll be rejected outright.

What do you need to do?

For the vast majority of you, the answer is: nothing! This is a behind-the-scenes change designed to protect you. We have been monitoring our email traffic for months to ensure all our legitimate messages are properly authenticated, and we don't anticipate any disruption.

However, if you or your teams suddenly have trouble receiving expected emails from us, please reach out to our support team immediately.

A note on automatic email forwarding

This new, stricter policy can sometimes affect automated forwarding rules.

If you have set up a rule to automatically forward emails from @scrive.com to another email address (like a personal Gmail account or a different ticketing system), you may need to check your configuration.
Why? When an email is forwarded, it can sometimes fail the new, stricter security checks, causing the final recipient to reject it.

What to do:

• If you use a major, modern email provider (like Google Workspace or Microsoft 365), this is almost always handled correctly for you.
• If you manage your own email server or use an older forwarding system, please ensure it is configured to handle forwarded mail correctly for DMARC.