Skip to main content

Mail Redirection (Custom Senders)

Overview​

To strengthen brand recognition and improve email deliverability, GoWit allows partners to send platform-generated emails—such as weekly reports or password resets—from their own verified domains. This replaces the default GoWit sender (postmaster@mail.gowit.com) with a custom address like ads@subdomain.marketplace.com.

How It Works​

  1. Mailgun as the delivery provider

    • GoWit uses Mailgun for outbound mail delivery.
    • Each partner domain is added to Mailgun so it can send with a custom “From” address.

  2. Domain verification & DNS configuration

    • The partner (or their DNS admin) adds TXT and CNAME records provided by Mailgun.
    • These records validate SPF, DKIM, and tracking, ensuring high deliverability and preventing spoofing.

  3. Template approval

    • All automated email templates (e.g., welcome emails, weekly reports) must be approved.
    • Templates can be localized; each language variant is reviewed before activation.

Requirements​

  • A domain or subdomain dedicated to email (e.g., subdomain.marketplace.com).
  • DNS access to add SPF, DKIM, and tracking records.
  • Approved templates (including any localized versions).

Setup Steps​

  1. Request or create the sending domain

    • Decide on the subdomain (e.g., ads.subdomain.marketplace.com).
    • Ensure it will be used solely for email.

  2. Obtain Mailgun records from GoWit

    • GoWit provides TXT and CNAME entries for SPF, DKIM, and tracking.
    • Example records:
      • TXT @ v=spf1 include:mailgun.org ~all
      • CNAME mailgun._domainkey -> mailgun.org
      • CNAME email -> mailgun.org

  3. Add DNS records

    • Use your DNS provider’s interface to add the provided TXT and CNAME records.
    • Note: DNS propagation may take up to 48 hours.

  4. Verify the domain in Mailgun

    • Once DNS updates propagate, GoWit (or the partner’s Mailgun account) confirms domain ownership.
    • After verification, the domain is ready for sending.

  5. Configure custom “From” address

    • Choose the sender address (e.g., ads@subdomain.marketplace.com).
    • Update application configuration or environment variables so all automated emails use this address.

  6. Template approval process

    • Submit email templates for approval; provide localized versions if needed.
    • After approval, templates are enabled for production use.

  7. Testing

    • Send a test email to confirm the “From” address, template rendering, and tracking.
    • Check spam/junk folders to ensure deliverability.

Fallback Behavior​

  • If no custom domain is configured, emails default to postmaster@mail.gowit.com.
  • This may lead to lower deliverability and weaker brand trust, so configuring a custom sender is strongly recommended.

Troubleshooting​

  • Unverified domain: Double-check DNS records and allow time for propagation.
  • SPF/DKIM failures: Ensure records match exactly; typos cause validation errors.
  • Template rejection: Address feedback (e.g., content, branding) and resubmit.