Email endpoints enable users to invoke a service by sending
one or more documents (as email attachments) to a specified email
account. The email inbox acts as a collecting point for the attachments.
The service monitors the inbox and processes the attachments. The
results of the conversion are forwarded to the user defined in the
endpoint.
For an email endpoint, authorized users can invoke a process
by emailing files to the appropriate account. The results will be
returned to the submitting user (by default) or to the user defined
in the endpoint settings.
Before you configure an email endpoint, create a POP3 or IMAP
email account for use by the endpoint. Set up a separate account
for each type of conversion. For example, one account can be configured
to generate standard PDF documents from incoming file attachments,
and another account can be configured to generate secure PDF documents.
Important: Each email address must map to only one
email endpoint. You cannot configure multiple email endpoints to
a single email address, even if the additional email endpoints are
disabled.
All email endpoints are configured with an authorized user name
and password for the email inbox, which are required when invoking
the service. The email account is protected by the mail server system
on which it is configured.
If your users send documents with Western European language characters
in file and conversion path names, they must use an email application
that supports the required encoding types (Latin1 [ISO-8859-1],
Western European [Windows], or UTF-8). For more information, see
the Installing and Deploying LiveCycle document for your
application server.
Before you configure an email endpoint, configure the Email service.
(See Configure default email endpoint settings.) The Email service’s configuration parameters
have two purposes:
