Email Account form –
|
|
Use the Email Account form to configure email accounts that manage outgoing (Sender) and incoming (Receiver) email. You specify email addresses to send from and to reply to, SMTP host information, User IDs, passwords, and more. When you configure email for your application, you reference the Email Account name in the email listener's Account Information field so the listener can get the information it needs to route incoming and outgoing messages.
Optionally, click Select Email Provider to select from a list of commonly used email providers, such as Google Gmail and Yahoo mail. When you make a selection and click OK, some form fields, such as Host, Port, and Protocol, are populated automatically. You can edit any of the automatically-populated fields. Be aware, however, that the edited information on the form may no longer accurately represent the provider.
Note: Connection settings vary by email service provider and these settings should be obtained from the service providers.
Complete the fields in this section to configure outgoing mail.
Complete the fields in this section if your application will be sending digitally signed email.
After you save the Email Account form, click to confirm that Pega 7 can connect to the SMTP host identified on this tab.
Complete the fields in this section to configure inbound mail.
IMAP: 143 (Unsecured) or 993 (Secured with SSL)
POP3: 110 (Unsecured) or 995 (Secured with SSL)
IMAP
or POP3
. IMAP has a larger feature set than POP3, and is usually the preferred protocol for that reason.After you save the Email Account form, click Test Connectivity to confirm that Pega can connect to the host identified on this tab. Review details that are displayed after the test is completed.
Use this section to override the default settings used by the email receiver. Specify the key and value for valid JavaMail API IMAP and POP3 protocol provider properties as defined in the Java packages com.sun.mail.imap
and com.sun.mail.pop3
, respectively.
Note: Customizing the email receiver with these settings must be done with care and may result in an unproven, unsupported configuration
For example, it may be necessary to disable plain authentication for compatibility with some Microsoft Exchange servers:
Key - mail.imaps.auth.plain.disable
Value - true
About Email Account data instances