Add a PFX Source to MailMan from BinData

See more POP3 Examples

Demonstrates the Chilkat MailMan.AddPfxSourceBd method, which adds a PFX/PKCS#12 certificate store to the MailMan object's internal list of sources used for locating certificates and private keys. The first argument is a BinData containing the PFX bytes and the second is the PFX password. This example loads a PFX into a BinData, registers it, and fetches a message Chilkat can decrypt.

// Demonstrates the MailMan.AddPfxSourceBd method, which adds a PFX/PKCS#12 certificate store
// to the MailMan object's internal list of sources used for locating certificates and
// private keys.  The 1st argument is a BinData containing the PFX bytes and the 2nd is the
// PFX password.

let mailman = chilkat::MailMan::new();

// Configure the POP3 server connection.
mailman.set_mail_host("pop.example.com");
mailman.set_mail_port(995);
mailman.set_pop_ssl(true);
mailman.set_pop_username("user@example.com");
mailman.set_pop_password("myPassword");

// Load the PFX bytes into a BinData (they could come from a file, database, or secrets store).
let bd_pfx = chilkat::BinData::new();
if bd_pfx.load_file("qa_data/certs/decryption.pfx").is_err() {
    println!("{}", bd_pfx.last_error_text());
    return;
}

// Add the PFX as a source of certificates and private keys.
if mailman.add_pfx_source_bd(&bd_pfx, "pfx_password").is_err() {
    println!("{}", mailman.last_error_text());
    return;
}

// Fetch a message; if it is encrypted, Chilkat can decrypt it using the PFX source.
let email = chilkat::Email::new();
if mailman.fetch_one(false, 0, 1, &email).is_err() {
    println!("{}", mailman.last_error_text());
    return;
}

println!("Decrypted = {}", email.decrypted());

// Note: The path "qa_data/certs/decryption.pfx" is a relative local filesystem path,
// relative to the current working directory of the running application.

// Note: Explicitly connecting/authenticating is optional.  Chilkat MailMan automatically
// connects and authenticates -- using the property settings above -- whenever a server
// operation requires it.  Calling the explicit connect/authenticate methods can still be
// helpful to determine whether a failure occurs while connecting or while authenticating.