ReadyWorks SaaS Product Offering

  • ReadyWorks SaaS Email Integration: Send Messages From Your Company Domain

    Overview

    This article explains how to configure email settings for your ReadyWorks implementation. ReadyWorks utilizes a built-in mail server for all enterprise implementations, which is our established best practice for our clients..

    Prerequisites

    Before configuring email in ReadyWorks, ensure you have:

    • Administrative access to your domain's DNS settings
    • Ability to create/modify SPF records
    • IP address of your ReadyWorks instance

    Configuration Steps

    1. Understanding ReadyWorks' Email Architecture

    ReadyWorks instances come with a pre-configured internal mail server that handles all outbound email communications. This is the standard configuration used across ourclient base and requires minimal setup.

    2. Creating the Required SPF Record

    To ensure emails sent from ReadyWorks are properly authenticated and not marked as spam:

    1. Access your domain's DNS settings through your domain registrar
    2. Create or modify your existing SPF record to include the ReadyWorks server IP address
    3. The format should be similar to: v=spf1 ip4:X.X.X.X ~all (where X.X.X.X is your ReadyWorks instance IP)
    4. Save your DNS changes (propagation may take up to 48 hours idepending on your network)

    3. Testing the Configuration

    After creating the SPF record:

    1. Log into your ReadyWorks instance
    2. Navigate to the TCOMM Tester page in ReadyWorks
    3. Send a test email to verify proper delivery
    4. Check that the email arrives and is not flagged as spam

    Common Configuration Questions

    Why does ReadyWorks use its built-in mail server?

    ReadyWorks' built-in mail server provides several advantages:

    • Simplified configuration and maintenance
    • Consistent email delivery across all deployments
    • Reduced dependency on external systems
    • Proven reliability in enterprise environments

    Will emails appear to come from our domain?

    Yes. When properly configured with the SPF record, emails will appear to come from your domain and will pass standard authentication checks.

    Is this approach secure?

    Yes. This is our enterprise-standard approach used by all our SaaS clients. The SPF record ensures that only the authorized ReadyWorks server can send email on your behalf.

    Troubleshooting

    If emails are not being delivered properly:

    1. Verify that the SPF record has been created correctly and has fully propagated
    2. Ensure your network firewall isn't blocking outbound SMTP traffic
    3. Check that recipient email systems aren't blocking incoming mail from your domain
    4. Contact ReadyWorks support if issues persist

    Additional Information

    This configuration approach is used by all SaaS ReadyWorks clients including within  industries that hold very strict security requirements. It provides the most reliable and maintainable solution while meeting enterprise security standards.

    See more