@MimePartAdd

A new MIMEPART segment is appended to HUGEMIMEPART MIMEPART1; the extended MIMEPART field is returned again.

FN FNFLAGS2

Flag   Hex   Dec   Kommentar
MIME_PART_HAS_BOUNDARY   0001   00001   
MIME_PART_HAS_HEADERS   0002   00002   
MIME_PART_BODY_IN_DBOBJECT   0004   00004   
MIME_PART_SHARED_DBOBJECT   0008   00008   Used only with MIME_PART_BODY_IN_DBOBJECT.
MIME_PART_SKIP_FOR_CONVERSION   0010   00016   only used during MIME->CD conversion

FN FNPARTTYPE3:
This parameter specifies the type for the new segment.

MIME_PART_PROLOG   0001   00001
MIME_PART_BODY   0002   00002
MIME_PART_EPILOG   0003   00003
MIME_PART_RETRIEVE_INFO   0004   00004
MIME_PART_MESSAGE   0005   00005

FN FNVERSION4:
This parameter specifies the version for the new segment.
Currently only version 2 is allowed!

TEXT MIMEBOUNDARY5:
This parameter specifies the boundary string for the new MIMEPART segment.
The boundary string is a more or less random string, but it should be unique and must not occur in the actual data so that it can be used as a delimiter.
A boundary string is terminated with "\X0D\0A"!
According to the RFC definition:
The boundary string is introduced with "–" for all parts, and in the epilogue the boundary string is terminated with "–" (before the final "\X0D\0A"; see the last segment in the example below!).
A segment does not necessarily have to contain a boundary string!

TEXT MIMEHEADERS56:
This parameter specifies the header lines for the new MIMEPART segment.
The header lines may contain various information about the body or, for example, define the boundary string.
A header line is terminated with "\X0D\0A"; the complete header is terminated with "\X0D\0A\X0D\0A"!
A segment does not necessarily have to contain header lines!

TEXT MIMEBODY7:
This parameter specifies the actual body of the new MIMEPART segment.
The body may contain the default text for non-HTML mail clients, or the reference to the attachment in the document with the HTML text (mime.htm) for HTML mail clients.
A segment does not necessarily have to contain a body!

On success, the return value of the function is the extended MIMEPART field.

Example @MimePartAdd(MIMEPART1;FNFLAGS2;FNPARTTYPE3;FNVERSION4;MIMEBOUNDARY5;MIMEHEADERS6;MIMEBODY7);

/*Create a typical MimePart field:*/
MIMEPART1:=@HugeMimePart;
Version:=2;

Flags:=2;
PartType:=1;
MimeBoundary:="";

MIMEPART1:=@MimePartAdd(MIMEPART1;Flags;PartType;Version;MimeBoundary;MimeHeaders;MimeBody);

Flags:=3;
PartType:=2;
MimeBoundary:="\X0D\X0A–_———-=_MCPart_1267956056\X0D\X0A";
MimeHeaders:="Content-Transfer-Encoding: quoted-printable\X0D\X0AContent-Type: text/plain; charset=\"utf-8\"; format=\"fixed\"\X0D\X0A\X0D\X0A";

MIMEPART1:=@MimePartAdd(MIMEPART1;Flags;PartType;Version;MimeBoundary;MimeHeaders;MimeBody);

Flags:=15;
PartType:=2;
MimeBoundary:="\X0D\X0A–_———-=_MCPart_1267956056\X0D\X0A";
MimeHeaders:="Content-Transfer-Encoding: 8bit\X0D\X0AContent-Type: text/html; charset=\"utf-8\"\X0D\X0A\X0D\X0A";

MIMEPART1:=@MimePartAdd(MIMEPART1;Flags;PartType;Version;MimeBoundary;MimeHeaders;MimeBody);

Flags:=1;
PartType:=3;
MimeBoundary:="\X0D\X0A–_———-=_MCPart_1267956056–\X0D\X0A";
MimeHeaders:="";

MIMEPART1:=@MimePartAdd(MIMEPART1;Flags;PartType;Version;MimeBoundary;MimeHeaders;MimeBody);

Es durch mehrere @MimePartAdd calls create a typical MIMEPART field.

Note : This text was machine-translated and may contain inaccuracies.