Re: Configuring Exchange 2003 with Symantec Anti-Virus

From: PES (NO*SPAMpestewartREMOVE*THIS_at_adelphia.netSPAM*SUCKS)
Date: 10/06/04 

Date: Wed, 6 Oct 2004 19:35:52 -0400

You're looking at the wrong product. Symantec has a product that can front
end any mail server. It is basically a mail relay. It can be installed on
Exchange and is probably actually a tad bit better for scanning incoming
mail for Virii. However the most integrated solution is called something
like savmse. It installs using the avapi and is very nice. It also gives
you the ability to scan mail boxes and mailbox to mailbox traffic where the
solution you mentioned does not. Both products are included with Symantec
Enterprise edition.

"kmcnet" <kmcnet@discussions.microsoft.com> wrote in message
news:FF9AF7F4-EADE-41C5-8B52-DA724EF834E7@microsoft.com...
> Hello Everyone and thanks foryour help in advance. I am new to Exchange
> 2003
> and have set up a new Exchange 2003 server. I want to install Symantec
> Anti-Virus for SMTP Servers to screen incoming messages for virues.
> Apparently, this software listens on port 25 and catches all incoming
> messages, screens them, and routes them to Exchange. However, if this is
> installed on the same machine, the documentation says it will conflict
> with
> Exchange. Since I am not entirely sure how things work, I want to know if
> I
> can reconfigure Exchange to receive on antoher port (is changing the the
> default SMTP Server port enough?) or, I if change the external port on my
> firewall to something other than 25, will I have routing problems? (the
> anti-virus software can redirect internally to any port inclduing 25). I
> guess my question is, if I change the firewall port to something other
> than
> port 25, will I need to make DNS changes or some other change to receive
> internet mail? Obviously, I am pretty confused on these topics. Any help
> would be greatly appreciated. Thanks.

Relevant Pages

  • RE: DNS and Exchange issues
    ... with the Exchange Server after you have installed the patch 888619. ... XFOR: Telnet to Port 25 of IMC to Test IMC Communication: ... Start Exchange System Manager. ... Port 21 enables external and internal file transfer ...
    (microsoft.public.windows.server.sbs)
  • Re: MSADC 8355 LDAP Result failed
    ... I receive 2 when the server restarts. ... Event Category: LDAP Operations ... Opening LDAP session to directory xxx on port 389. ... If you put Exchange on one, ...
    (microsoft.public.exchange.setup)
  • Re: ConfigDSInteg error
    ... Agreement to point to the new Exchange 2003 server is so that it will have ... You would also change the port ... Any ADC connection agreements configured to point to the SRS would need to ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2003 - POP3 only delivers email to Administrator
    ... Server to allow internet users access Exchange through POP3 services, ... Port 21 enables external and internal file transfer ...
    (microsoft.public.windows.server.sbs)
  • Re: ConfigDSInteg error
    ... Agreement to point to the new Exchange 2003 server is so that it will have ... You would also change the port ... Any ADC connection agreements configured to point to the SRS would need to ...
    (microsoft.public.exchange.setup)
Loading