Trade with certificates

An email client partner can send messages to a n Interchange partner using a certificate to encrypt attached documents. This method is for users who prefer to send or receive encrypted attachments to email messages.

Related topics

Configure Interchange

Use this procedure to configure Interchange to trade documents with a partner who uses an email client application.

This procedure presumes you already have a community. If not, see Add a community.

  1. In your community, add a generic email protocol delivery for receiving messages from a partner. You must use the generic email protocol and not AS1.
  2. The best practice is to use an external server (SMTP/POP) rather than an embedded SMTP server. Although it is possible to use an embedded server, the configuration is more complex.
  3. Make sure to properly set the “from” and “to” address on the POP pickup delivery exchange transport maintenance page. On the from and to address tabs, select Always parse for the address. Also select If the document is EDI, parse for the address, and If the document is XML, use XPaths to locate the address and the XPath.
  4. Give your email client partner the email address for the delivery added in step 1. Your partner uses this address to send messages to your community.
  5. On the community summary page, click Partner delivery on the navigation graphic at the top of the page to open the Partner deliveries page. Find the generic email transport and click to open the transport’s maintenance page. The email address is listed on the settings tab.
  6. Add a partner for your email client partner. Give it a meaningful name and routing ID.
  7. Add a generic email protocol delivery for sending messages to the partner via SMTP. You must use the generic email protocol and not AS1.
  8. In adding the transport, type the partner’s email address. This is the address your community uses to send messages to the partner.
  9. Export a community certificate and public key to a file and give it to the email client partner. The partner’s email client uses this certificate to encrypt messages sent to your community.
  10. A self-signed certificate or one issued by a certificate authority can be used.
  11. Export the certificate to a file with an extension of .cer or .p7b. Select the option “Include all certificates in the certification path if possible” when exporting (see Export a certificate to a file). Send the certificate file to your partner by a secure means. Do not send your private key to your partner.
  12. Export the certificate with an extension of .cer or .p7c. Then send the certificate file to your partner by a secure means. Do not send your private key to your partner.

Related topic

Configure email client partner

Use this procedure to configure an email client partner to trade documents with a partner who uses Interchange.

  1. In Outlook, add your Interchange partner as a contact. Use the partner’s email address for receiving documents as the contact email address.
  2. Set the mail client to compose messages in plain text. This makes sure the Interchange partner does not receive excess messages composed of MIME parts in addition to the document attachment.
  3. In Outlook, select Tools > Options. On the Mail Format tab, select Plain Text for the Compose in this message format field.
  4. Have your Interchange partner send you the certificate to use for encrypting message attachments.
  5. Import the partner’s certificate to the partner’s contact information in Outlook. On the certificates properties window, make sure to specify that Outlook is to explicitly trust the certificate.
  6. If upon importing the certificate, Outlook displays a message that the email address in the certificate is not found in the contact’s email list, click Yes to accept the certificate.

Related topics

Related Links