Wednesday, November 29, 2023

Change Port Number for a Send Connector

Depending on your Exchange environment it may be necessary to change the port number that your Send Connector communicates on. Generally it is left to port 25 but some applications may require a different configuration. An example of this may be.

  • Connection to an external/internal smarthost on a different port
  • Connection to a secure gateway for a particular domain in a scoped connector
  • Connection of a test server on a residential internet that blocks port 25

Whilst this option is clearly visible in a receive connector, it is not able to be changed in the EAC for a Send Connector. Luckily there is an easy powershell command to achieve this. From the Exchange Shell use this

set-sendconnector -identity ‘Outbound Email’ -port 2500

Simple as that, although you will need to stop and start your Transport Service to enact the change.


net stop MSExchangeTransport net start MSExchangeTransport

Don’t forget that you will need to open the port on the Windows Firewall manually too. Also any external firewalls will need a rule placed there too. Other than that, you are good to go.

Mark Rochester
Mark Rochesterhttps://thecloudgeezer.com
Mark currently works in the cloud space assisting large companies to migrate from either on premises to the cloud, or cloud to cloud. His experience with Enterprise migrations spans more than 25 years which basically makes him old. However, with all the oldness creeping up he still finds technology massively exciting. Please reach out for a chat anytime you would like. :-)

Related Articles

CloudOCM Video Training

Yes, migrations are often complex and difficult. One of the hardest things is to get your userbase educated in all of the new systems...

Introducing CloudOCM

The most common questions in migrations with Microsoft 365 is always this..... "Do you have any email templates for the communications?" "What can we use to...

Stop Microsoft Teams Sprawl

Anybody that has come into an organization and looked at the Teams Admin Center, had a heart attack because there are so many Teams...

Stay Connected

85FansLike
35,855FollowersFollow
32,381SubscribersSubscribe
- Advertisement -

Latest Articles