Configure E-Mail Connector
This is one of the basic connector which has to be configured for any client requirement and I found it tedious to remember all the configuration settings. Hence I wanted it to be kept in the internet.
Above is the configuration screen to be configured while creating an E-Mail connector.
Two points to be noted :
- Make sure you are connected to internet if you are configuring for gmail.
- We have to add jvm properties in JRE configurations also, please find the properties which are to be added as jvm properties.
-Dmail.pop3.socketFactory.class=javax.net.ssl.SSLSocketFactory
-Dmail.pop3.socketFactory.fallback=false
-Dmail.smtp.socketFactory.class=javax.net.ssl.SSLSocketFactory
-Dmail.smtp.socketFactory.fallback=false
I tried understanding what are these, I could just find out when we enable SSL while configuring the container we need to add those class files to the jvm then only it can detect.
As always : Correct me If I am wrong anywhere.
-------------------------------------------------------------------------------------------------------
I have tried with the above settings and What I found was a configuration error while starting the container. The error is shown below,
Connection to the mail server failed -' javax.mail.MessagingException: Connect failed; nested exception is: java.io.IOException: Unexpected response: * OK Gimap ready for requests from 115.119.152.140 jz7if19298575pbc.133 ' is not supported.com.eibus.applicationconnector.email.MailConnector.open(MailConnector.java:230)com.eibus.soap.Processor.open(Processor.java:755)com.eibus.soap.Processor.startProcessor(Processor.java:1050)com.eibus.soap.ProcessStreamsHandler.startProcessor(ProcessStreamsHandler.java:686)com.eibus.soap.ProcessStreamsHandler$StreamReader.run(ProcessStreamsHandler.java:353)
This error is resolved by making the property value of the property "mail.pop3.socketFactory.port" from 993 to 995, As I have seen that this is the default port where gmail will be listening to. These properties will be set by default when you check set SSL checkbox. Now I had to modify manually this value from 993 to 995. Restarted the container worked. I don't know why is this strange behaviour in two different environment.