RE: Exchange relay

  • From: "Medeiros, Jose" <jmedeiros@xxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 9 Jun 2005 18:06:16 -0700

Hi Andrew, 

Add the printers IP address as one of the exceptions in the SMTP Relay 
configuration menu, that way the mail server will not require SMTP 
authentication on send.

Jose

-----Original Message-----
From: Andrew English [mailto:andrew@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, June 09, 2005 5:44 PM
To: [ExchangeList]
Subject: [exchangelist] Exchange relay


http://www.MSExchange.org/

I am running Exchange 2003 Server which is IP 192.168.0.3, I have a
Xerox WorkCentre Pro 55 copier which also does email on the same
network; IP address 192.168.0.114

I am having an issue with SMTP internally. When I send out a email via
the Xerox it never goes out unless I setup the Xerox to authenticate
with the SMTP server and add the user associated to the Xerox machine
(info@xxxxxxxxxxx) to the Exchange Relay as a able user to relay.

Is this the correct method or is there a better way to do it? 

Andrew


------------------------------------------------------
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: 
jmedeiros@xxxxxxxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx



Other related posts: