>The other thing that can be done is to embed the content directly into a message. Outlook does this for example if you choose a background for your messages. This is done by embedding the images as multi-part content into the same message. While wwIPStuff can handle attachments (which is essentially what these embedded items are) it can't easily deal with referencing the content embedded. Actually I think it is possible to do this, but I'm not sure what the format for this is.
Here's a sample of the HNY message I recently sent... if anyone can find out how to simulate this, along with proper syntax for content-id and boundary strings. As you said, it's feasible, but it seems to be quite a day's work to achieve.
Content-Type: multipart/related;
boundary="------------020602060702070501010106"
--------------020602060702070501010106
Content-Type: text/html; charset=ISO-8859-2
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-2" http-equiv="Content-Type">
</head>
<body alink="#000099"
background="cid:part1.00040309.09050406@ndragan.com" bgcolor="#ffffff"
link="#000099" text="#ffffff" vlink="#990099">
<font face="Georgia"><b><big><big>All the best wishes for the New 2005<br>
From Nedeljkovich family<br>
</big></big></b><br>
</font>
</body>
</html>
--------------020602060702070501010106
Content-Type: image/jpeg;
name="nova2005.jpg"
Content-Transfer-Encoding: base64
Content-ID: <part1.00040309.09050406@ndragan.com>
Content-Disposition: inline;
filename="nova2005.jpg"
/9j/4AAQSkZJRgABAQEASABIAAD/2wBDAAUDBAQEAwUEBAQFBQUGBwwIBwcHBw8LCwkMEQ8S
EhEPERETFhwXExQaFRERGCEYGh0dHx8fExciJCIeJBweHx7/2wBDAQUFBQcGBw4ICA4eFBEU
[snipped the bulk of the base-64 encoded image]
AelZs+jWiT2sDNLKdjIsshBdFHIUHHT60UU3siU/dfqXrLQIftUkhv8AUDJwNxlGcD8Kswaa
IhKi3lwfJ3FCwRj+OV+br3zRRRFtXSBNnS6dpWyyiX+0tSOB3uT/AE4H0ooorKTd2aKcktz/
2Q==
--------------020602060702070501010106--
--------------080102000403080906080702--
