RE: RPCPING Utility and Exception 1722
- From: Sarbjit Singh Gill <ssgill@xxxxxxxxxxxxxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Wed, 29 Sep 2004 15:22:17 +0800
Since we are on this topic, can i use my ISA2004 as a SMTP
gateway? I have already got the ISA 2004 to generate OWA
forms so that unathenticated traffic does not reach my OWA
server.
My client does not have any additional boxes for SMTP
gateway, so i thought of using the ISA 2004 for SMTP gateway-
ing
Cheers
Gill
---- Original message ----
>Date: Tue, 28 Sep 2004 15:11:45 -0400
>From: "Lara, Greg" <GLara@xxxxxxx>
>Subject: [exchangelist] RE: RPCPING Utility and Exception
1722
>To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
>
>http://www.MSExchange.org/
>
>Client systems don't use MX records, but external servers
do. You need them
>in your external DNS so that when someone sends a message
to your domain,
>their server can query the MX record for your domain and
thus know where to
>deliver the message.
>
>How do you handle incoming mail now? You have a number of
options getting
>Internet mail into your system.
>
>You could use your ISP to receive all your incoming mail on
their SMTP
>servers, and have them forward it to your Exchange server
(using port
>address translation on your firewall, allowing only SMTP
from that one
>system). The advantage here is if your network is down,
your incoming mail
>will continue to queue. In this case, you'd have your ISP
configure an MX
>record that would point to their SMTP server.
>
>Another common scenario is to set up an SMTP relay in a DMZ
(preferable),
>give it a public IP address, and have it forward mail to
your Exchange
>server. Many people do this with a Linux or FreeBSD box,
and run sendmail or
>postfix as the relay software (postfix is easier to
manage). It could be
>done with a Windows box running the IIS SMTP service, but
be sure to lock
>the box down tight. Whatever the server you use, you'd give
it an externally
>accessible IP address, and configure a rule in your
firewall to forward SMTP
>traffic (TCP/IP port 25) to that server. The MX record in
your external DNS
>would then point to that server.
>
>If you want your mail users to access their mailboxes
externally, I suggest
>using Microsoft's suggestions for configuring OWA, or go to
MSExchange.org
>for configuration examples.
>
>Greg Lara
>
>------------------------------------------------------------
----------------
>---------------------------
>This e-mail message may contain privileged, confidential
and/or proprietary
>information intended only for the person(s) named. If you
are not the
>intended recipient, please destroy this message, and any
attachments, and
>notify the sender by return e-mail. If you are not the
intended
>recipient(s), or the employee or agent responsible for
delivering the
>message to the intended recipient(s), you are hereby
notified that any
>dissemination, disclosure or copying of this communication
is strictly
>prohibited.
>------------------------------------------------------------
----------------
>---------------------------
>
>
>-----Original Message-----
>From: Mustafa Cicek [mailto:mbcicek@xxxxxxxxx]
>Sent: Tuesday, September 28, 2004 12:57 PM
>To: [ExchangeList]
>Subject: [exchangelist] RE: RPCPING Utility and Exception
1722
>
>http://www.MSExchange.org/
>
>Hi Greg!
>
>Thanks for respond.
>First:
>That is my type error in this message board that I listed
twice exchfe in
>my internal DNS list. That ist not true for my internal
NDS. I have A
>records for EXCHEFE and EXCHBE.
>
>Second:
>I want that the internal and external users can access
Exchange internally
>or externally. In Addition I wil deploy multiple mail
domains that the
>other maild domein users access my Exchange environment.
>
>I don't understand why I should not my MX records in
internal DNS? How can
>internal user access Exchange if they have no MX record in
internal DNS?
>Can you list me your correction for my external and
internal DNS entries?
>
>Thanks.
>
>MustafA
>
>------------------------------------------------------
>List Archives: http://www.webelists.com/cgi/lyris.pl?
enter=exchangelist
>Exchange Newsletters:
http://www.msexchange.org/pages/newsletter.asp
>Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?
type=FAQ
>------------------------------------------------------
>Other Internet Software Marketing Sites:
>World of Windows Networking:
http://www.windowsnetworking.com
>Leading Network Software Directory:
http://www.serverfiles.com
>No.1 ISA Server Resource Site: http://www.isaserver.org
>Windows Security Resource Site:
http://www.windowsecurity.com/
>Network Security Library: http://www.secinf.net/
>Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
>------------------------------------------------------
>You are currently subscribed to this MSEXchange.org
Discussion List as:
>glara@xxxxxxx
>To unsubscribe visit
>http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
>Report abuse to listadmin@xxxxxxxxxxxxxx
>
>------------------------------------------------------
>List Archives: http://www.webelists.com/cgi/lyris.pl?
enter=exchangelist
>Exchange Newsletters:
http://www.msexchange.org/pages/newsletter.asp
>Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?
type=FAQ
>------------------------------------------------------
>Other Internet Software Marketing Sites:
>World of Windows Networking:
http://www.windowsnetworking.com
>Leading Network Software Directory:
http://www.serverfiles.com
>No.1 ISA Server Resource Site: http://www.isaserver.org
>Windows Security Resource Site:
http://www.windowsecurity.com/
>Network Security Library: http://www.secinf.net/
>Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
>------------------------------------------------------
>You are currently subscribed to this MSEXchange.org
Discussion List as: ssgill@xxxxxxxxxxxxxxxxxxxx
>To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?
enter=exchangelist
>Report abuse to listadmin@xxxxxxxxxxxxxx
Sarbjit Singh Gill
ssgill@xxxxxxxxxxxxxxxxxxxx
Other related posts:
