[THIN] Re: OT: Exchange - bringing e-mail in-house
- From: "Evan Mann" <emann@xxxxxxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Wed, 30 Nov 2005 12:16:38 -0500
Mail Security is actually at v4.6 currently, 10.0 is the Corporate
Edition for desktops/servers,
But anyway, Mail Security is the only Symantec product I kept (dropped
desktop/server). I have actually been very pleased with it's
performance. I've been slammed by Sober.X lately, over 50k e-mails in
the past 1 1/2 weeks, and it just chugs along, no issues.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Mark Mucher
Sent: Wednesday, November 30, 2005 12:07 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: OT: Exchange - bringing e-mail in-house
Yes, I have Mail Security - Version 10.0 (tho I normally detest Symantec
products...)
Thanks,
Mark
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Roger Riggins
Sent: Wednesday, November 30, 2005 11:54 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: OT: Exchange - bringing e-mail in-house
If you have Symantec's AV for Exchange, you are already licensed to use
their SAV for SMTP Gateways product. It's pretty basic, but works well.
Roger Riggins
Network Administrator
Lutheran Services in Iowa
w: 319.859.3543
c: 319.290.5687
http://www.lsiowa.org
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Doug Rooney
Sent: Wednesday, November 30, 2005 10:43 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: OT: Exchange - bringing e-mail in-house
I looked at these items and some others, does anyone know where one can
see the prices of them?
Thank You
-Doug Rooney
Sonoma TileMakers
IT Systems Administrator
7750 Bell Rd.
Windsor Ca, 95492
(707) 837-8177 X11
(707) 837-9472 FAX
it@xxxxxxxxxxxxxxxxxxxx
The information contained in this e-mail may be confidential and is
intended solely for the use of the named addressee.
Access, copying or re-use of the e-mail or any information contained
therein by any other person is not authorized.
If you are not the intended recipient please notify us immediately by
returning the e-mail to the originator.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Grant, Lachlan ISMC:EX
Sent: Tuesday, November 29, 2005 12:29 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: OT: Exchange - bringing e-mail in-house
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] On
Behalf Of Philip Walley
Sent: November 29, 2005 12:22 PM
To: 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>> 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>>>
> 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:
//www.freelists.org/list/thin
************************************************
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
************************************************
Other related posts:
