Hrmm, so what about the header? Do I need to format the header into a string and put both header and body of the embedded message and set body->contents.text.data and body->contents.text.size?

On Thu, 10 Jun 2004 08:59:25 -0700 (PDT), Mark Crispin <[EMAIL PROTECTED]> wrote:

On Thu, 10 Jun 2004, Shawn Walker wrote:
I'm trying to get c-client to see a embedded message that I have inserted in the BODY structure.

I presume that you meant to say, "I am trying to *send* an embedded message, but when I go to read the message that I have sent I see that it is empty."


You apparently missed the point where it says that composing a message that is not of type MULTIPART, you use body->contents.text (store the text in body->contents.text.data and its size in body->contents.text.size).

You do this even when body->type is TYPEMESSAGE and body->subtype is "RFC822"; you supply the complete message in body->contents.text.data instead of using body->nested.msg.

Put another way, when sending, embedded messages look like any other type of text attachments. The body->nested.msg stuff is only used when reading messages. The body structure for a message being sent is not the same as that for a message that was read back.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.





Reply via email to