Thanks for the responses, but so far they have really only muddied the water.
I'm not interested in the stats, ethics, or efficiency of this practice. I'm not even sure if it is any benefit to the particular task at hand. It's more of a mountain that I intend to climb because it's there. What I've discovered so far is that references to attached images in HTML emails are of the form <img src="cid:image.gif";> but image.gif is not the name of the image (although it could be) but is the Content ID. In Perl and PHP solutions you specify a Content ID for each graphic, then call this ID in the HTML. So if you had an image called 'image.gif' you would specify that it's CID is 'image.gif' (or ABC or whatever) and then refer to it in the HTML as <img src="cid:image.gif";> (or <img src="cid:ABC";>). Unforunately the Tango Mail action doesn't provide a CID specification field for attached items. So is anyone actually doing this? If so, how? With a fourth party email app perhaps? No reason why Tango couldn't pass the info to a CGI that does support Content ID specification. Wayne Irvine Byte Services Pty Ltd http://www.byteserve.com.au/ [EMAIL PROTECTED] Ph 02 9960 6099 Mob 0409 960 609 Fax 02 9960 6088 ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
![cid:image.gif"](cid:image.gif"){kind=link}