Question
DXC Technology
PH
Last activity: 13 Dec 2016 10:26 EST
Email Account - Receiver - Failed to connect to server
Hi,
I'm currently getting issues when I do a "Test Connectivity" for my Email Account - Receiver. I'm getting the error below.
2016-10-17 17:45:36,457 INFO [STDOUT] (Dispatcher-Thread-21) 2016-10-17 17:45:36,441 [XX.XXX.XX.XX-8930-12] [ Developer] [ OnBoarding:02.08] (ivity.Data_EmailAccount.Action) ERROR ntsydasd1218|XX.XX.XX.XX rachel_car - Data-EmailAccount.CAR-Impl-Work: MessagingException caught connecting to email server; javax.mail.MessagingException: No login methods supported!;
nested exception is:
com.sun.mail.iap.ProtocolException: No login methods supported!
javax.mail.MessagingException: No login methods supported!;
nested exception is:
com.sun.mail.iap.ProtocolException: No login methods supported!
at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:569)
at javax.mail.Service.connect(Service.java:288)
at com.pegarules.generated.activity.ra_action_pop3orimapconnectivity_c70455405b06947dad030ffcd2fe55c9.step5_circum0(ra_action_pop3orimapconnectivity_c70455405b06947dad030ffcd2fe55c9.java:793)
I've found an article but it's for Pega 7. Is there a solution for this in Pega 6.2 SP2?
Thanks, Rachel
Hi,
I'm currently getting issues when I do a "Test Connectivity" for my Email Account - Receiver. I'm getting the error below.
2016-10-17 17:45:36,457 INFO [STDOUT] (Dispatcher-Thread-21) 2016-10-17 17:45:36,441 [XX.XXX.XX.XX-8930-12] [ Developer] [ OnBoarding:02.08] (ivity.Data_EmailAccount.Action) ERROR ntsydasd1218|XX.XX.XX.XX rachel_car - Data-EmailAccount.CAR-Impl-Work: MessagingException caught connecting to email server; javax.mail.MessagingException: No login methods supported!;
nested exception is:
com.sun.mail.iap.ProtocolException: No login methods supported!
javax.mail.MessagingException: No login methods supported!;
nested exception is:
com.sun.mail.iap.ProtocolException: No login methods supported!
at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:569)
at javax.mail.Service.connect(Service.java:288)
at com.pegarules.generated.activity.ra_action_pop3orimapconnectivity_c70455405b06947dad030ffcd2fe55c9.step5_circum0(ra_action_pop3orimapconnectivity_c70455405b06947dad030ffcd2fe55c9.java:793)
I've found an article but it's for Pega 7. Is there a solution for this in Pega 6.2 SP2?
Thanks, Rachel
***Updated by Moderator: Lochan. Removed user added #helpme tag. Apologies for confusion, shouldn't have been an end-user option***
***Updated by Moderator: Marissa to remove proprietary information***
***26/10/2016: Updated by moderator: Lochan to add SR Details***
Accepted Solution
DXC Technology
PH
Hi Houlj,
We're using Microsoft Exchange server. I've now raised an SR (SR-B183) for this and it looks like there needs to be a fix done on Pega side. We did a test run of modifying POP3orIMAPConnectivity activity. After doing that change, doing a test connectivity on the email receiver connected successfully to the email server.
Pegasystems Inc.
GB
Are you trying to use exchange 2010 and TLS ?
What authentication are you trying to use?
The exception that you are receiving "No login methods supported!" is indicating that the email server has not been configured to allow PRPC application to send emails using the username / password that prpc is using
Has the username used when you ran the email server wizard been tested to see if it can send emails?
Pegasystems Inc.
US
"No login methods supported" means that the login methods (not the specific credentials) provided by the server did not intersect with those that Pega (Java Mail) was told to support for the connection.
There are multiple possible casues. Some that come to mind are:
- The client is not using SSL or STARTTLS but the server requires it. This happens often when the client is coming from outside the corporate network.
- The version of Java Mail in use by Pega is "old" and does not support the authentication method that the server requries.
- client's IP or domain is impacting the security policies on the server
- There is a load balancer that is causing requests from the client to go to a wrong or badly configured email relay/server
- The hosts file or DNS cache is causing the client to connect to the wrong relay/server
DXC Technology
PH
Hi islak-1,
I just copied over the email account data from one environment to another and did a test on the connectivity. It's working on our UAT but I'm getting errors in SIT.
Accepted Solution
DXC Technology
PH
Hi Houlj,
We're using Microsoft Exchange server. I've now raised an SR (SR-B183) for this and it looks like there needs to be a fix done on Pega side. We did a test run of modifying POP3orIMAPConnectivity activity. After doing that change, doing a test connectivity on the email receiver connected successfully to the email server.