 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Problem forwarding email to external address.</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/problem-forwarding-email-to-external-address/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/problem-forwarding-email-to-external-address/</link>
	<description></description>
	<lastBuildDate>Sat, 25 May 2013 05:16:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: astronomer</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/problem-forwarding-email-to-external-address/#comment-43205</link>
		<dc:creator>astronomer</dc:creator>
		<pubDate>Wed, 04 May 2005 16:36:24 +0000</pubDate>
		<guid isPermaLink="false">#comment-43205</guid>
		<description><![CDATA[After seven hours with microsoft yesterday I have what I think is the solution. I can&#039;t be sure of all the things he did on our server during those seven hours but the main things we did are: reconfigured my smtp connector to the 2003 virtual server and all addresses, (*), to a cost of 1, reconfigured the default smtp connector on the exchange 5.5 box to a cost of 100 and pointed it to a non-existent domain. This fixed the issue of email not going out when the 5.5 server was down. 
This didn&#039;t fix the redirection issue but the error message changed so it no longer referred to the 5.5 server. For this issue we re-created the contacts. This time we made sure the option to create an email account was checked. 
He also had me disable the smtp fixup on the pix but I don&#039;t believe this had any effect.
rt]]></description>
		<content:encoded><![CDATA[<p>After seven hours with microsoft yesterday I have what I think is the solution. I can&#8217;t be sure of all the things he did on our server during those seven hours but the main things we did are: reconfigured my smtp connector to the 2003 virtual server and all addresses, (*), to a cost of 1, reconfigured the default smtp connector on the exchange 5.5 box to a cost of 100 and pointed it to a non-existent domain. This fixed the issue of email not going out when the 5.5 server was down.<br />
This didn&#8217;t fix the redirection issue but the error message changed so it no longer referred to the 5.5 server. For this issue we re-created the contacts. This time we made sure the option to create an email account was checked.<br />
He also had me disable the smtp fixup on the pix but I don&#8217;t believe this had any effect.<br />
rt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: astronomer</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/problem-forwarding-email-to-external-address/#comment-43206</link>
		<dc:creator>astronomer</dc:creator>
		<pubDate>Mon, 02 May 2005 18:58:49 +0000</pubDate>
		<guid isPermaLink="false">#comment-43206</guid>
		<description><![CDATA[I may have found the cause. There is a connector with a name matching the 5.5 server for SMTP with an address of * and a cost of 1. 
To change this should I add another connector for the local virtual server with address * and make the 5.5 connector a higher cost or should I change the 5.5 connector to just the local domain?
I don&#039;t want to remove the 5.5 server until our real email admin comes back. There may be other reasons she hasn&#039;t disabled it yet.
rt]]></description>
		<content:encoded><![CDATA[<p>I may have found the cause. There is a connector with a name matching the 5.5 server for SMTP with an address of * and a cost of 1.<br />
To change this should I add another connector for the local virtual server with address * and make the 5.5 connector a higher cost or should I change the 5.5 connector to just the local domain?<br />
I don&#8217;t want to remove the 5.5 server until our real email admin comes back. There may be other reasons she hasn&#8217;t disabled it yet.<br />
rt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: astronomer</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/problem-forwarding-email-to-external-address/#comment-43207</link>
		<dc:creator>astronomer</dc:creator>
		<pubDate>Mon, 02 May 2005 12:32:11 +0000</pubDate>
		<guid isPermaLink="false">#comment-43207</guid>
		<description><![CDATA[I did more testing last friday. When the 5.5 server is down, no external mail is sent. When I brought it back up, I got the bounce response to the email I sent while the 5.5 system was down. Can someone tell me how to instruct the 2003 server to send mail out directly instead of thru the 5.5 server?
Thanks.
rt ]]></description>
		<content:encoded><![CDATA[<p>I did more testing last friday. When the 5.5 server is down, no external mail is sent. When I brought it back up, I got the bounce response to the email I sent while the 5.5 system was down. Can someone tell me how to instruct the 2003 server to send mail out directly instead of thru the 5.5 server?<br />
Thanks.<br />
rt </p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 5/8 queries in 0.024 seconds using memcached
Object Caching 297/298 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-25 07:22:34 -->