This guide explains how to set up email forwarding to Autorply when you prefer not to configure IMAP. Forwarding allows your email provider to push inbound messages directly to Autorply, which then processes them as incoming conversations in your inbox.
Forwarding emails to Autorply requires a cloud storage configured

​
When to Use Forwarding

Forwarding is a good option if:
  • You don’t want to use IMAP or your provider does not allow IMAP access.
  • You want a simple, push‑based way to deliver inbound emails to Autorply.
  • Your provider supports routing or forwarding rules (Gmail, Google Workspace, Outlook, Fastmail, Zoho, custom servers, etc.).
  • You already use SMTP for outbound mail and just need a lightweight inbound setup.

​
How Forwarding Works in Autorply

Each email inbox in Autorply is assigned an ingress address—a unique, system‑generated email address. When your provider forwards an email to that address, Autorply. Note: For installations using an ingress provider (SES, SendGrid, Mailgun, etc.), you must configure an MX record pointing to the ingress provider so that inbound email is accepted and routed correctly.
  1. Ingress provider receives the email and forwards it to the configured Autorply URL.
  2. Autorply parses the content, attachments, headers, and thread references.
  3. Creates or updates the conversation in the appropriate inbox.
  4. Handles message threading properly via Message-ID, References, and In-Reply-To.
Outbound email continues to use your configured SMTP provider.

​
Requirements

To use forwarding successfully, ensure:
  • Email ingress is enabled on your Autorply installation. Some self-hosted setups disable ingress by default for security.
  • Your installation supports inbound processing via the configured mailer/ingress pipeline.
  • The forwarding rule is set to forward all relevant mail, including replies.
  • SPF, DKIM, and DMARC are correctly configured on your domain for good deliverability.
If ingress is disabled, Autorply will show a warning in the UI. Your administrator must enable it before forwarding works. The receiving domain should be configured in the environment variable MAILER_INBOUND_EMAIL_DOMAIN. 
MAILER_INBOUND_EMAIL_DOMAIN=

​
Finding the Forwarding Address

In Autorply:
  1. Go to your inbox settings.
  2. Select your email channel settings -> Configuration
  3. Copy the provided Autorply ingress email address.
This address is unique per inbox.

​
Configuring Forwarding on Your Email Provider

The setup varies slightly across providers, but the steps are generally:
  1. Open your email provider’s forwarding or routing settings.
  2. Add the Autorply ingress email as a forwarding destination.
  3. Verify the address if the provider requires confirmation.
  4. Set a rule to forward all incoming email (or only relevant messages) to the ingress address.
  5. Save the configuration.

​
Configuring Ingress Provider

For Autorply installations, a dedicated ingress provider (Amazon SES, SendGrid, Mailgun, etc.) is required. The provider acts as the first receiver of your domain’s email and then forwards it to the Autorply ingress URL. See more details here.

​
Outbound Email Behavior

Forwarding affects only inbound messages. Outbound messages will still be sent using:
  • The SMTP provider you configured for the inbox (recommended), or
  • The default SMTP provider configured in the Autorply installation.

​
Troubleshooting

Common issues:

​
1. Forwarding Not Enabled in Autorply

If you see: “Support for forwarding emails is not configured. Contact your administrator.” Your Autorply installation must enable email ingress. MAILER_INBOUND_EMAIL_DOMAIN configuration is missing.

​
2. Emails Not Appearing in the Inbox

Check:
  • Forwarding rule is enabled and active.
  • Provider is not suppressing or classifying forwarded mail.
  • No DMARC quarantine/reject issues.
  • The ingress address is correct.

​
3. Threading Issues

Autorply relies on message headers for threading. Ensure your provider forwards headers intact.