Notify Email Configuration for pega Cloud
Problem:
We need to send email notifications from the our Pega Cloud application to premise email addresses.
This is NOT sending email marketing offers to end customers. All emails are sent to “Notify Parties” that have our xxx.com email addresses.
The application in Pega Cloud is based on standard Pega 7.3.1 rules and the email notifications are standard notifications from various Pega7.3.1 processes to notify individuals that jobs have run successfully or not, distribute reports, etc.
The assumptions is that to send an email from Pega Cloud the email will be sent from the application to an email server using SMTP.
Our understanding is that in this context, the application represents the email “client” and the requirement is to integrate that “client” to the email server (our premise email server - which appears to be Microsoft Exchange.)
Our project team is looking for a check list of what needs to be done by Pega Cloud and by the customer.
This would include:
- From a Pega Cloud perspective, what needs to be done is open appropriate ports so the SMTP message is sent from Pega Cloud.
- From a customer perspective, what needs to be done to integrate their mail server to the “Application Client” (ports, protocols and email server configuration.)
- From a network perspective, what are the firewall settings and whitelisting that needs to be accommodated.
Pegasystems Inc.
US
Hi,
There is no such defined check list available.
Please check below steps:
1) Assign Static Ip's to Pegacloud App instances, from where the Mails will be triggered --> You need to check with Pegacloud on this.
2) Whitelist all static Ip's over mail server at Customer end
3) Test the connectivity from Pegacloud servers
4) Create a Mail account in PRPC (Designer Studio > Integration > Email > Email Wizard)
Pegasystems Inc.
PL
Hi,
So from Cloud Perspective, there is nothing to do on Pega side. Please keep in mind that for smtp protocol, please do not use port 25. Amazon EC2 throttles traffic on port 25 of all EC2 instances by default. Instead of this please use e.g. port 587 which is standard as for now and Microsoft using that port too.
From the network perspective on the mail server side, please allow inbound access for the entire VPC CIDR. If you do not know what is your VPC CIDR please contact Cloud Support. We are not operating on static IP's
If you will have any other questions please post message.
Thank you
Jakub
Pegasystems Inc.
DE
To amend Jakub's answer: if you are using Microsoft's Office365 product for your email environment, you may stuck with port 25. As long as you are using smtp.office365.com as your endpoint, everything works fine in that case, from Cloud/EC2 point of view.
But if you use another endpoint ("MX Record" in Microsoft's language), that throttling mentioned by Jakub will hit you.
In that case you can issue a Support Request to Pega Support and ask to remove/disable that Port-25-Throttling for your specific endpoint.
That throttling manifests in failed connections to the SMTP MTA after a handful of successfully sent emails; after a few minutes, again a very small number of emails can be sent before the connection will fail again. So if you do not sent more than three to four emails within a five to ten minute period, everything appears to be fine. Only with higher volumes, the throttling will jump in.
Pegasystems Inc.
US
Would it be possible to provide specific data points to the throttling or is there a specific document that has the throttling information?
What are the specific throttling limits? Is the throttling by bandwidth (bytes per second), number of messages, length of message, etc.
How many emails per minute will result in throttling?
What is the period of time that must expire before the throttling is reset?
Adaps
IN
Below link might help you.