Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Email servers

Updated on April 6, 2022

Email server data instances represent a physical email server. Email listeners connect to the server represented by the data object and then route messages from the server to email service rules.

Note: This data class is deprecated as of PRPC Version 6.2 SP2. To create email servers, as well as email listeners and email service rules, see Configuring service processing for Service Email rules and Creating an email listener.

Fields and controls

The following table describes the available options on the Environment tab of the Email Server form.

FieldDescription
Host Name

Enter a Domain Name Server (DNS) name for the mail server, for example, EXCHDEV4.racme.com. Alternatively, identify an IP address of the mail server.

This field supports the Global Resource Settings syntax (= PageName.PropertyName ). The default property name for this field is pyEmailHostName. For more information, see Using the Global Resource Settings feature.

Port Number Identify a TCP/IP port for this email server, conventionally port 110 for POP3 protocol or port 143 for IMAP protocol. To receive messages using SSL, different port numbers typically apply.

This field supports the Global Resource Settings syntax (= PageName.PropertyName ). The default property name for this field is pyEmailPortNumber. For more information, see Using the Global Resource Settings feature.

Protocol Select whether email is to be received through the POP3 or IMAP mail protocol.
Use SSLSelect if email listeners that connect to the email server use the Secure Sockets Layer protocol, SSL, for authentication and for retrieving messages.
User ID Enter the user ID of the account that your system uses to connect to the email server.

This field supports the Global Resource Settings syntax (= PageName.PropertyName ). The default property name for this field is pyEmailUserID. For more information, see Using the Global Resource Settings feature.

Password Optional. If required, enter the password of the user account specified in the User ID field.

This field supports the Global Resource Settings syntax (= PageName.PropertyName ). The default property name for this field is pyEmailPassword. For more information, see Using the Global Resource Settings feature.

Send Email As Enter an email address to use as the default "from" party for reply messages to the email messages retrieved from this account. Note that a Send Email As value provided by the email listener overrides this value.

This field supports the Global Resource Settings syntax (= PageName.PropertyName ). The default property name for this field is pyReplyAsEmail. For more information, see Using the Global Resource Settings feature.

Forward Unprocessed Emails Select to forward any failed incoming email messages as an attachment to an administrator's email address. Scenarios that may cause an incoming message to fail include:
  • The incoming message size is larger than the value set in the Maximum Email Size (KB) field of the Email Listener data instance.
  • The incoming message cannot be decrypted.
Forwarding Email Address for Unprocessed Emails Enter the email address to which failed incoming email messages are forwarded.

This field supports the Global Resource Settings syntax (= PageName.PropertyName ). The default property name for this field is pyAdminEmail. For more information, see Using the Global Resource Settings feature.

Test Connectivity After you complete this tab and save the Email Server data instance, click to confirm that you can connect to the email server.

The system presents test results in a separate window, identifying the parameters used in the test, the steps attempted, and the outcome of each step.

This option does not retrieve email messages from the server.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us