Skip to main content

Featured Post

Exchange Admin Center language

Depending on your computer language settings, Exchange Admin Center can take those and open in a language you actually don't want to use.
You'll Google that this can be changed if administrator/ admin user has mailbox by openening OWA settings and changing Regional parameters.

But usually Admin user does not have mailbox or you don't want her/him to have it. You will search again and find that you can add mkt=en-US (as an example) to the URL of the Exchange Admin Center (https://yourexchangehostname/ecp?ExchClientVer=15&mkt=en-US)

Third option you have is opening Internet Explorer settings (I am using Windows 2016)


Click languagesClick Set Language Preferences

Add language you want to use by clicking Add language
Use Move up or Move Down options to put desired language on topClose Internet ExplorerOpen it again and login again to Exchange Admin Center

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing:
Use these local IP Addresses to receive mail
Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail.
Receive mail from remote servers which have these IP addresses
Use this list to specify the remote IP address range from which this Receive connector accepts connections.

You change Send Connector port by using PowerShell. Open Exchange Management Shell and type:

Get-SendConnector -Identity "SENDCONNECTORNAME" | fl
Check the port number then type:
Set-SendConnector -Identity "SENDCONNECTORNAME" -port 26
In this example I set port 26 as SMTP port for sending messages. Check the change by typing

Get-SendConnector -Identity "SENDCONNECTORNAME" | fl
HUB and EDGE servers are responsible for mail transport, so include all the servers you need in your requirement.

Comments

  1. Great!!!!!!!!! Thank you. I was pulling my hair out trying to locate where to chnage the outbound port. AT&T blocks outbound 25.

    ReplyDelete
  2. This fixed my SBS 2008 server after my ISP started blocking port's 25. I used port forwarding on the router for the inbound.
    Thank you

    ReplyDelete
  3. thanks a bunch... the commandlet made my evening. A beer in your name

    ReplyDelete
  4. Great job.
    Just changing from 2003 Exchange to 2007 and I really got stucked with this new type of topology.

    ReplyDelete
  5. Hi, thanks for the tips. I need some help on configuring ASSP and Exchange 2007.

    I have a SBS2008 with Exchange on the same server. I have setup my ASSP incoming port to 25, and the send to exchhange port 125. Then exchange reply from port 225 to ASSP receiving port 225 and then send to internet by port 25.

    I'M I ok ??
    what connector do i need in total for outgoing and incoming.

    Thanks in advance

    ReplyDelete
  6. Yes, This is awesome! You saved my A**! Thanks man!

    ReplyDelete
  7. Hi!
    I have sbs 2008.
    And i have problem with smtp port!
    My smtp port is 25 and i will change on 587. Whan i change on 587 i send mail no problem but i can't receive nobody mail. Why?

    ReplyDelete
  8. Hi thanks for your post.
    So far, it looks to be the most promising.
    We are supposed to change our outgoing SMTP port and it is like studying Greek to me.
    Get-SendConnector -Identity "SENDCONNECTORNAME" | fl

    Am I supposed to substitute something for the word SENDCONNECTORNAME? It says it can't find it. I substituteds the server name etc. but it seems to want something else. Any help would be appreciated.

    Thanks again and thanks in advance.
    B.

    ReplyDelete
  9. Okay, I figured it out. I had to use the whole long name that was listed in the "Send Connectors" Tab of the Hub Transport under Organizational Configuration in the Exchange Managementn Console. In my case the name was "Windows SBS Internet Send XXSERVER" Once I substituted that, it was all good. Thanks again for your very useful help.

    ReplyDelete
  10. Hi can Anybody help me with how to turn on SSL on in exchange 2007

    ReplyDelete
    Replies
    1. If by "turn on SSL on in exchange 2007" you mean enable SSL in OWA then check this page https://technet.microsoft.com/en-us/library/bb123583(v=exchg.141).aspx or look for similar articles.

      Delete
  11. This comment has been removed by a blog administrator.

    ReplyDelete

Post a Comment

Popular posts from this blog

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

Move-ActiveMailboxDatabase - Failed

If by any chance you see the error below after updating the server which is part of DAG, just suspend and then activate the database copy. Exchange will resynchronize the copies and you’ll be able to move the database. You do that by clicking on the database under Database Management, then select non active copy in the Database Copies window, right click on it and select Suspend Database Copy. Repeat the step and select Resume Database Copy.
Move-ActiveMailboxDatabase
Failed
Error:
An Active Manager operation failed. Error The database action failed. Error: An error occurred while trying to validate the specified database copy for possible activation. Error: Database copy 'DBx' has been blocked from activation on server 'x.domain.com' by an administrative action. Reason: None specified.. [Database: DBx, Server: x.domain.com]
An Active Manager operation failed. Error An error occurred while trying to validate the specified database copy for possible activation. Error: Datab…