Okay, here's the deal: on the same box as Imail, you set up MS SMTP (free with NT Server) to listen on port 26 or what-have-you (this is just to avoid conflicting with Imail--we won't be sending to it via SMTP). Then you set up MS' upstream relay (Default Host) to [127.0.0.1]--meaning that it will send all external messages directly to the Imail server on port 25. THEN you can use MS' \pickup directory, which is a really cool feature that lets you dump messages in the standard RFC 822 format, including any customized headers, message IDs, whatever. And the pickup directory will send any file you dump in there, regardless of file extension--it just needs to have the basic To:, From:, and Subject: fields, no queue control files or anything else.
If this sounds appealing, I'll give you more details. Note that you can also drop into Imail's spool directory, but that I found it prohibitively cumbersome due to the need to create two files and other queue-management difficulties. With MS SMTP, you can manage the utilization of your custom messaging system separately from Imail's general statistics (if the server is also in general use), and it's multithreaded and quite efficient.
Sandy
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jared Holmberg
Sent: Friday, December 08, 2000 12:23 PM
To: '[EMAIL PROTECTED]'
Subject: [IMail Forum] headerstill desperate looking for a way to write the email header rather than relying on iMail to create it for me. Anyone with ideas?Or, does anyone know if adding {$TEXT$} before the <emailaddress> would still work properly?Jared Holmberg
graphics team lead
8500 west 110th street
overland park, ks 66210
e. [EMAIL PROTECTED]
p. 913.469.5900x1154
f. 913.253.1154
