React Native Requires Chilkat v11.0.0+

POP3 Read S/MIME Encrypted Email

Read S/MIME encrypted email. React Native

import { Email, EmailBundle, MailMan } from '@chilkat/react-native'

async function chilkatExample() {
  // This example assumes the Chilkat API to have been previously unlocked.
  // See Global Unlock Sample for sample code.

  // The mailman object is used for receiving (POP3) 
  // and sending (SMTP) email.
  const mailman = new MailMan();

  // Set the POP3 server's hostname
  mailman.mailHost = 'pop.example.com';

  // Set the POP3 login/password.
  mailman.popUsername = 'myLogin';
  mailman.popPassword = 'myPassword';

  // If running on Microsoft Windows, the Chilkat mailman
  // will automatically search the registry-based certificate stores
  // for matching certificates and private keys required for
  // decryption.  However, on Linux, MAX OS X, and other
  // operating systems, no such thing exists.  Therefore, you'll 
  // need to specify one or more PFX (.p12 / .pfx) files as
  // sources for locating the certs required for decyrption.
  try {
    mailman.addPfxSourceFile('/pfxFiles/certs_and_keys_1.pfx', 'pfxPassword1');
  } catch {
    console.log(mailman.lastErrorText);
    return;
  }

  try {
    mailman.addPfxSourceFile('/pfxFiles/certs_and_keys_2.pfx', 'pfxPassword2');
  } catch {
    console.log(mailman.lastErrorText);
    return;
  }

  // ...
  // Note: On MS Windows, it is not required to provide PFX sources
  // if the needed certs and private keys are already installed
  // on the system (in the registry-based certificate stores).

  // Copy the all email from the user's POP3 mailbox 
  // into a bundle object.  The email remains on the server.
  const bundle = new EmailBundle();
  const keepOnServer = true;
  const headersOnly = false;
  // Irrelevent because we are NOT downloading headers-only
  const numBodyLines = 0;
  try {
    await mailman.fetchAllAsync(keepOnServer, headersOnly, numBodyLines, bundle);
  } catch {
    console.log(mailman.lastErrorText);
    return;
  }

  // S/MIME security envelopes are automatically "unwrapped" 
  // when a message is retrieved from the server. Signed emails are automatically verified, and 
  // encrypted emails are automatically decrypted, restoring the email to the original state before 
  // signing and/or encrypting. Information about the signing and encrypting certificates can be 
  // retrieved from the Email object (methods: GetSignedByCert, GetEncryptedByCert; 
  // properties: SignedBy, EncryptedBy, SignaturesValid, Decrypted, ReceivedSigned, 
  // ReceivedEncrypted).

  // Loop over the bundle
  const email = new Email();
  let i = 0;
  while (i < bundle.messageCount) {

    bundle.emailAt(i, email);

    console.log(email.from);
    console.log(email.subject);

    // At this point, if the email was signed and/or encrypted, it is already "unwrapped", i.e.
    // the email is already decrypted and in a state as if it were never signed or encrypted.
    // You may check to see if the email was received encrypted or signed, and if so,
    // whether it was successfully unwrapped and who signed or encrypted it:
    if (email.receivedEncrypted) {

      console.log('This email was encrypted when received.');
      if (email.decrypted) {
        console.log('This email was successfully decrypted.  It was encrypted by:');
        console.log(email.encryptedBy);
      } else {
        console.log('This email was not decrypted.');
      }
    }

    if (email.receivedSigned) {

      console.log('This email was signed when received.');
      if (email.signaturesValid) {
        console.log('The signature was verified.  It was signed by:');
        console.log(email.signedBy);
      } else {
        console.log('The signature verification failed.');
      }
    }

    // The email's body, HTML body, attachments, etc.
    // are decrypted and available just like any non-encrypted email.

    console.log('--');

    i++;
  }
}