Trade without certificates

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

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 Trading pickup on the navigation graphic at the top of the page to open the Trading pickups 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. Make sure message signing and encryption for inbound messages from this partner are turned off. Do the following:
    1. On the community summary page, click Message validation on the navigation graphic at the top of the page.
    2. Click the Signing tab. If Reject messages that are not signed is selected, click Add an exception for a partner, select the email partner and click Add.
    3. Click the Encryption tab. If Reject messages that are not encrypted is selected, click Add an exception for a partner, select the email partner and click Add.
  10. Make sure message signing and encryption for outbound messages to this partner are turned off. Do the following:
    1. On the community summary page, click Collaboration settings on the navigation graphic at the top of the page.
    2. Click Default settings at the top left of the page titled “Configure community-specific collaboration settings.”
    3. Click the generic email tab.
    4. By default, all settings should be off for request receipts, encrypt messages and sign messages. If not, clear the options and click Save changes.

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’s e‑mail 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.

Related topics

Related Links