Exchange Server Forums

New smtp port for specific ip

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Message Routing >> New smtp port for specific ip

Page: [1]

Message

<< Older Topic Newer Topic >>

New smtp port for specific ip - 14.Jul.2008 5:23:28 AM

Xas

Posts: 4
Joined: 15.May2008
Status: offline

Hello,
Some of my Exchange users are in a different city. They have a busy mail traffic and connect through a DSL provider. Recently that provider blocked the usage of port 25 for them. I want to make another port usable for smtp for their ip, for example 26.

Aside from any firewall etc. settings, what are the proper steps to do it in Exchange 2007? I want to make sure im doing everything properly.

Thanks..

Post #: 1

Featured Links*

RE: New smtp port for specific ip - 14.Jul.2008 3:01:21 PM

Sembee

Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline

Any reason you are using SMTP and I guess POP3 and not Outlook Anywhere? Outlook Anywhere would be the answer to this question as it would allow those remote users to access the full feature set of Exchange. I would actually go as far as to say that POP3 is the last remote access method of choice for Exchange as it basically turns Exchange in to nothing more than a POP3 service that you can get from your ISP for free!

If you want to continue to use SMTP though, why not use SMTP over SSL, which is already setup on Exchange for port 587. You will need to ensure that you have a valid external SSL certificate and that the users are connecting using the correct URL. However it means the usernames and passwords are not going across in the clear and shouldn't be blocked by the ISP.

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://blog.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.sembee.co.uk/
Exchange Resources: http://exbpa.com/

(in reply to Xas)

Post #: 2

RE: New smtp port for specific ip - 15.Jul.2008 2:59:34 AM

Xas

Posts: 4
Joined: 15.May2008
Status: offline

Hello Simon,

Currently the remote users are accessing Exchange through OWA. However, they want to keep on using their Outlook routine and they make it a big problem.

Port 587 can easily be guessed and get blocked by the ISP. Thats why I dont prefer it.

(in reply to Sembee)

Post #: 3

RE: New smtp port for specific ip - 15.Jul.2008 6:28:47 AM

Sembee

Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline

If the ISP is blocking ports then you have to ask why. If you are running a business on a residential connection then you should probably upgrade.
Outlook Anywhere allows the users to use the full Outlook client. It only requires one port to be open - port 443. If you are already using OWA with an SSL certificate then you are most of the way there - you just need to enable Outlook Anywhere and adjust the client.

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://blog.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.sembee.co.uk/
Exchange Resources: http://exbpa.com/

(in reply to Xas)

Post #: 4

RE: New smtp port for specific ip - 15.Jul.2008 7:12:47 AM

Xas

Posts: 4
Joined: 15.May2008
Status: offline

They think that if an ip uses port 25 quite often, then it must be sending spam. Thus the blocking. Legal system and procedures are very ridicilous in my country and its really painful to talk and persuade them to unblock.

Isn't there any way to make another smtp port usable for a specific ip?

(in reply to Sembee)

Post #: 5

RE: New smtp port for specific ip - 15.Jul.2008 8:47:48 AM

Sembee

Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline

I go back to the original question - why don't you want to use Outlook Anywhere? Remote access to the server is what it is designed for. If the users are currently using OWA then a return to POP3/SMTP or IMAP/SMTP will be a significant backwards step.

You can configure Exchange to listen on another port if you wish, it is part of the Receive Connector configuration - but there is no need to as Exchange/Outlook provides an alternative that is far and away better than POP3/IMAP/SMTP. I don't actually enable POP3/IMAP on any deployments I do because it is not necessary.

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://blog.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.sembee.co.uk/
Exchange Resources: http://exbpa.com/

(in reply to Xas)

Post #: 6