Fix: "Your Organization Does Not Allow External Forwarding" When Connecting Email to Trello

The error, verbatim

Remote server returned '550 5.7.520 Access denied, Your organization does not allow external forwarding. Please contact your administrator for further assistance. AS(7555)'

You'll see this (or a close cousin) when a rule in your Microsoft 365 / Exchange Online mailbox tries to automatically forward mail to an address outside your company — a Trello board's email-to-board address, a helpdesk power-up's intake address, a personal Gmail, anything external. Trello users hit it constantly when wiring a shared mailbox into a board; there's a representative Atlassian Community thread where the eventual advice was, essentially, "forward each email by hand."

Google Workspace has the same lever: admins can disable automatic forwarding for Gmail, and security-conscious orgs do.

Why your mail server does this (and why it's right)

Automatic external forwarding is one of the classic data-exfiltration channels: compromise one mailbox, add a silent rule, and every future email leaks outward. That's why Microsoft ships modern tenants with external auto-forwarding disabled in the outbound spam policy, and why security baselines tell admins to keep it that way.

This matters for your Trello plans because the policy isn't a bug to work around — it's a control your IT team chose. Any email→Trello setup built on auto-forwarding is, from the mail server's point of view, indistinguishable from the attack it exists to stop.

What this breaks in the Trello ecosystem

• Native email-to-board automation. Manual forwarding still works (a human pressing Forward is not "auto-forwarding"), but rules that relay everything from help@ to the board address bounce. That's the automation path gone — one of the eight structural limits of email-to-board.
• Forwarding-address power-ups. Tools like SendBoard and Hipporello receive your mail on their own intake addresses (yourco.sendboard.com-style). Perfectly good products — but if the mail lives in a corporate mailbox that isn't allowed to auto-forward externally, the pipeline never starts.
• Zapier email triggers via forwarding. Same relay, same bounce.

The workarounds, ranked by realism

1. Ask IT for a scoped exception. Exchange admins can permit auto-forwarding for a specific mailbox or to a specific destination. It's the "proper" fix — and it's frequently declined, because the exception recreates the exact channel the policy closes. Worth one polite ask; don't build your workflow on hope.
2. Move the intake address outside the corporate tenant. Publish a non-corporate address for the workflow (e.g. a dedicated Gmail) and let people email it directly. Works, but now your business mail lives outside the org's mail governance — many companies dislike that even more than forwarding.
3. Forward manually. Compliant, reliable, and exactly the copy-paste treadmill you were automating away.
4. Stop forwarding altogether — read the mailbox in place. This is the structural fix: an integration that signs into the mailbox through the provider's official OAuth flow and works with mail where it already is. Nothing is relayed to an external address, so there's nothing for the forwarding policy to block.

Why OAuth access doesn't trip the policy

The forwarding block stops mail leaving the organization automatically. An OAuth integration like Email Inbox for Trello never sends your mail anywhere: it connects to your Gmail or Google Workspace account through Google's consent screen and reads, replies, and files messages inside the mailbox itself, displaying them within Trello. From the mail system's perspective:

• No relay, no rule, no bounce — there is simply no forwarding step to deny.
• Access is visible and revocable — it appears in the Google account's security page (and in the Workspace admin console), scoped to what the app actually does, and can be cut off in one click.
• Replies come from your real address — sent by Gmail itself with proper threading, not by a third-party relay pretending to be you.

One honest caveat: Workspace admins can restrict which third-party OAuth apps users may connect. If your org locks that down too, no integration of any kind will fly without an admin conversation — but you'll be asking for a reviewable, revocable, read-in-place grant instead of an open relay, which is a much easier "yes."

Setting up the no-forwarding pipeline

1. Add Email Inbox to your Trello board and connect the Gmail or Google Workspace account that receives the mail.
2. Create an automation from any Gmail search — to:help@yourco.com is:unread, label:tickets, from:invoices@ has:attachment — and pick the destination list.
3. New matching mail becomes cards automatically, with sender and attachments intact; replies land on the card, and you answer from Trello.

If your team is on Outlook/Microsoft 365 for the mailbox itself, an OAuth Gmail tool won't help — your realistic options are a scoped IT exception or a provider-agnostic forwarding tool, compared honestly in our email power-up roundup.

Frequently asked questions