Sample code for 30+ languages & platforms
PHP

Add a Detached Signature (Header Placement Control)

See more MIME Examples

Demonstrates the Chilkat Mime.AddDetachedSignature2 method, which creates the same multipart/signed structure as AddDetachedSignature, with a second argument controlling whether the existing message header fields are transferred to the new outer entity.

Note: The file paths are relative to the application's current working directory. Absolute paths may also be used. Supply the paths appropriate to your own environment.

Background: Signing wraps the content in a new outer multipart/signed, which raises the question of where the message-level headers (Subject, From, To) should live. This variant lets you choose: transfer them up to the outer entity so the signed message looks like a normal email, or leave them on the inner part. Transferring is typical for email; the finer control matters when the signed entity is embedded in a larger structure.

Chilkat PHP Downloads

Chilkat2 PHP
<?php

use Chilkat2\Cert;
use Chilkat2\Mime;

$mime = new Mime();
try {
    $mime->SetBodyFromPlainText('This message will be signed.');

    // Load the signing certificate (which must have access to its private key) from a PFX file.
    // The PFX password should come from a secure source rather than being hard-coded.
    $pfxPassword = 'myPfxPassword';
    $cert = new Cert();
    $cert->LoadPfxFile('qa_data/signer.pfx', $pfxPassword);

    // AddDetachedSignature2 is the same as AddDetachedSignature, but the 2nd argument controls whether
    // the existing message header fields are transferred to the new outer multipart/signed entity.
    $transferHeaderFields = true;
    $mime->AddDetachedSignature2($cert, $transferHeaderFields);

    $mime->SaveMime('qa_output/signed.eml');
} catch (\Chilkat2\Exception $e) {
    echo $e->getMessage(), "\n";
    exit;
}

echo "Detached signature added (headers transferred).\n";