Question : XSLT transformation

I have a source XML, part of this XML need to be copied to another XML usig XSLT.
Here is my example source XML
------------------------------------------Source XML--------------------------------------------------------
<?xml version="1.0" encoding="ISO-8859-1"?>

<START>
<URL_Header>
      <urlid>abc1234abc</urlid>
</URL_Header>

<CATALOG>
<CDS>
      <CD>
            <TITLE>Picture book</TITLE>
            <ARTIST>Simply Red</ARTIST>
            <COUNTRY>EU</COUNTRY>
            <COMPANY>Elektra</COMPANY>
            <PRICE>7.20</PRICE>
            <YEAR>1985</YEAR>
      </CD>
      <CD>
            <TITLE>Red</TITLE>
            <ARTIST>The Communards</ARTIST>
            <COUNTRY>UK</COUNTRY>
            <COMPANY>London</COMPANY>
            <PRICE>7.80</PRICE>
            <YEAR>1987</YEAR>
      </CD>
</CDS>
<DVDS>
       <DVD>
            <TITLE>Red</TITLE>
            <ARTIST>The Communards</ARTIST>
            <COUNTRY>UK</COUNTRY>
            <COMPANY>London</COMPANY>
            <PRICE>10.00</PRICE>
            <YEAR>1987</YEAR>
      </DVD>
</DVD>
</CATALOG>
</START>
-----------------------------------Target XML--------------------

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://soap.sforce.com/schemas/class/SAPTestWS">

   <soapenv:Header>

      <sap:AllowFieldTruncationHeader>
        <sap:allowFieldTruncation>true</sap:allowFieldTruncation>
      </sap:AllowFieldTruncationHeader>
      <sap:SessionHeader>
         <sap:sessionId>[b]abc1234abc[/b]</sap:sessionId>
      </sap:SessionHeader>

   </soapenv:Header>

   <soapenv:Body>
     [b] <CATALOG>
   	 <CDS>	
	    <CD>
		<TITLE>Picture book</TITLE>
		<ARTIST>Simply Red</ARTIST>
		<COUNTRY>EU</COUNTRY>
		<COMPANY>Elektra</COMPANY>
		<PRICE>7.20</PRICE>
		<YEAR>1985</YEAR>
	    </CD>
	<CD>
		<TITLE>Red</TITLE>
		<ARTIST>The Communards</ARTIST>
		<COUNTRY>UK</COUNTRY>
		<COMPANY>London</COMPANY>
		<PRICE>7.80</PRICE>
		<YEAR>1987</YEAR>
	</CD>
     </CDS>
     <DVDS>
	 <DVD>
		<TITLE>Red</TITLE>
		<ARTIST>The Communards</ARTIST>
		<COUNTRY>UK</COUNTRY>
		<COMPANY>London</COMPANY>
		<PRICE>10.00</PRICE>
		<YEAR>1987</YEAR>
	</DVD>	
     </DVD>
   </CATALOG>[/b]
   </soapenv:Body>

</soapenv:Envelope>

Answer : XSLT transformation

I couldn't wait to get a answer for this question so i contacted Microsoft. After spending almost 5 hours on the phone with Microsoft business support we have figured out a solution for the issue.

Microsoft says that there is a issue on GoDaddy's end and Microsoft is getting there documentation together to get on a conference call with godaddy to show them there issue...From what they have found when you connect to smtpout.secureserver.net you are connecting to a random SMTP server in a group. Not all those server are responding properly which is causing the failure.

But anyways the solution.
If you do a telnet smtpout.secureserver.net 25
Copy the banner that is presented Example "p3plsmtpa01-v01.prod.phx3.secureserver.net"
In your smarthost configuration replace the smtpout.secureserver.net with that above banner.

If you ran the telnet command a few times the "p3plsmtpa01-v01" portion changes as you connect to different servers. You are able to create a couple smarthosts connecting to these different addresses that way if one of them is down it will role over to the next available...

I know this doesn't solve the smtpout.secureserver.net issue directly but by putting in the direct SMTP server address it will make the server work correctly!