InfoPath Dev

I have discovered that I can use JScript MailEnvelope and this will allow me to include my form in the body of the email but the disadvantage is that the infopath xml form will automatically be sent with the email and I have no control over this in InfoPath 2003.  I also discovered that I can control the email attachment by using the emailadapter but the disadvantage is that I can no longer use my form in the body of the email. 

 Does any one know how I can either combine the two or if their is some other code that I can use either in the xsn file or something that I am overlooking that will allow me to disable the xml attachment.  We do not want the xml attachment automatically sent with the email.  I know that this has been resolved in InfoPath 2007 but upgrading to this version within our company is not an option.  I have been looking through many books, forums and articles and no one seems to have an answer.  Your assistance is greatly appreciated.  Thank you. 

please have a look here http://www.infopathdev.com/forums/thread/12614.aspx especially for the post of julie. hope this helps.

Thank you for the reference to the link.  I unfortunately have already read this link previously during my research.  The code I am very familiar with because it is one that I have utilized.  The problem that still remains I have to make sacrifices for the use of MailEnvelope or EmailAdapter.  I need to deliver the form in its entirety within the body of the email and at the same time prevent the xml form attachment from going out with the email.  We do not want to recreate the form in plain text because this would sacrifice the asthetic look and feel of the email. 

Hopefully someone knows of a way that I can modify the code in some way that would allow me to use the best of both worlds as they pertain to the MailEvnelope and EmailAdapter.  I still can't believe someone at Microsoft did not consider the idea that someone would want to disable the feature of sending the xml file with the email.  I know it has been resolved in InfoPath 2007 so I figure there must have been a work around for InfoPath 2003.  Any ideas?