[THIN] Re: OT: Exchange - bringing e-mail in-house
- From: Philip Walley <mythinlist@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Tue, 29 Nov 2005 15:25:29 -0600
now jeff, where is your sense of adventure?
Jeff Pitsch wrote:
My entire point of that post though was to eliminate your exchange box
being directly exposed to the internet. Not something you typically
want to do.
Jeff
On 11/29/05, *Philip Walley* <mythinlist@xxxxxxxxx
<mailto:mythinlist@xxxxxxxxx>> wrote:
2003s built in spam filter seems to be a pretty good product.
Grant, Lachlan ISMC:EX wrote:
>I've used both NetIQ's MailMarshall and ClearSwift's MIMEsweeper
in a DMZ to
>handle both incoming and outgoing mail which will also stop you
from putting
>your exchange server up for grabs. They both do pretty well if
you've got
>the hardware for them. I prefered MailMarshall, it seemed to be
more stable
>than MIMESweeper.
>
>You can do some really neat content filtering stuff with these
products,
>especially if you've got a user base who likes to push the
rules.... And
>also makes some pretty reports to justify more spending or
anything else
>you'd like to prove.
>
>Lachlan.
>
>-----Original Message-----
>From: thin-bounce@xxxxxxxxxxxxx
<mailto:thin-bounce@xxxxxxxxxxxxx>
[mailto:thin-bounce@xxxxxxxxxxxxx
<mailto:thin-bounce@xxxxxxxxxxxxx>] On Behalf
>Of Philip Walley
>Sent: November 29, 2005 12:22 PM
>To: thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx>
>Subject: [THIN] Re: OT: Exchange - bringing e-mail in-house
>
>
>trend scanmail, runs on the server and works like a champ
>
>Jeff Pitsch wrote:
>
>
>
>>On those thoughts, you may want to make another box in the DMZ the
>>receipient of the mail, scan it, do whatever with it, then
forward it
>>on to the exchange box. that way you protect yourself.
>>
>>Jeff Pitsch
>>
>>
>>On 11/29/05, *Philip Walley* <mythinlist@xxxxxxxxx
<mailto:mythinlist@xxxxxxxxx>
>><mailto: mythinlist@xxxxxxxxx <mailto:mythinlist@xxxxxxxxx>>> wrote:
>>
>> You'd want to change the MX and the A records I believe, but
yeah,
>> that
>> and making sure that you have a public IP on your outside
nat'd to
>> the
>> correct internal with port 25 open. Bingo! it works. You do need
>> to make
>> sure that the recipient policy is setup for your external email
>> address.
>> Exchange 2003 needs that to ensure that it will route it
>>correctly.
>>
>> Jeff Pitsch wrote:
>>
>> > Maybe this is my ignorance but isn't it a simple change of
the MX
>> > record and making sure the proper port and IP is NAT'd
through the
>> > firewall to the server.
>> >
>> > Jeff Pitsch
>> >
>> >
>> > On 11/29/05, *Mark Mucher* <mmucher@xxxxxxxxxxxxx
<mailto:mmucher@xxxxxxxxxxxxx>
>> <mailto:mmucher@xxxxxxxxxxxxx <mailto:mmucher@xxxxxxxxxxxxx>>
>> > <mailto: mmucher@xxxxxxxxxxxxx
<mailto:mmucher@xxxxxxxxxxxxx> <mailto:mmucher@xxxxxxxxxxxxx
<mailto:mmucher@xxxxxxxxxxxxx>>>>
>> wrote:
>> >
>> > Sorry for the OT, but I couldn't think of a better
group to
>> steer
>> > me in the right direction.
>> >
>> > We have Exchange 2003 on Server 2003 with internal
e-mail and
>> > calendaring, etc. enabled.
>> >
>> > The task now is to bring the external e-mail (now
hosted by and
>> > ISP with our domain name) in-house.
>> >
>> > I'm looking for a white paper, tutorial, etc. that will
>> cover all
>> > the steps including routing the public IP to the Exchange
>> server.
>> >
>> > Thanks in advance for any and all suggestions.
>> >
>> > Mark
>> >
>> >
>> ************************************************
>> For Archives, RSS, to Unsubscribe, Subscribe or
>> set Digest or Vacation mode use the below link:
>> http://www.freelists.org/list/thin
>> ************************************************
>>
>>
>>
>>
>************************************************
>For Archives, RSS, to Unsubscribe, Subscribe or
>set Digest or Vacation mode use the below link:
>http://www.freelists.org/list/thin
>************************************************
>************************************************
>For Archives, RSS, to Unsubscribe, Subscribe or
>set Digest or Vacation mode use the below link:
>http://www.freelists.org/list/thin
<http://www.freelists.org/list/thin>
>************************************************
>
>
>
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://www.freelists.org/list/thin
************************************************
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://www.freelists.org/list/thin
************************************************
- References:
- [THIN] Re: OT: Exchange - bringing e-mail in-house
- From: Grant, Lachlan ISMC:EX
- [THIN] Re: OT: Exchange - bringing e-mail in-house
- From: Philip Walley
- [THIN] Re: OT: Exchange - bringing e-mail in-house
- From: Jeff Pitsch
Other related posts:
- » [THIN] OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
- » [THIN] Re: OT: Exchange - bringing e-mail in-house
Jeff
On 11/29/05, *Philip Walley* <mythinlist@xxxxxxxxx <mailto:mythinlist@xxxxxxxxx>> wrote:
2003s built in spam filter seems to be a pretty good product.
Grant, Lachlan ISMC:EX wrote:
>I've used both NetIQ's MailMarshall and ClearSwift's MIMEsweeper
in a DMZ to
>handle both incoming and outgoing mail which will also stop you
from putting
>your exchange server up for grabs. They both do pretty well if
you've got
>the hardware for them. I prefered MailMarshall, it seemed to be
more stable
>than MIMESweeper.
>
>You can do some really neat content filtering stuff with these
products,
>especially if you've got a user base who likes to push the
rules.... And
>also makes some pretty reports to justify more spending or
anything else
>you'd like to prove.
>
>Lachlan.
>
>-----Original Message-----
>From: thin-bounce@xxxxxxxxxxxxx
<mailto:thin-bounce@xxxxxxxxxxxxx>
[mailto:thin-bounce@xxxxxxxxxxxxx
<mailto:thin-bounce@xxxxxxxxxxxxx>] On Behalf
>Of Philip Walley
>Sent: November 29, 2005 12:22 PM
>To: thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx>
>Subject: [THIN] Re: OT: Exchange - bringing e-mail in-house
>
>
>trend scanmail, runs on the server and works like a champ
>
>Jeff Pitsch wrote:
>
>
>
>>On those thoughts, you may want to make another box in the DMZ the
>>receipient of the mail, scan it, do whatever with it, then
forward it
>>on to the exchange box. that way you protect yourself.
>>
>>Jeff Pitsch
>>
>>
>>On 11/29/05, *Philip Walley* <mythinlist@xxxxxxxxx
<mailto:mythinlist@xxxxxxxxx>
>><mailto: mythinlist@xxxxxxxxx <mailto:mythinlist@xxxxxxxxx>>> wrote:
>>
>> You'd want to change the MX and the A records I believe, but
yeah,
>> that
>> and making sure that you have a public IP on your outside
nat'd to
>> the
>> correct internal with port 25 open. Bingo! it works. You do need
>> to make
>> sure that the recipient policy is setup for your external email
>> address.
>> Exchange 2003 needs that to ensure that it will route it
>>correctly.
>>
>> Jeff Pitsch wrote:
>>
>> > Maybe this is my ignorance but isn't it a simple change of
the MX
>> > record and making sure the proper port and IP is NAT'd
through the
>> > firewall to the server.
>> >
>> > Jeff Pitsch
>> >
>> >
>> > On 11/29/05, *Mark Mucher* <mmucher@xxxxxxxxxxxxx
<mailto:mmucher@xxxxxxxxxxxxx>
>> <mailto:mmucher@xxxxxxxxxxxxx <mailto:mmucher@xxxxxxxxxxxxx>>
>> > <mailto: mmucher@xxxxxxxxxxxxx
<mailto:mmucher@xxxxxxxxxxxxx> <mailto:mmucher@xxxxxxxxxxxxx
<mailto:mmucher@xxxxxxxxxxxxx>>>>
>> wrote:
>> >
>> > Sorry for the OT, but I couldn't think of a better
group to
>> steer
>> > me in the right direction.
>> >
>> > We have Exchange 2003 on Server 2003 with internal
e-mail and
>> > calendaring, etc. enabled.
>> >
>> > The task now is to bring the external e-mail (now
hosted by and
>> > ISP with our domain name) in-house.
>> >
>> > I'm looking for a white paper, tutorial, etc. that will
>> cover all
>> > the steps including routing the public IP to the Exchange
>> server.
>> >
>> > Thanks in advance for any and all suggestions.
>> >
>> > Mark
>> >
>> >
>> ************************************************
>> For Archives, RSS, to Unsubscribe, Subscribe or
>> set Digest or Vacation mode use the below link:
>> http://www.freelists.org/list/thin
>> ************************************************
>>
>>
>>
>>
>************************************************
>For Archives, RSS, to Unsubscribe, Subscribe or
>set Digest or Vacation mode use the below link:
>http://www.freelists.org/list/thin
>************************************************
>************************************************
>For Archives, RSS, to Unsubscribe, Subscribe or
>set Digest or Vacation mode use the below link:
>http://www.freelists.org/list/thin
<http://www.freelists.org/list/thin>
>************************************************
>
>
>
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://www.freelists.org/list/thin
************************************************- [THIN] Re: OT: Exchange - bringing e-mail in-house
- From: Grant, Lachlan ISMC:EX
- [THIN] Re: OT: Exchange - bringing e-mail in-house
- From: Philip Walley
- [THIN] Re: OT: Exchange - bringing e-mail in-house
- From: Jeff Pitsch