[GH-ISSUE #13] Only external emails are cought #10

Open
opened 2026-02-27 15:44:57 +03:00 by kerem · 1 comment
Owner

Originally created by @Pro on GitHub (Sep 14, 2015).
Original GitHub issue: https://github.com/Pro/exchange-catchall/issues/13

Currently, the agent only catches emails which are received from an external mail server.

E.g. suppose the following setup:
Your mail-server handles the domains:

  • example.com
  • anyname.com

You set up catchall for the domain anyname.com to forward all emails to user@example.com

Now if you send a mail from an internal user info@example.com to hello@anyname.com you will get an error that the address doesn't exist because exchange doesn't route internal mails through the agent.

This means that only mails from external providers (like GMail,...) are cought and forwarded correctly.

Originally created by @Pro on GitHub (Sep 14, 2015). Original GitHub issue: https://github.com/Pro/exchange-catchall/issues/13 Currently, the agent only catches emails which are received from an external mail server. E.g. suppose the following setup: Your mail-server handles the domains: - example.com - anyname.com You set up catchall for the domain `anyname.com` to forward all emails to `user@example.com` Now if you send a mail from an internal user `info@example.com` to `hello@anyname.com` you will get an error that the address doesn't exist because exchange doesn't route internal mails through the agent. This means that only mails from external providers (like GMail,...) are cought and forwarded correctly.
Author
Owner

@asadhaider commented on GitHub (Sep 20, 2015):

Just installed the release v1.6.3-new onto a new Exchange 2013 (SP 1 CU4) server and when testing this - both internal and external emails are working fine for me.

I have user1@example.com configured as the catchall address for example.com, and mail from user2@example.com to catchall@example.com is being correctly forwarded to user1 (sent through OWA).

I only have one send connector configured to route mail using the domains MX records for all SMTP mail, not sure if this is what's making it work as it may be doing it with internal domains too?

<!-- gh-comment-id:141742673 --> @asadhaider commented on GitHub (Sep 20, 2015): Just installed the release v1.6.3-new onto a new Exchange 2013 (SP 1 CU4) server and when testing this - both internal and external emails are working fine for me. I have user1@example.com configured as the catchall address for example.com, and mail from user2@example.com to catchall@example.com is being correctly forwarded to user1 (sent through OWA). I only have one send connector configured to route mail using the domains MX records for all SMTP mail, not sure if this is what's making it work as it may be doing it with internal domains too?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/exchange-catchall#10
No description provided.