>Pegasus Mail's "glue" header format:
-----
$$ [EMAIL PROTECTED] <-- return path ("eMail" in ARACHNE.CFG)
T [EMAIL PROTECTED] <-- addresses in "To:" field
T [EMAIL PROTECTED]
(add more "T" lines here)
C [EMAIL PROTECTED] <-- addresses in "CC:" field
C [EMAIL PROTECTED]
(add more "C" lines here)
B [EMAIL PROTECTED] <-- addresses in "BCC" field
B [EMAIL PROTECTED] (commonly misused by spammers ;-)
(add more "B" lines here)
<-- one blank line (mandatory)
From: "Arachne User" <[EMAIL PROTECTED]> <- message header
Organization: Arachne Fan Club starts here
Date: Thu, 03 Aug 2000 12:00:50 -0000
X-Mailer: Arachne V1.66
To: [EMAIL PROTECTED], [EMAIL PROTECTED], ...
CC: [EMAIL PROTECTED], [EMAIL PROTECTED], ...
Subject: some subject
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
<-- one blank line (mandatory)
That page had nothing to help me <-- message body starts here
with the header format for SMTPOP.
SMTPOP12 really ought to include a sample.
-- This mail was written by user of Arachne
-----
>
Thanks for this info. But is it necessary for the user to repeat the glue header
info in a set of regular headers? Or does Arachne/Insight do that for you?
