Question
PEG
SG
Last activity: 18 Jul 2017 10:44 EDT
Gmail Listener Configuration on 718
Hi,
The gmail listener configuration doesn't seems to work on Pega 718. We have the same gmail account working on version 717 but not on 718. Yahoo seems to be working fine on 718. Has anybody encountered this issue before?
Regads,
Sumit
***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
I just quickly tried to start a listener using a Gmail account and POP3 and it started up without issue.
Are you having a problem connecting or is the issue related to processing the incoming emails?
Are you testing with POP3 or IMAP?
Do you see an error when testing the connectivity for the Receiver on the Email Account you're using?
If you do see errors, could you please provide them?
PEG
SG
We had problems setting up a gmail account itself. We switched to yahoo and seems to be working fine. But gmail still issues connecting.
Inline is the setting that we are using for gmail. We tried changing the port from 587 to 465 but still the same error persists
Are the credentials being used are correct? Can you try using SMTP tester and confirm if you get the same exception: https://smtptest.codeplex.com/
Updated: 30 Jun 2015 14:44 EDT
I performed some testing on both a 717 and 718 instance and am not seeing different behavior. Using port 587 and leaving "Use SSL" or "Use SMTPS" unchecked, the test connectivity button is successful in both versions. If I use port 465 instead, it fails in both versions with this error:
Status
Fail:Configuration
Message
The connection to the outbound email server timed out. The server may be unavailable, or the connection configuration may be incorrect.
Verify username, password, and SSL options.
The only way I was able to produce the error you mention is by using the wrong username and or password. I would try re-entering the password on this Email Account carefully to see if that is the issue.