[GH-ISSUE #12] Where to install? #8

Closed
opened 2026-02-27 15:44:56 +03:00 by kerem · 2 comments
Owner

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

Hello,

First of all apologies to use the issue tracker for this. However i don't know how to contact otherwise.
We have 4 exchange servers; 2 mailbox servers in DAG and 2 CAS servers. I cannot determine which servers need the transport agent installation and which don't. Could you please update the readme with this info?

Best regards,

Frans

Originally created by @posixx on GitHub (Sep 13, 2015). Original GitHub issue: https://github.com/Pro/exchange-catchall/issues/12 Hello, First of all apologies to use the issue tracker for this. However i don't know how to contact otherwise. We have 4 exchange servers; 2 mailbox servers in DAG and 2 CAS servers. I cannot determine which servers need the transport agent installation and which don't. Could you please update the readme with this info? Best regards, Frans
kerem 2026-02-27 15:44:56 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@Pro commented on GitHub (Sep 14, 2015):

The transport agent has to be installed on the server which handles the SMTP connection and Edge Transport.
In your case I think these are the two CAS servers.
What this agent does is as soon as an email is sent to the server via SMTP, it rewrites the E-Mail header so that Exchange thinks this was sent to the catchall-target address.

Please keep in mind that those catch-all email addresses only work if the email is received from an EXTERNAL server. I have to check if it is somehow possible to circumvent this problem.

<!-- gh-comment-id:139994253 --> @Pro commented on GitHub (Sep 14, 2015): The transport agent has to be installed on the server which handles the SMTP connection and Edge Transport. In your case I think these are the two CAS servers. What this agent does is as soon as an email is sent to the server via SMTP, it rewrites the E-Mail header so that Exchange thinks this was sent to the catchall-target address. Please keep in mind that those catch-all email addresses only work if the email is received from an EXTERNAL server. I have to check if it is somehow possible to circumvent this problem.
Author
Owner

@posixx commented on GitHub (Sep 14, 2015):

Thanks for your response. Yes the CAS servers are responsible for receive and sent to external SMTP servers, so i will deploy on these servers. For us it's not a big deal it only works for external addresses.

Thanks again!

<!-- gh-comment-id:140000767 --> @posixx commented on GitHub (Sep 14, 2015): Thanks for your response. Yes the CAS servers are responsible for receive and sent to external SMTP servers, so i will deploy on these servers. For us it's not a big deal it only works for external addresses. Thanks again!
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#8
No description provided.