Review internal Exchange communication as its own boundary
Fortra Exchange Gateway is a specific enquiry for policy around supported Exchange environments. Its design question differs from a general external mail gateway because internal correspondence may follow paths that never cross the internet-facing control. Establish which internal messages and information-handling decisions the project must address.
Record the exact Exchange version, deployment arrangement and existing mail-flow rules. Do not infer support solely from a familiar product name; current platform and version compatibility belongs in the technical proposal. Identify shared mailboxes, service-generated messages and delegated administration that could behave differently from ordinary user-to-user mail.
Validate policy without disrupting internal applications
Confirm the current integration method and prerequisites with the manufacturer. Map permissions and the customer teams responsible for Exchange, security policy and server maintenance. Use representative business departments to select approved messages and documents for testing.
Acceptance should show that intended internal flows remain usable and that a supported policy event reaches the right review path. Include changes to permissions, failed integration and the approved recovery process. Handover should contain configuration records, policy exceptions and a procedure for reviewing the effect of Exchange updates. Product licensing, operating-system work and ongoing policy administration may have different commercial boundaries; make those visible before scheduling rollout.
Evidence to request for this scope
- Confirm current support for the exact Exchange version and topology.
- Test representative internal messages, shared mailboxes and application-generated correspondence.
- Document integration access, update responsibilities and recovery from an incorrect policy effect.
