yeah thats prolly the cause. Most companies not allow to connect to
random ports. So maybe test it again when you are at home ..

Bye,
Norman

2009/9/1 smiletolead <kumar.gane...@gmail.com>:
>
> I am behind a proxy actually. Is it because of that?
>
> On Sep 1, 2:24 pm, Norman Maurer <nor...@apache.org> wrote:
>> Ok this sounds like a firewall in front. telnet to port 993 works fine here..
>>
>> Bye,
>> Norman
>>
>> 2009/9/1 smiletolead <kumar.gane...@gmail.com>:
>>
>>
>>
>> > Telnetting is giving me the following result:
>>
>> > C:\>telnet imap.gmail.com 993
>> > Connecting To imap.gmail.com...Could not open connection to the host,
>> > on port 993: Connect failed
>>
>> > Thanks,
>> > Ganesh
>>
>> > On Sep 1, 2:11 pm, Norman Maurer <nor...@apache.org> wrote:
>> >> can you try to connect to it via telnet, just to see if there is a
>> >> firewall in front:
>>
>> >> telnet imap.gmail.com 993
>> >> telnet smtp.gmail.com 465
>>
>> >> Thx,
>> >> Norman
>>
>> >> 2009/9/1 smiletolead <kumar.gane...@gmail.com>:
>>
>> >> > Here is the config.properties:
>>
>> >> > # The IP or domainname of the IMAP server
>> >> > IMAPServerAddress=imap.gmail.com
>> >> > # The port of the IMAP server
>> >> > IMAPServerPort=993
>> >> > # Use SSL/TLS to connect to the IMAP server
>> >> > IMAPS=true
>> >> > # The IP or domainname of the SMTP server
>> >> > SMTPServerAddress=smtp.gmail.com
>> >> > # The port of the SMTP server
>> >> > SMTPServerPort=465
>> >> > # Use AUTH for SMTP
>> >> > SMTPAuth=true
>> >> > # Use SSL/TLS to connect to the SMTP server
>> >> > SMTPS=true
>>
>> >> > It is copied from the reply given by you only
>>
>> >> > Ganesh
>>
>> >> > On Sep 1, 2:01 pm, Norman Maurer <nor...@apache.org> wrote:
>> >> >> Can you post your config.properties file.
>>
>> >> >> Connection timeout sounds like a firewall,wrong ip or wrong port.
>>
>> >> >> Thx,
>> >> >> Norman
>>
>> >> >> 2009/9/1 smiletolead <kumar.gane...@gmail.com>:
>>
>> >> >> > Hi Norman,
>> >> >> >  I downloaded the latest code. When connecting to gmail, I get the
>> >> >> > following error:
>>
>> >> >> > 268627 [btpool0-2] ERROR HupaLogger  - Unable to authenticate user
>> >> >> > kumar.gane...@gmail.com
>> >> >> > javax.mail.MessagingException: Connection timed out: connect;
>> >> >> >  nested exception is:
>> >> >> >        java.net.ConnectException: Connection timed out: connect
>> >> >> >        at 
>> >> >> > com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:611)
>> >> >> >        at javax.mail.Service.connect(Service.java:291)
>> >> >> >        at org.apache.hupa.server.InMemoryIMAPStoreCache.get
>> >> >> > (InMemoryIMAPStoreCache.java:87)
>> >> >> >        at org.apache.hupa.server.InMemoryIMAPStoreCache.get
>> >> >> > (InMemoryIMAPStoreCache.java:69)
>> >> >> >        at org.apache.hupa.server.handler.LoginUserHandler.execute
>> >> >> > (LoginUserHandler.java:71)
>> >> >> >        at org.apache.hupa.server.handler.LoginUserHandler.execute
>> >> >> > (LoginUserHandler.java:1)
>> >> >> >        at 
>> >> >> > net.customware.gwt.dispatch.server.DefaultDispatch.doExecute
>> >> >> > (DefaultDispatch.java:78)
>> >> >> >        at net.customware.gwt.dispatch.server.DefaultDispatch.execute
>> >> >> > (DefaultDispatch.java:68)
>> >> >> >        at
>> >> >> > net.customware.gwt.dispatch.server.service.DispatchServiceServlet.execute
>> >> >> > (DispatchServiceServlet.java:24)
>> >> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >> >> >        at sun.reflect.NativeMethodAccessorImpl.invoke
>> >> >> > (NativeMethodAccessorImpl.java:39)
>> >> >> >        at sun.reflect.DelegatingMethodAccessorImpl.invoke
>> >> >> > (DelegatingMethodAccessorImpl.java:25)
>> >> >> >        at java.lang.reflect.Method.invoke(Method.java:597)
>> >> >> >        at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse
>> >> >> > (RPC.java:527)
>> >> >> >        at 
>> >> >> > com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall
>> >> >> > (RemoteServiceServlet.java:166)
>> >> >> >        at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost
>> >> >> > (RemoteServiceServlet.java:86)
>> >> >> >        at 
>> >> >> > javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
>> >> >> >        at 
>> >> >> > javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>> >> >> >        at com.google.inject.servlet.ServletDefinition.doService
>> >> >> > (ServletDefinition.java:216)
>> >> >> >        at com.google.inject.servlet.ServletDefinition.service
>> >> >> > (ServletDefinition.java:141)
>> >> >> >        at com.google.inject.servlet.ManagedServletPipeline.service
>> >> >> > (ManagedServletPipeline.java:93)
>> >> >> >        at com.google.inject.servlet.FilterChainInvocation.doFilter
>> >> >> > (FilterChainInvocation.java:63)
>> >> >> >        at com.google.inject.servlet.ManagedFilterPipeline.dispatch
>> >> >> > (ManagedFilterPipeline.java:122)
>> >> >> >        at 
>> >> >> > com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:
>> >> >> > 110)
>> >> >> >        at 
>> >> >> > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
>> >> >> > (ServletHandler.java:1088)
>> >> >> >        at org.mortbay.jetty.servlet.ServletHandler.handle
>> >> >> > (ServletHandler.java:360)
>> >> >> >        at org.mortbay.jetty.security.SecurityHandler.handle
>> >> >> > (SecurityHandler.java:216)
>> >> >> >        at org.mortbay.jetty.servlet.SessionHandler.handle
>> >> >> > (SessionHandler.java:181)
>> >> >> >        at org.mortbay.jetty.handler.ContextHandler.handle
>> >> >> > (ContextHandler.java:729)
>> >> >> >        at 
>> >> >> > org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:
>> >> >> > 405)
>> >> >> >        at org.mortbay.jetty.handler.HandlerWrapper.handle
>> >> >> > (HandlerWrapper.java:152)
>> >> >> >        at org.mortbay.jetty.handler.RequestLogHandler.handle
>> >> >> > (RequestLogHandler.java:49)
>> >> >> >        at org.mortbay.jetty.handler.HandlerWrapper.handle
>> >> >> > (HandlerWrapper.java:152)
>> >> >> >        at org.mortbay.jetty.Server.handle(Server.java:324)
>> >> >> >        at 
>> >> >> > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:
>> >> >> > 505)
>> >> >> >        at org.mortbay.jetty.HttpConnection$RequestHandler.content
>> >> >> > (HttpConnection.java:843)
>> >> >> >        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:647)
>> >> >> >        at 
>> >> >> > org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
>> >> >> >        at 
>> >> >> > org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
>> >> >> >        at org.mortbay.io.nio.SelectChannelEndPoint.run
>> >> >> > (SelectChannelEndPoint.java:395)
>> >> >> >        at org.mortbay.thread.QueuedThreadPool$PoolThread.run
>> >> >> > (QueuedThreadPool.java:488)
>> >> >> > Caused by: java.net.ConnectException: Connection timed out: connect
>> >> >> >        at java.net.PlainSocketImpl.socketConnect(Native Method)
>> >> >> >        at 
>> >> >> > java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>> >> >> >        at 
>> >> >> > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:
>> >> >> > 195)
>> >> >> >        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>> >> >> >        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>> >> >> >        at java.net.Socket.connect(Socket.java:519)
>> >> >> >        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect
>> >> >> > (SSLSocketImpl.java:550)
>> >> >> >        at com.sun.net.ssl.internal.ssl.BaseSSLSocketImpl.connect
>> >> >> > (BaseSSLSocketImpl.java:141)
>> >> >> >        at 
>> >> >> > com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:
>> >> >> > 267)
>> >> >> >        at 
>> >> >> > com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:227)
>> >> >> >        at com.sun.mail.iap.Protocol.<init>(Protocol.java:107)
>> >> >> >        at 
>> >> >> > com.sun.mail.imap.protocol.IMAPProtocol.<init>(IMAPProtocol.java:
>> >> >> > 103)
>> >> >> >        at 
>> >> >> > com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:578)
>> >> >> >        ... 40 more
>>
>> >> >> > On Sep 1, 11:44 am, Norman Maurer <nor...@apache.org> wrote:
>> >> >> >> Hi all,
>>
>> >> >> >> Hupa supports SSL since yesterday morning ;)  I just tested Hupa 
>> >> >> >> with
>> >> >> >> gmail and it worked.
>> >> >> >> So here are the steps you need to take:
>> >> >> >> * Checkout latest trunk of Hupa 
>> >> >> >> (https://svn.apache.org/repos/asf/labs/hupa/)
>> >> >> >> * Change the config.properties file to contain this:
>>
>> >> >> >> # The IP or domainname of the IMAP server
>> >> >> >> IMAPServerAddress=imap.gmail.com
>> >> >> >> # The port of the IMAP server
>> >> >> >> IMAPServerPort=993
>> >> >> >> # Use SSL/TLS to connect to the IMAP server
>> >> >> >> IMAPS=true
>>
>> >> >> >> # The IP or domainname of the SMTP server
>> >> >> >> SMTPServerAddress=smtp.gmail.com
>> >> >> >> # The port of the SMTP server
>> >> >> >> SMTPServerPort=465
>> >> >> >> # Use AUTH for SMTP
>> >> >> >> SMTPAuth=true
>> >> >> >> # Use SSL/TLS to connect to the SMTP server
>> >> >> >> SMTPS=true
>>
>> >> >> >> That's it.
>> >> >> >> Feedback is welcome :)
>>
>> >> >> >> Bye,
>> >> >> >> Norman
>>
>> >> >> >> 2009/8/31 Manuel Carrasco Moñino <manuel.carrasc...@gmail.com>:
>>
>> >> >> >> > Last time I played with hupa i didn't support ssl, however gmail 
>> >> >> >> > needs ssl
>> >> >> >> > for imap and tls for smtp.
>> >> >> >> > So I think it is not possible to use it with gmail.
>>
>> >> >> >> > Manolo Carrasco
>>
>> >> >> >> > On Mon, Aug 31, 2009 at 3:04 PM, Norman Maurer 
>> >> >> >> > <nor...@apache.org> wrote:
>>
>> >> >> >> >> well it should work with gmail.. Did you check if you have 
>> >> >> >> >> enabled
>> >> >> >> >> imap support in gmail:
>> >> >> >> >>http://mail.google.com/support/bin/answer.py?answer=77695
>>
>> >> >> >> >> And how you run Hupa ? In tomcat/Jetty/Jboss/Hosted Mode ?
>>
>> >> >> >> >> Bye,
>> >> >> >> >> Norman
>>
>> >> >> >> >> 2009/8/31 smiletolead <kumar.gane...@gmail.com>:
>>
>> >> >> >> >> > Hi Norman,
>> >> >> >> >> >  Is it like I have to set up the mail server in my own machine?
>>
>> >> >> >> >> > --Ganesh
>>
>> >> >> >> >> > On Aug 30, 12:52 pm, Norman Maurer <nor...@apache.org> wrote:
>> >> >> >> >> >> Hi,
>>
>> >> >> >> >> >> anything in the server logs ? I neved tested it with 
>> >> >> >> >> >> googlemail yet,
>> >> >> >> >> >> Im tested it against dovecot and courier-imap.
>>
>> >> >> >> >> >> Any feedback is welcome:)
>>
>> >> >> >> >> >> Bye,
>> >> >> >> >> >> Norman
>>
>> >> >> >> >> >> 2009/8/30 smiletolead <kumar.gane...@gmail.com>:
>>
>> >> >> >> >> >> > Hi
>>
>> ...
>>
>> read more »
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to