Preventing email notifications from being blocked
Email notifications from Nutrient Workflow Automation Platform can sometimes be blocked, dropped, or marked as spam by email servers. This guide helps admins troubleshoot and prevent these delivery issues to ensure reliable communication.
Server information
For Nutrient Workflow Automation Platform Trials, Shared Cloud, and Private Cloud accounts:
Fully qualified domain name: cloudmail.integrify.com
IP Address: 52.44.253.12
Common solutions
Below are common methods to prevent email notifications from being blocked or marked as spam.
Enable Nutrient’s cloud email server
Configure your email server to enable communications from our server to bypass spam and virus filtering algorithms. If your organization receives many notifications from Nutrient Workflow Automation Platform, this approach also reduces CPU usage on your mail server.
Allowlist your system email address
If you can’t configure server-wide email enabling, add the specific email address used for sending notifications in Nutrient Workflow Automation Platform to your server’s global allowlist.
Configure SPF records
Nutrient Workflow Automation Platform already has valid SPF and PTR records for our cloud server. You only need to modify your DNS SPF record if you’re using a system email address from a domain other than integrify.com
.
When SPF configuration is needed:
- Your Nutrient Workflow Automation Platform instance uses a system email address like
notification@mydomain.com
- Your personal email is
me@mydomain.com
- Your email server performs reverse DNS and SPF record validation
Without proper SPF records containing either ip4:52.44.253.12
or include:integrify.com
, email delivery may fail.
Adding our server to your SPF record
- Access your DNS management console
- Locate your domain’s SPF record (a TXT record starting with
v=spf1
) - Add either
ip4:52.44.253.12
orinclude:integrify.com
to your existing SPF record - Save changes and allow time for DNS propagation
Example SPF record:
v=spf1 include:integrify.com ~all
Additional resources
For detailed SPF record syntax information, refer to the SPF Record Syntax documentation(opens in a new tab).
Next steps
After implementing these changes:
- Test email delivery by triggering a notification from your Nutrient Workflow Automation Platform instance
- Monitor your email server logs for any remaining delivery issues
- Contact Nutrient support if problems persist after implementing these solutions