Pretty Signatures

  use Mail::DKIM::TextWrap;

in your program before generating the signature.

new()

  # create a signer using the default policy
  my $signer = Mail::DKIM::ARC::Signer->new(
                  Algorithm => 'rsa-sha256',
                  Chain => 'none',    # or pass|fail|ar
                  Domain => 'example.org',
                  SrvId => 'example.org',
                  Selector => 'selector1',
                  KeyFile => 'private.key',
                  Headers => 'x-header:x-header2',
             );

Key

rather than using "KeyFile", use "Key" to use an already-loaded Mail::DKIM::PrivateKey object.

Chain

The cv= value for the Arc-Seal header. "ar" means to copy it from an Authentication-Results header, or use none if there isn't one.

SrvId

The authserv-id in the Authentication-Results headers, defaults to Domain.

Headers

A colon separated list of headers to sign, this is added to the list of default headers as shown in in the DKIM specification.

For each specified header all headers of that type which are present in the message will be signed, but we will not oversign or sign headers which are not present.

If you require greater control over signed headers please use the extended_headers() method instead.

The list of headers signed by default is as follows

    From Sender Reply-To Subject Date
    Message-ID To Cc MIME-Version
    Content-Type Content-Transfer-Encoding Content-ID Content-Description
    Resent-Date Resent-From Resent-Sender Resent-To Resent-cc
    Resent-Message-ID
    In-Reply-To References
    List-Id List-Help List-Unsubscribe List-Subscribe
    List-Post List-Owner List-Archive
    

PRINT()

  $signer->PRINT("a line of the message\015\012");

Feeds content of the message being signed into the signer. The API is designed this way so that the entire message does NOT need to be read into memory at once.

Please note that although the PRINT() method expects you to use SMTP-style line termination characters, you should NOT use the SMTP-style dot-stuffing technique described in RFC 2821 section 4.5.2. Nor should you use a <CR><LF>.<CR><LF> sequence to terminate the message.

CLOSE()

  $signer->CLOSE;

This method finishes the canonicalization process, computes a hash, and generates a signature.

extended_headers()

The method expects a HashRef to be passed in.

The Keys are the headers to sign, and the values are either the number of headers of that type to sign, or the special values '*' and '+'.

* will sign ALL headers of that type present in the message.

+ will sign ALL + 1 headers of that type present in the message to prevent additional headers being added.

You may override any of the default headers by including them in the hashref, and disable them by giving them a 0 value.

Keys are case insensitive with the values being added upto the highest value.

    Headers => {
        'X-test'  => '*',
        'x-test'  => '1',
        'Subject' => '+',
        'Sender'  => 0,
    },

add_signature()

  $signer->add_signature(new Mail::DKIM::Signature(...));

Signer policies can use this method to specify complete parameters for the signature to add, including what type of signature. For more information, see Mail::DKIM::SignerPolicy.

algorithm()

  $alg = $signer->algorithm;

  $signer->algorithm('rsa-sha256');

domain()

  $alg = $signer->domain;

  $signer->domain('example.org');

load()

  $signer->load($file_handle);

Reads a complete message from the designated file handle, feeding it into the signer. The message must use <CRLF> line terminators (same as the SMTP protocol).

headers()

  my $headers = $signer->headers;

This is a string containing the names of the header fields that will be signed, separated by colons.

key()

  my $key = $signer->key;

  $signer->key(Mail::DKIM::PrivateKey->load(File => 'private.key'));

The key object can be any object that implements the sign_digest() method. (Providing your own object can be useful if your actual keys are stored out-of-process.)

If you use this method to specify a private key, do not use "key_file()".

key_file()

  my $filename = $signer->key_file;

  $signer->key_file('private.key');

If you use this method to specify a private key file, do not use "key()".

message_originator()

  my $address = $signer->message_originator;

Returns the "originator address" found in the message, as a Mail::Address object. This is typically the (first) name and email address found in the From: header. If there is no From: header, then an empty Mail::Address object is returned.

To get just the email address part, do:

  my $email = $signer->message_originator->address;

See also "message_sender()".

message_sender()

  my $address = $dkim->message_sender;

Returns the "sender" found in the message, as a Mail::Address object. This is typically the (first) name and email address found in the Sender: header. If there is no Sender: header, it is the first name and email address in the From: header. If neither header is present, then an empty Mail::Address object is returned.

To get just the email address part, do:

  my $email = $dkim->message_sender->address;

The "sender" is the mailbox of the agent responsible for the actual transmission of the message. For example, if a secretary were to send a message for another person, the "sender" would be the secretary and the "originator" would be the actual author.

selector()

  $alg = $dkim->selector;

  $dkim->selector('alpha');

signatures()

  my @signatures = $dkim->signatures;

Returns all generated signatures, as a list.

as_string()

  my $pre_headers = $signer->as_string();

The headers are separated by \015\012 (SMTP line separator) including a trailing separator, so can be directly injected in front of the raw message.

as_strings()

  my @pre_headers = $signer->as_string();

The headers are returned as a list so you can add whatever line ending your local MTA prefers.