Troubleshooting

Go to your email provider's settings and confirm the forwarding rule is active and pointing to the correct MailBridge address (e.g. abc123@in.mailbridge.ai).

Copy the forwarding address directly from Settings → Inbox in your MailBridge dashboard and paste it into your provider — don't type it manually.

Send a fresh email to your support address from a different inbox. Wait 30 seconds and refresh your MailBridge dashboard.

Some providers block forwarding to unknown addresses. Check if your email provider has a 'blocked senders' or 'spam filter' that might be catching outbound forwards.

Go to Settings → Integrations. Confirm your Slack or Discord integration shows as Connected.

Make sure a default channel is selected. If the channel was deleted or the bot was removed from it, messages will fail silently.

Disconnect and reconnect the integration from Settings → Integrations. This refreshes the OAuth token in case it expired.

In Slack, ensure MailBridge has channels:write and chat:write. In Discord, the bot must have Send Messages and Embed Links in the target channel.

Go to Settings → Routing and check whether a rule matches the email category and is pointing to the correct channel.

Rules are evaluated top-to-bottom. A higher rule with the same category may be overriding the one you expect to fire.

Open the request in your dashboard and look at the AI-assigned category. If the category is different from what you expected, the correct rule may not have matched.

Go to Settings → Webhooks and verify the endpoint URL is correct and reachable from the public internet. Localhost URLs will not work.

Your endpoint must return a 2xx HTTP status within 10 seconds. Any other response (redirect, error, timeout) is treated as a failure.

If your server is rejecting requests, confirm you're verifying the X-MailBridge-Signature header correctly. See the Webhooks guide for the exact verification code.

Go to Settings → Webhooks → click your endpoint → Delivery history. Each attempt shows the response code and body returned by your server.

Your API key is missing or invalid. Check that you're including the Authorization: Bearer YOUR_KEY header and that the key hasn't been revoked.

Your API key doesn't have permission for this action. Ensure the key belongs to an Admin-role user if you're performing a write operation.

You've hit the rate limit. Check the X-RateLimit-Reset header to see when the limit resets, and consider reducing request frequency.

If you're seeing server errors, check the MailBridge status page at mailbridge.ai/status. If no incident is posted, contact support with the request ID from the response.