Re: Blocking Port 25
- From: Jeff Grossman <jeff.nospam@xxxxxxxxxxx>
- Date: Mon, 03 Apr 2006 06:21:26 -0700
Thanks for the information. I will give it a try later today.
Jeff
"Lasse Pettersson [Exchange MVP]" <lasse@xxxxxxxxxxxx> wrote:
Use IP restrictions on default Virtual SMTP Server to allow certain IP's.
only could do the trick. Its done under the Connection Control on the
virtual SMTP server
then create another virtual smtp server that you bind to port 587, you could
use IP restrictions on this virtual SMTP server if you want aswell
/Lasse
"Jeff Grossman" <jeff.nospam@xxxxxxxxxxx> wrote in message
news:sj5132tir5u9dglucoakpirp4ej1np4mrd@xxxxxxxxxx
I am almost ready to put my Exchange server into production.
Currently, I have a front gateway machine that receives all e-mail via
port 25, does some spam and virus checking, and then forwards to the
mail to my final e-mail server. I am going to keep the front gateway
machine going, but switch out the backend e-mail server. I do not
allow any port 25 traffic to the backend machine, except for local
internal traffic. If any remote users want to send mail through our
server, they connect to backend email server via port 587 and
authenticate themselves.
How can I do the same setup with Exchange? I do not want to allow
outside traffic to port 25, only port 587 (I will still allow IMAP
connections from outside).
Thanks for any help you can offer me.
Jeff
- References:
- Blocking Port 25
- From: Jeff Grossman
- Re: Blocking Port 25
- From: Lasse Pettersson [Exchange MVP]
- Blocking Port 25
- Prev by Date: Re: How to remove Outlook server-side rules from Exchange server
- Next by Date: Re: Public Store Defrag
- Previous by thread: Re: Blocking Port 25
- Next by thread: databse corrupt
- Index(es):
Relevant Pages
|
