Mime C Library Reference
Mime
Chilkat MIME allows you to easily create and manipulate MIME and S/MIME messages from within your applications. ("Chilkat MIME" may be referred to as "Chilkat S/MIME" on some chilkatsoft.com web pages. They are the same product.) The Chilkat MIME license also includes the Chilkat DKIM C library/class/libs for creating and verifying DKIM / DomainKey signatures.
Create/Dispose
HCkMime CkMime_Create(void);
Creates an instance of the CkMime object and returns a handle (i.e. a "void *" pointer). The handle is passed in the 1st argument for the functions listed on this page.
void CkMime_Dispose(HCkMime handle);
Objects created by calling CkMime_Create must be freed by calling this method. A memory leak occurs if a handle is not disposed by calling this function.
C "Properties"
void CkMime_getBoundary(HCkMime cHandle, HCkString retval);
void CkMime_putBoundary(HCkMime cHandle, const char *newVal);
The boundary string for a multipart MIME message.
It is the value of the boundary attribute of the Content-Type header field. For example, if the Content-Type header is this:
Content-Type: multipart/mixed; boundary="------------080707010302060306060800"
then the value of the Boundary property is "------------080707010302060306060800".
When building multipart MIME messages, the boundary is automatically generated by methods such as NewMultipartMixed, to be a unique and random string, so explicitly setting the boundary is usually not necessary.
void CkMime_getCharset(HCkMime cHandle, HCkString retval);
void CkMime_putCharset(HCkMime cHandle, const char *newVal);
The value of the "charset" attribute of the Content-Type header field. For example, if the Content-Type header is this:
Content-Type: text/plain; charset="iso-8859-1"
then the value of the Charset property is "iso-8859-1".
void CkMime_getContentType(HCkMime cHandle, HCkString retval);
void CkMime_putContentType(HCkMime cHandle, const char *newVal);
The MIME content type, such as "text/plain", "text/html", "image/gif", "multipart/alternative", "multipart/mixed", etc.
It is the value of the Content-Type header field, excluding any attributes. For example, if the Content-Type header is this:
Content-Type: multipart/mixed; boundary="------------080707010302060306060800"
then the value of the ContentType property is "multipart/mixed".
void CkMime_getCurrentDateTime(HCkMime cHandle, HCkString retval);
Returns the current date/time in RFC 822 format.
void CkMime_getDisposition(HCkMime cHandle, HCkString retval);
void CkMime_putDisposition(HCkMime cHandle, const char *newVal);
The value of the Content-Disposition header field, excluding any attributes. For example, if the Content-Disposition header is this:
Content-Disposition: attachment; filename="starfish.gif"
then the value of the Disposition property is "attachment".
void CkMime_getEncoding(HCkMime cHandle, HCkString retval);
void CkMime_putEncoding(HCkMime cHandle, const char *newVal);
The value of the Content-Transfer-Encoding header field. Typical values are "base64", "quoted-printable", "7bit", "8bit", "binary", etc. For example, if the Content-Transfer-Encoding header is this:
Content-Transfer-Encoding: base64
then the value of the Encoding property is "base64".
void CkMime_getFilename(HCkMime cHandle, HCkString retval);
void CkMime_putFilename(HCkMime cHandle, const char *newVal);
The value of the "filename" attribute of the Content-Disposition header field. For example, if the Content-Disposition header is this:
Content-Disposition: attachment; filename="starfish.gif"
then the value of the Filename property is "starfish.gif".
void CkMime_getLastErrorHtml(HCkMime cHandle, HCkString retval);
Error information in HTML format for the last method called.
void CkMime_getLastErrorText(HCkMime cHandle, HCkString retval);
Error information in plain-text format for the last method called.
void CkMime_getLastErrorXml(HCkMime cHandle, HCkString retval);
Error information in XML format for the last method called.
void CkMime_getMicalg(HCkMime cHandle, HCkString retval);
void CkMime_putMicalg(HCkMime cHandle, const char *newVal);
The value of the "micalg" attribute of the Content-Type header field. For example, if the Content-Type header is this:
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1;
boundary="------------ms000908010507020408060303"
then the value of the Micalg property is "sha".
Note: The micalg attribute is only present in PKCS7 signed MIME. Setting the Micalg property has the effect of choosing the hash algorithm used w/ signing. Possible choices are "sha1", "md5", "sha256", "sha384", and "sha512". However, it is preferable to set the signing hash algorithm by setting the SigningHashAlg property instead.
void CkMime_getName(HCkMime cHandle, HCkString retval);
void CkMime_putName(HCkMime cHandle, const char *newVal);
The value of the "name" attribute of the Content-Type header field. For example, if the Content-Type header is this:
Content-Type: image/gif; name="starfish.gif"
then the value of the Name property is "starfish.gif".
long CkMime_getNumEncryptCerts(HCkMime cHandle);
The number of certificates found when decrypting S/MIME. This property is set after UnwrapSecurity is called.
long CkMime_getNumHeaderFields(HCkMime cHandle);
The number of header fields. Header field names and values can be retrieved by index (starting at 0) by calling GetHeaderFieldName and GetHeaderFieldValue.
long CkMime_getNumParts(HCkMime cHandle);
The number of sub-parts contained within this message. Each sub-part is a complete Chilkat MIME message itself.
long CkMime_getNumSignerCerts(HCkMime cHandle);
The number of certificates found when verifying signature(s). This property is set after UnwrapSecurity is called.
void CkMime_getPkcs7CryptAlg(HCkMime cHandle, HCkString retval);
void CkMime_putPkcs7CryptAlg(HCkMime cHandle, const char *newVal);
When the MIME is encrypted (using PKCS7 public-key encryption), this selects the underlying symmetric encryption algorithm. Possible values are: "aes", "des", "3des", and "rc2".
int CkMime_getPkcs7KeyLength(HCkMime cHandle);
void CkMime_putPkcs7KeyLength(HCkMime cHandle, int newVal);
When the MIME is encrypted (using PKCS7 public-key encryption), this selects the key length of the underlying symmetric encryption algorithm. The possible values allowed depend on the Pkcs7CryptAlg property. For "aes", the key length may be 128, 192, or 256. For "3des" the key length must be 192. For "des" the key length must be 40. For "rc2" the key length can be 40, 56, 64, or 128.
void CkMime_getProtocol(HCkMime cHandle, HCkString retval);
void CkMime_putProtocol(HCkMime cHandle, const char *newVal);
The value of the "protocol" attribute of the Content-Type header field. For example, if the Content-Type header is this:
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1;
boundary="------------ms000908010507020408060303"
then the value of the Protocol property is "application/x-pkcs7-signature".
void CkMime_getSigningHashAlg(HCkMime cHandle, HCkString retval);
void CkMime_putSigningHashAlg(HCkMime cHandle, const char *newVal);
Selects the underlying hash algorithm used when creating signed (PKCS7) MIME. Possible values are "sha1", "sha256", "sha384", "sha512", "md5", and "md2".
BOOL CkMime_getUnwrapExtras(HCkMime cHandle);
void CkMime_putUnwrapExtras(HCkMime cHandle, BOOL newVal);
Controls whether extra (informative) header fields are added to the MIME message when unwrapping security.
BOOL CkMime_getUseMmDescription(HCkMime cHandle);
void CkMime_putUseMmDescription(HCkMime cHandle, BOOL newVal);
Controls whether the boilerplate text "This is a multi-part message in MIME format." is used as the body content of a multipart MIME part.
BOOL CkMime_getUtf8(HCkMime cHandle);
void CkMime_putUtf8(HCkMime cHandle, BOOL newVal);
When set to true, all "const char *" arguments are expected to be utf-8 strings. If set to false, the "const char *" arguments are expected to be ANSI strings.
BOOL CkMime_getVerboseLogging(HCkMime cHandle);
void CkMime_putVerboseLogging(HCkMime cHandle, BOOL newVal);
If true, increases the amount of information available in LastErrorText (or LastErrorXml / LastErrorHtml). The default is false.
void CkMime_getVersion(HCkMime cHandle, HCkString retval);
The version, such as "1.0.0".
C "Methods"
void CkMime_AddContentLength(HCkMime cHandle);
Computes the size of the MIME body and adds a Content-Length header field with the computed value. If the MIME body is non-multipart, the Content-Length is just the size of the content. If the MIME is multipart, then the Content-Length is the sum of all the sub-parts. Calling this method more than once causes the Content-Length header to be re-computed and updated.
BOOL CkMime_AddDetachedSignature(HCkMime cHandle, HCkCert cert);
Signs the message using the certificate provided. If successful, the message is converted to "multipart/signed" and the original message will be contained in the first sub-part. Returns TRUE for success, FALSE for failure.
BOOL CkMime_AddDetachedSignature2(HCkMime cHandle, HCkCert cert, BOOL transferHeaderFields);
Same as AddDetachedSignature, except an extra argument is provided to control whether header fields from the calling MIME object are transferred to the content part of the multipart/signed object. This method transforms the calling object into a multipart/signed MIME with two sub-parts. The first contains the original content of the calling object, and the second contains the digital signature. Returns TRUE for success, FALSE for failure.
BOOL CkMime_AddDetachedSignaturePk(HCkMime cHandle, HCkCert cert, HCkPrivateKey privateKey);
To be documented soon.
BOOL CkMime_AddDetachedSignaturePk2(HCkMime cHandle, HCkCert cert, HCkPrivateKey privateKey, BOOL transferHeaderFields);
To be documented soon.
BOOL CkMime_AddEncryptCert(HCkMime cHandle, HCkCert cert);
Adds a certificate to the object's internal list of certificates to be used when the EncryptN method is called. (See the EncryptN method for more information.) The internal list may be cleared by calling ClearEncryptCerts. Returns TRUE for success, FALSE for failure.
BOOL CkMime_AddHeaderField(HCkMime cHandle, const char *name, const char *value);
Adds a header field to the MIME.
BOOL CkMime_AddPfxSourceData(HCkMime cHandle, HCkByteData pfxData, const char *password);
Adds a PFX to the object's internal list of sources to be searched for certificates and private keys when decrypting . Multiple PFX sources can be added by calling this method once for each. (On the Windows operating system, the registry-based certificate stores are also automatically searched, so it is commonly not required to explicitly add PFX sources.)
The pfxFileData contains the bytes of a PFX file (also known as PKCS12 or .p12). Returns TRUE for success, FALSE for failure.
BOOL CkMime_AddPfxSourceFile(HCkMime cHandle, const char *pfxFilePath, const char *password);
Adds a PFX file to the object's internal list of sources to be searched for certificates and private keys when decrypting. Multiple PFX files can be added by calling this method once for each. (On the Windows operating system, the registry-based certificate stores are also automatically searched, so it is commonly not required to explicitly add PFX sources.)
The ARG1 contains the bytes of a PFX file (also known as PKCS12 or .p12). Returns TRUE for success, FALSE for failure.
BOOL CkMime_AppendPart(HCkMime cHandle, HCkMime mime);
Appends a MIME message to the sub-parts of this message. Arbitrarily complex messages with unlimited nesting levels can be created. If the calling Mime object is not already multipart, it is automatically converted to multipart/mixed first.
BOOL CkMime_AppendPartFromFile(HCkMime cHandle, const char *filename);
Loads a file and creates a Mime message object using the file extension to determine the content type, and adds it as a sub-part to the calling object. Returns TRUE for success, FALSE for failure.
BOOL CkMime_AsnBodyToXml(HCkMime cHandle, HCkString outStr);
To be documented soon.
void CkMime_ClearEncryptCerts(HCkMime cHandle);
Clears the internal list of certificates added by previous calls to the AddEncryptCert method. (See the EncryptN method for information about encrypting using multiple certificates.)
BOOL CkMime_ContainsEncryptedParts(HCkMime cHandle);
Returns true if the MIME message contains encrypted parts.
Note: This method examines the MIME as-is. If UnwrapSecurity is called and it is successful, then the MIME should no longer contain encrypted parts, and this method would return 0.
Note: If a signed MIME message is then encrypted, then it is not possible to know that the MIME is both encrypted and signed until UnwrapSecurity is called. (In other words, it is not possible to know the contents of the encrypted MIME until it is decrypted.) Therefore, the ContainsSignedParts method would return false.
BOOL CkMime_ContainsSignedParts(HCkMime cHandle);
Returns true if the MIME message contains signed parts.
Note: This method examines the MIME as-is. If UnwrapSecurity is called and it is successful, then the MIME should no longer contain signed parts, and this method would return 0.
Note: If a signed MIME message is then encrypted, then it is not possible to know that the MIME is both encrypted and signed until UnwrapSecurity is called. (In other words, it is not possible to know the contents of the encrypted MIME until it is decrypted.) Therefore, the ContainsSignedParts method would return false.
Note: The same concept also applies to opaque signatures, such as with the MIME produced by calling ConvertToSigned.
void CkMime_Convert8Bit(HCkMime cHandle);
Changes the content-transfer-encoding to "base64" for all 8bit or binary MIME subparts. This allows for the MIME to be exported as a string via the GetMime method.
void CkMime_ConvertToMultipartAlt(HCkMime cHandle);
To be documented soon. Returns TRUE for success, FALSE for failure.
void CkMime_ConvertToMultipartMixed(HCkMime cHandle);
To be documented soon. Returns TRUE for success, FALSE for failure.
BOOL CkMime_ConvertToSigned(HCkMime cHandle, HCkCert cert);
Digitally signs a MIME message. The MIME is converted to an application/x-pkcs7-mime which is a PKCS7 signature that includes both the original MIME message and the signature. This is different than AddDetachedSignature, where the signature is appended to the MIME.
Note: This is commonly referred to as an "opaque" signature. Returns TRUE for success, FALSE for failure.
BOOL CkMime_ConvertToSignedPk(HCkMime cHandle, HCkCert cert, HCkPrivateKey privateKey);
To be documented soon. Returns TRUE for success, FALSE for failure.
BOOL CkMime_Decrypt(HCkMime cHandle);
If the MIME is PKCS7 encrypted, this method can decrypt. Information about the certificates required for decryption is always embedded within a PKCS7 enveloped (i.e. encrypted) message. This method will automatically use this information to locate the certificate + private key in Windows-based registry stores. If the cert + private key was previously installed, such as from a PFX, then the Decrypt method should be able to find it.
If the required cert + private key was NOT previously installed, then it is possible to use PFX files directly. See the AddPfxSourceData and AddPfxSourceFile methods for more information. (Also, see the example linked below.) Returns TRUE for success, FALSE for failure.
BOOL CkMime_Decrypt2(HCkMime cHandle, HCkCert cert, HCkPrivateKey privateKey);
To be documented soon. Returns TRUE for success, FALSE for failure.
BOOL CkMime_DecryptUsingPfxData(HCkMime cHandle, HCkByteData pfxData, const char *password);
Decrypts MIME using a specific PFX ( also known as PKCS12, which is a file format commonly used to store private keys with accompanying public key certificates, protected with a password-based symmetric key). This method allows the bytes of the PKCS12 file to be passed directly, thus allowing PKCS12's to be persisted and retrieved from non-file-based locations, such as in LDAP or a database. Returns TRUE for success, FALSE for failure.
BOOL CkMime_DecryptUsingPfxFile(HCkMime cHandle, const char *pfxFilePath, const char *password);
Decrypts MIME using a specific PFX file (also known as PKCS12) as the source for any required certificates and private keys. (Note: .pfx and .p12 files are both PKCS12 format.) Returns TRUE for success, FALSE for failure.
BOOL CkMime_Encrypt(HCkMime cHandle, HCkCert cert);
Encrypts the MIME to create PKCS7 encrypted MIME. A digital certificate (which always contains a public-key) is used to encrypt. Returns TRUE for success, FALSE for failure.
BOOL CkMime_EncryptN(HCkMime cHandle);
Encrypt MIME using any number of digital certificates. Each certificate to be used must first be added by calling AddEncryptCert (once per certificate). See the example code below: Returns TRUE for success, FALSE for failure.
HCkStringArray CkMime_ExtractPartsToFiles(HCkMime cHandle, const char *dirPath);
Recursively descends through the parts of a MIME message and extracts all parts having a filename to a file. The files are created in dirPath. Returns a (Ck)StringArray object containing the names of the files created. The filenames are obtained from the "filename" attribute of the content-disposition header. If a filename does not exist, then the MIME part is not saved to a file. Returns a null reference on failure
BOOL CkMime_GetBodyBinary(HCkMime cHandle, HCkByteData outData);
Returns the body of the MIME message as a block of binary data. The body is automatically converted from its encoding type, such as base64 or quoted-printable, before being returned.
BOOL CkMime_GetBodyDecoded(HCkMime cHandle, HCkString outStr);
Returns the body of the MIME message as a string. The body is automatically converted from its encoding type, such as base64 or quoted-printable, before being returned.
BOOL CkMime_GetBodyEncoded(HCkMime cHandle, HCkString outStr);
Returns the body of the MIME message as a String. The body is explicitly not decoded from it's encoding type, so if it was represented in Base64, you will get the Base64 encoded body, as an example.
HCkCert CkMime_GetEncryptCert(HCkMime cHandle, long index);
Returns the Nth certificate found when decrypting. The EncryptCerts property contains the number of certificates.
void CkMime_GetEntireBody(HCkMime cHandle, HCkString outStr);
Returns the entire MIME body, including all sub-parts.
void CkMime_GetEntireHead(HCkMime cHandle, HCkString outStr);
Returns the MIME header.
BOOL CkMime_GetHeaderField(HCkMime cHandle, const char *name, HCkString outStr);
Returns the value of a MIME header field. fieldName is case-insensitive.
BOOL CkMime_GetHeaderFieldAttribute(HCkMime cHandle, const char *name, const char *attrName, HCkString outStr);
Parses a MIME header field and returns the value of an attribute. MIME header fields w/ attributes are formatted like this:
Header-Name: value; attrName1="value1"; attrName2="value2"; .... attrNameN="valueN"
Semi-colons separate attribute name=value pairs. The Content-Type header field often contains attributes. Here is an example:
Content-Type: multipart/signed;
protocol="application/x-pkcs7-signature";
micalg=SHA1;
boundary="----=_NextPart_000_0000_01CB03E4.D0BAF010"
In the above example, to access the value of the "protocol" attribute, call GetHeaderFieldAttribute("Content-Type", "protocol");
BOOL CkMime_GetHeaderFieldName(HCkMime cHandle, int index, HCkString outStr);
Returns the Nth MIME header field name.
BOOL CkMime_GetHeaderFieldValue(HCkMime cHandle, int index, HCkString outStr);
Returns the Nth MIME header field value.
BOOL CkMime_GetMime(HCkMime cHandle, HCkString outStr);
Returns a string containing the complete MIME message, including all sub-parts.
BOOL CkMime_GetMimeBytes(HCkMime cHandle, HCkByteData outBytes);
Returns a byte array containing the complete MIME message, including all sub-parts.
HCkMime CkMime_GetPart(HCkMime cHandle, long index);
Returns the Nth sub-part of the MIME message. Indexing begins at 0.
BOOL CkMime_GetSignatureSigningTime(HCkMime cHandle, int index, SYSTEMTIME *outSysTime);
To be documented soon.
HCkCert CkMime_GetSignerCert(HCkMime cHandle, long index);
Returns the Nth digital certificate used to sign the MIME message. Indexing begins at 0.
BOOL CkMime_GetXml(HCkMime cHandle, HCkString outStr);
Converts the MIME (or S/MIME) message to XML and returns the XML as a string.
BOOL CkMime_HasSignatureSigningTime(HCkMime cHandle, int index);
To be documented soon.
BOOL CkMime_IsApplicationData(HCkMime cHandle);
Return true if the MIME message contains application data, otherwise returns false.
BOOL CkMime_IsAttachment(HCkMime cHandle);
Return true if this MIME message is an attachment, otherwise returns false.
BOOL CkMime_IsAudio(HCkMime cHandle);
Return true if the MIME message contains audio data, otherwise returns false.
BOOL CkMime_IsEncrypted(HCkMime cHandle);
Returns true if the MIME message is PKCS7 encrypted, otherwise returns false.
BOOL CkMime_IsHtml(HCkMime cHandle);
Return true if the MIME body is HTML, otherwise returns false.
BOOL CkMime_IsImage(HCkMime cHandle);
Return true if the MIME message contains image data, otherwise returns false.
BOOL CkMime_IsMultipart(HCkMime cHandle);
Return true if the MIME message is multipart (multipart/mixed, multipart/related, multipart/alternative, etc.), otherwise returns false.
BOOL CkMime_IsMultipartAlternative(HCkMime cHandle);
Return true if the MIME message is multipart/alternative, otherwise returns false.
BOOL CkMime_IsMultipartMixed(HCkMime cHandle);
Return true if the MIME message is multipart/mixed, otherwise returns false.
BOOL CkMime_IsMultipartRelated(HCkMime cHandle);
Return true if the MIME message is multipart/related, otherwise returns false.
BOOL CkMime_IsPlainText(HCkMime cHandle);
Return true if the MIME message body is plain text, otherwise returns false.
BOOL CkMime_IsSigned(HCkMime cHandle);
Return true if the MIME message is PKCS7 digitally signed, otherwise returns false.
BOOL CkMime_IsText(HCkMime cHandle);
Return true if the MIME message body is any text content type, such as text/plain, text/html, text/xml, etc., otherwise returns false.
BOOL CkMime_IsUnlocked(HCkMime cHandle);
Returns true if the component is already unlocked, otherwise returns false.
BOOL CkMime_IsVideo(HCkMime cHandle);
Return true if the MIME message contains video data, otherwise returns false.
BOOL CkMime_IsXml(HCkMime cHandle);
Return true if the MIME message body is XML, otherwise returns false.
BOOL CkMime_LoadMime(HCkMime cHandle, const char *mimeMsg);
Discards the current contents of the MIME object and loads a new MIME message from a string.
BOOL CkMime_LoadMimeBytes(HCkMime cHandle, HCkByteData bData);
Loads a MIME document from an in-memory byte array.
BOOL CkMime_LoadMimeFile(HCkMime cHandle, const char *fileName);
Discards the current contents of the MIME object and loads a new MIME message from a file. Returns TRUE for success, FALSE for failure.
BOOL CkMime_LoadXml(HCkMime cHandle, const char *xml);
Converts XML to MIME and replaces the MIME object's contents with the converted XML.
BOOL CkMime_LoadXmlFile(HCkMime cHandle, const char *fileName);
Converts XML to MIME and replaces the MIME object's contents with the converted XML. Returns TRUE for success, FALSE for failure.
BOOL CkMime_NewMessageRfc822(HCkMime cHandle, HCkMime mimeObject);
Clears the Mime object and initializes it such that the header contains a "content-type: message/rfc822" line and the body is the MIME text of the Mime object passed to the method.
BOOL CkMime_NewMultipartAlternative(HCkMime cHandle);
Discards the current MIME message header fields and contents, if any, an initializes the MIME object to be an empty mulipart/alternative message.
BOOL CkMime_NewMultipartMixed(HCkMime cHandle);
Discards the current MIME message header fields and contents, if any, an initializes the MIME object to be an empty mulipart/mixed message.
BOOL CkMime_NewMultipartRelated(HCkMime cHandle);
Discards the current MIME message header fields and contents, if any, an initializes the MIME object to be an empty mulipart/related message.
void CkMime_RemoveHeaderField(HCkMime cHandle, const char *name, BOOL bAllOccurances);
Removes a header field from the MIME header. If bAllOccurances is true, then all occurances of the header field are removed. Otherwise, only the 1st occurance is removed.
BOOL CkMime_RemovePart(HCkMime cHandle, int index);
Removes the Nth subpart from the MIME message.
BOOL CkMime_SaveBody(HCkMime cHandle, const char *filename);
Saves the MIME message body to a file. If the body is base64 or quoted-printable encoded, it is automatically decoded.
BOOL CkMime_SaveLastError(HCkMime cHandle, const char *filename);
Saves the last error information to an XML formatted file.
BOOL CkMime_SaveMime(HCkMime cHandle, const char *filename);
Saves the MIME message to a file, in MIME format. (This is the same as the .EML format used by Microsoft Outlook Express.)
BOOL CkMime_SaveXml(HCkMime cHandle, const char *filename);
Converts the MIME message to XML and saves to an XML file.
void CkMime_SetBody(HCkMime cHandle, const char *str);
Sets the MIME body content to a text string.
BOOL CkMime_SetBodyFromBinary(HCkMime cHandle, HCkByteData dbuf);
Sets the MIME message body from a byte array.
BOOL CkMime_SetBodyFromEncoded(HCkMime cHandle, const char *encoding, const char *str);
Sets the MIME message body from a Base64 or Quoted-Printable encoded string.
BOOL CkMime_SetBodyFromFile(HCkMime cHandle, const char *fileName);
Sets the MIME message body from the contents of a file. Note: A MIME message consists of a header and a body. The body may itself be a MIME message that consists of a header and body, etc. This method loads the contents of a file into the body of a MIME message, without replacing the header.
The Content-Type and Content-Transfer-Encoding header fields are automatically updated to match the type of content loaded (based on file extension). If your application requires the MIME to have a specific Content-Type and/or Content-Transfer-Encoding, set the ContentType and Encoding properties after calling this method (not before).
BOOL CkMime_SetBodyFromHtml(HCkMime cHandle, const char *str);
Sets the MIME message body from a string containing HTML. The Content-Type header is added or updated to the value "text/html".
If 8bit (non-us-ascii) characters are present, and if the Charset property was not previously set, then the "charset" attribute is automatically added to the Content-Type header using the default value of "utf-8". This can be changed at any time by setting the Charset property.
If the Encoding property was not previously set, then the Content-Transfer-Encoding header is automatically added. It will be set to "7bit" or "8bit" depending on whether the HTML body contains 8-bit non-us-ascii characters.
To set the MIME body with no intentional side-effects, use SetBody instead.
BOOL CkMime_SetBodyFromPlainText(HCkMime cHandle, const char *str);
Sets the MIME message body from a string containing plain-text. The Content-Type header is added or updated to the value "text/plain".
If 8bit (non-us-ascii) characters are present, and if the Charset property was not previously set, then the "charset" attribute is automatically added to the Content-Type header using the default value of "utf-8". This can be changed at any time by setting the Charset property.
If the Encoding property was not previously set, then the Content-Transfer-Encoding header is automatically added. It will be set to "7bit" or "8bit" depending on whether the plain-text body contains 8-bit non-us-ascii characters.
To set the MIME body with no intentional side-effects, use SetBody instead.
BOOL CkMime_SetBodyFromXml(HCkMime cHandle, const char *str);
Sets the MIME message body from a string containing XML. The Content-Type header is added or updated to the value "text/xml".
If 8bit (non-us-ascii) characters are present, and if the Charset property was not previously set, then the "charset" attribute is automatically added to the Content-Type header using the default value of "utf-8". This can be changed at any time by setting the Charset property.
If the Encoding property was not previously set, then the Content-Transfer-Encoding header is automatically added. It will be set to "7bit" or "8bit" depending on whether the plain-text body contains 8-bit non-us-ascii characters.
To set the MIME body with no intentional side-effects, use SetBody instead.
BOOL CkMime_SetHeaderField(HCkMime cHandle, const char *name, const char *value);
Adds or replaces a MIME message header field. If the field already exists, it is automatically replaced. Otherwise it is added. Pass zero-length value to remove the header field.
void CkMime_SetVerifyCert(HCkMime cHandle, HCkCert cert);
Allows a certificate to be explicitly specified for verifying a signature.
HCkEmail CkMime_ToEmailObject(HCkMime cHandle);
Returns the MIME message converted to a CkEmail object. Returns a null reference on failure
BOOL CkMime_UnlockComponent(HCkMime cHandle, const char *unlockCode);
Unlocks the component allowing for the full functionality to be used. If this method unexpectedly returns false, examine the contents of the LastErrorText property to determine the reason for failure. Returns TRUE for success, FALSE for failure.
BOOL CkMime_UnwrapSecurity(HCkMime cHandle);
Decrypts and/or verifies all digital signatures contained within the MIME message, and returns true if all decryptions and verifications succeeded. Otherwise returns false. After unwrapping, the information regarding security and certificates can be obtained by the methods GetSignerCert and GetEncryptCert, and the properties NumEncryptCerts and NumSignerCerts.
The MIME is restored to the original structure/content prior to all signing and/or encryption.
The difference between UnwrapSecurity and methods such as Verify or Decrypt is that UnwrapSecurity will recursively traverse the MIME to decrypt and/or verify all parts. Also, UnwrapSecurity will unwrap layers until no further encrypted/signed content is found. For example, if a MIME message was encrypted and then subsequently signed, then UnwrapSecurity will verify and unwrap the detached signature/signed-data layer, and then decrypt the "enveloped data". Returns TRUE for success, FALSE for failure.
void CkMime_UrlEncodeBody(HCkMime cHandle, const char *charset);
To be documented soon.
BOOL CkMime_Verify(HCkMime cHandle);
Verifies PKCS7 signed MIME and "unwraps" the signature. The MIME is restored to the original structure that it would have originally had prior to signing. The Verify method works with both detached signatures, as well as opaque/attached signatures.
A PKCS7 signature usually embeds both the signing certificate with its public key. Therefore, it is usually possible to verify a signature without the need to already have the certificate installed. If the signature does not embed the certificate, the Verify method will automatically locate and use the certificate if it was correctly pre-installed on the computer. Returns TRUE for success, FALSE for failure.
const char *CkMime_asnBodyToXml(HCkMime cHandle);
To be documented soon. Returns a null on failure
const char *CkMime_bodyDecoded(HCkMime cHandle);
Returns the body of the MIME message as a string. The body is automatically converted from its encoding type, such as base64 or quoted-printable, before being returned. Returns a null on failure
const char *CkMime_bodyEncoded(HCkMime cHandle);
Returns the body of the MIME message as a String. The body is explicitly not decoded from it's encoding type, so if it was represented in Base64, you will get the Base64 encoded body, as an example. Returns a null on failure
const char *CkMime_boundary(HCkMime cHandle);
The boundary string for a multipart MIME message.
It is the value of the boundary attribute of the Content-Type header field. For example, if the Content-Type header is this:
Content-Type: multipart/mixed; boundary="------------080707010302060306060800"
then the value of the Boundary property is "------------080707010302060306060800".
When building multipart MIME messages, the boundary is automatically generated by methods such as NewMultipartMixed, to be a unique and random string, so explicitly setting the boundary is usually not necessary. Returns a null on failure
const char *CkMime_charset(HCkMime cHandle);
The value of the "charset" attribute of the Content-Type header field. For example, if the Content-Type header is this:
Content-Type: text/plain; charset="iso-8859-1"
then the value of the Charset property is "iso-8859-1".Returns a null on failure
const char *CkMime_contentType(HCkMime cHandle);
The MIME content type, such as "text/plain", "text/html", "image/gif", "multipart/alternative", "multipart/mixed", etc.
It is the value of the Content-Type header field, excluding any attributes. For example, if the Content-Type header is this:
Content-Type: multipart/mixed; boundary="------------080707010302060306060800"
then the value of the ContentType property is "multipart/mixed".Returns a null on failure
const char *CkMime_currentDateTime(HCkMime cHandle);
Returns the current date/time in RFC 822 format. Returns a null on failure
const char *CkMime_disposition(HCkMime cHandle);
The value of the Content-Disposition header field, excluding any attributes. For example, if the Content-Disposition header is this:
Content-Disposition: attachment; filename="starfish.gif"
then the value of the Disposition property is "attachment".Returns a null on failure
const char *CkMime_encoding(HCkMime cHandle);
The value of the Content-Transfer-Encoding header field. Typical values are "base64", "quoted-printable", "7bit", "8bit", "binary", etc. For example, if the Content-Transfer-Encoding header is this:
Content-Transfer-Encoding: base64
then the value of the Encoding property is "base64".Returns a null on failure
const char *CkMime_entireBody(HCkMime cHandle);
Returns the entire MIME body, including all sub-parts. Returns a null on failure
const char *CkMime_entireHead(HCkMime cHandle);
Returns the MIME header. Returns a null on failure
const char *CkMime_filename(HCkMime cHandle);
The value of the "filename" attribute of the Content-Disposition header field. For example, if the Content-Disposition header is this:
Content-Disposition: attachment; filename="starfish.gif"
then the value of the Filename property is "starfish.gif".Returns a null on failure
const char *CkMime_getBodyDecoded(HCkMime cHandle);
Returns the body of the MIME message as a string. The body is automatically converted from its encoding type, such as base64 or quoted-printable, before being returned. Returns a null on failure
const char *CkMime_getBodyEncoded(HCkMime cHandle);
Returns the body of the MIME message as a String. The body is explicitly not decoded from it's encoding type, so if it was represented in Base64, you will get the Base64 encoded body, as an example. Returns a null on failure
const char *CkMime_getEntireBody(HCkMime cHandle);
Returns the entire MIME body, including all sub-parts. Returns a null on failure
const char *CkMime_getEntireHead(HCkMime cHandle);
Returns the MIME header. Returns a null on failure
const char *CkMime_getHeaderField(HCkMime cHandle, const char *name);
Returns the value of a MIME header field. fieldName is case-insensitive. Returns a null on failure
const char *CkMime_getHeaderFieldAttribute(HCkMime cHandle, const char *name, const char *attrName);
Parses a MIME header field and returns the value of an attribute. MIME header fields w/ attributes are formatted like this:
Header-Name: value; attrName1="value1"; attrName2="value2"; .... attrNameN="valueN"
Semi-colons separate attribute name=value pairs. The Content-Type header field often contains attributes. Here is an example:
Content-Type: multipart/signed;
protocol="application/x-pkcs7-signature";
micalg=SHA1;
boundary="----=_NextPart_000_0000_01CB03E4.D0BAF010"
In the above example, to access the value of the "protocol" attribute, call GetHeaderFieldAttribute("Content-Type", "protocol");Returns a null on failure
const char *CkMime_getHeaderFieldName(HCkMime cHandle, int index);
Returns the Nth MIME header field name. Returns a null on failure
const char *CkMime_getHeaderFieldValue(HCkMime cHandle, int index);
Returns the Nth MIME header field value. Returns a null on failure
const char *CkMime_getMime(HCkMime cHandle);
Returns a string containing the complete MIME message, including all sub-parts. Returns a null on failure
const char *CkMime_getXml(HCkMime cHandle);
Converts the MIME (or S/MIME) message to XML and returns the XML as a string. Returns a null on failure
const char *CkMime_header(HCkMime cHandle, const char *name);
Returns the content of a MIME header field. The "fieldName" is case-insensitive, and if the MIME header field does not exist, an empty string is returned. Returns a null on failure
const char *CkMime_headerName(HCkMime cHandle, int index);
Returns the Nth MIME header field name. Returns a null on failure
const char *CkMime_headerValue(HCkMime cHandle, int index);
Returns the Nth MIME header field value. Returns a null on failure
const char *CkMime_lastErrorHtml(HCkMime cHandle);
Error information in HTML format for the last method called.Returns a null on failure
const char *CkMime_lastErrorText(HCkMime cHandle);
Error information in plain-text format for the last method called.Returns a null on failure
const char *CkMime_lastErrorXml(HCkMime cHandle);
Error information in XML format for the last method called.Returns a null on failure
const char *CkMime_micalg(HCkMime cHandle);
The value of the "micalg" attribute of the Content-Type header field. For example, if the Content-Type header is this:
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1;
boundary="------------ms000908010507020408060303"
then the value of the Micalg property is "sha".
Note: The micalg attribute is only present in PKCS7 signed MIME. Setting the Micalg property has the effect of choosing the hash algorithm used w/ signing. Possible choices are "sha1", "md5", "sha256", "sha384", and "sha512". However, it is preferable to set the signing hash algorithm by setting the SigningHashAlg property instead. Returns a null on failure
const char *CkMime_mime(HCkMime cHandle);
Returns a string containing the complete MIME message, including all sub-parts. Returns a null on failure
const char *CkMime_name(HCkMime cHandle);
The value of the "name" attribute of the Content-Type header field. For example, if the Content-Type header is this:
Content-Type: image/gif; name="starfish.gif"
then the value of the Name property is "starfish.gif".Returns a null on failure
const char *CkMime_pkcs7CryptAlg(HCkMime cHandle);
When the MIME is encrypted (using PKCS7 public-key encryption), this selects the underlying symmetric encryption algorithm. Possible values are: "aes", "des", "3des", and "rc2". Returns a null on failure
const char *CkMime_protocol(HCkMime cHandle);
The value of the "protocol" attribute of the Content-Type header field. For example, if the Content-Type header is this:
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1;
boundary="------------ms000908010507020408060303"
then the value of the Protocol property is "application/x-pkcs7-signature".Returns a null on failure
const char *CkMime_signingHashAlg(HCkMime cHandle);
Selects the underlying hash algorithm used when creating signed (PKCS7) MIME. Possible values are "sha1", "sha256", "sha384", "sha512", "md5", and "md2". Returns a null on failure
const char *CkMime_version(HCkMime cHandle);
The version, such as "1.0.0". Returns a null on failure
const char *CkMime_xml(HCkMime cHandle);
Converts the MIME (or S/MIME) message to XML and returns the XML as a string. Returns a null on failure
|