Posted: April 4, 2016
Last activity: May 19, 2016
Last activity: 19 May 2016 4:26 EDT
This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.
What version of Pega are you using?
Did this ever work?
Do you see this whenever you try to send an email?
Is there a full stack of the exception in the log? If so, can you provide it?
I am using 7.1.8 version and I tried this first time. Actually I created Email account,there sender and receiver connectivity was successful.After creating the case,in attachments I clicked on correspondence and I am getting the above mentioned error.
Is there a corresponding error in the PegaRULES log file? If so, can you provide it?
You can also update the following logger to debug level logging and this may provide further details in the log:
I recently edited a PDN article, which had the same error message. Maybe this article might help you. I've pasted the link below. However, this article was written for an issue in PRPC 6.2 SP2.
In your email account change the port number from 25 to 587,this might solve your issue.
Further to Prathap's suggestion: since you are using Gmail here: see this link also (which also list the 587 Port Number, or the alternative 465):
You will also need to enable 'starttls' (I believe this is labelled 'Use SSL' in the PRPC Email Account Rule form).
Additionally (as per other suggestions here): if this still doesn't work : you probably should aim to get a Java Stack Trace (and possibly even SMTP debug) information in order to troubleshoot further.
You should have a 'test connection' button on your Email Account Form in the PRPC Designer Studio - if it is failing to connect - check the PegaRules.log for errors.
You can also enable DEBUG logging for the PRPC 'SendEmail' function (in the 'Default' Library) - use SMA (AKA 'prsysmgmt') to enable DEBUG for the library functions. (From memory: I believe you have to enable DEBUG at the library level rather than at the level of a single function, but I could be wrong).
Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.