Yes, it does not work.

rich
----- Original Message -----
From: "Ben Johansen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 15, 2001 6:27 PM
Subject: RE: MS EXCHANGE ATTACH PARAMATER


> Hi Rich,
>
> Have you tried it in the Raw Standard format RFC-822 (Below)
>
> RFC-822 message format info
> --------------------------
> RAW mail consists of a series of required and optional text headers
followed
> by a message body.   Most headers consist of a token followed by a value
> enclosed in <> symbols.  Each header line ends with a <CRLF> combination
of
> characters.  All text, headers and body, are plain ASCII and are contained
> in a file which ends with the extension: RAW.  Headers are separated from
> the message body by a blank line and are case insensitive.  The from and
to
> headers are the only ones which are required.
>
> From <[EMAIL PROTECTED]>
> "This field contains the email address of the sender."
>
> To <[EMAIL PROTECTED] [, [EMAIL PROTECTED]]>
> "This field contains the email address(es) of the recipient(s).  Multiple
> recipients can be specified by separating each one with a comma
character."
>
> ReplyTo <[EMAIL PROTECTED]>
> "An optional email address where replies to this message will be
directed."
>
> CC <[EMAIL PROTECTED][, [EMAIL PROTECTED]]>
> "An optional list of carbon copy recipients of this message.  Multiple
> carbon recipients can be specified by separating each one with a comma
> character."
>
> Subject <text> "An optional subject for the message."
>
> Header <Header: Value> "Allows you to explicitly place Header/Value
> combinations into the message."
>
>
> File attachment and encoding:
> -------------------------------
> X-FLAG=ATTACH <filepath, method> [-X]
> Example: X-FLAG=ATTACH <c:\utils\pkzip.exe, MIME> -x
>
> This X-FLAG specifies the value "ATTACH" along with two parameters within
> the <> characters.  The first parameter is a complete path to the file
which
> should be attached to the message.  The second parameter which is
separated
> from the first by a comma character and specifies the method of encoding
> that is to be used when attaching the message.  MDaemon Server v4 supports
> two values for this parameter.  The method of MIME instructs the server to
> use the Internet standard Base64 method of message encoding.  The method
of
> ASCII instructs the server to simply import the file into the message.
An
> optional -X parameter at the end of the string instructs the server to
> remove the file from disk once it has been attached.
>
> Sample RAW mail messages:
> 1)
>
> from <[EMAIL PROTECTED]>
> to <[EMAIL PROTECTED]>
>
> Hello John!
>
> 2)
>
> from <[EMAIL PROTECTED]>
> to <[EMAIL PROTECTED]>
> subject <Secret FBI Files>
> X-FLAG=CONFIRM_DELIVERY
> X-FLAG=ATTACH <c:\secret\files\dole.zip, MIME> -X
>
>
> Ben Johansen - www.pcforge.com
> list commands: www.pcforge.com/WiTangoTalk.htm
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of rich
> Sent: Monday, October 15, 2001 2:34 PM
> To: [EMAIL PROTECTED]
> Subject: MS EXCHANGE ATTACH PARAMATER
>
>
> Does anyone know the format of the MS EXCHANGE parameter for an
attachment.
> I am formating a email message that needs an attachment. I can get the
email
> to go by putting it in the exchange pickup folder but I need the format of
> the attach line.
>
> Rich
>
>

Reply via email to