On Wed, 2 Aug 2000 05:21:03 -0400 (EDT), Thomas wrote:

> That page had nothing to help me with the header format
> for SMTPOP.  SMTPOP12 really ought to include a sample
> message to show the header format.

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
  -----

When sending, the above construct will be sent as follows:

  -----
  ** Trying mail.somehost.net port 25...
  << 220 mail.somehost.net ESMTP server ready
  >> HELO somehost.net
  << 250 mail.somehost.net Nice to meet you
  >> MAIL FROM: <[EMAIL PROTECTED]>
  << 250 Sender <[EMAIL PROTECTED]> Ok
  >> RCPT TO: <[EMAIL PROTECTED]>
  << 250 Recipient <[EMAIL PROTECTED]> Ok
  >> RCPT TO: <[EMAIL PROTECTED]>
  << 250 Recipient <[EMAIL PROTECTED]> Ok
  (more recipientN's RCPTs and 250s snupped for brevity)
  >> RCPT TO: <[EMAIL PROTECTED]>
  << 250 Recipient <[EMAIL PROTECTED]> Ok
  >> RCPT TO: <[EMAIL PROTECTED]>
  << 250 Recipient <[EMAIL PROTECTED]> Ok
  (more cc_recipientN's RCPTs and 250s snupped for brevity)
  >> RCPT TO: <[EMAIL PROTECTED]>
  << 250 Recipient <[EMAIL PROTECTED]> Ok
  >> RCPT TO: <[EMAIL PROTECTED]>
  << 250 Recipient <[EMAIL PROTECTED]> Ok
  (more cc_recipientN's RCPTs and 250s snupped for brevity)
  >> DATA
  << 354 Ok Send data ending with <CRLF>.<CRLF>
  >> From: "Arachne User" <[EMAIL PROTECTED]>
  >> Organization: Arachne Fan Club
  >> 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
  >>
  >> That page had nothing to help me
  >> with the header format for SMTPOP.
  >> SMTPOP12 really ought to include a sample.
  >>
  >> -- This mail was written by user of Arachne
  >> .
  << 250 Message received for delivery: 7736CDAFCF2.AAC4B94
  >> QUIT
  ** Connection closed by remote host
  -----

BTW, why Arachne only recognized one "To:" and one "CC:"
addresses?   The rest are ignored when sending.  It's just
me or something has been changed in Arachne?  IIRC the
older beta versions can accept more than one addresses.

--Eko
http://survpc.virtualave.net/


Reply via email to