Re: imapproxy with gmail

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



=>
> Please, post plain text messages only on this list.  Please read the
> posting guidelines if you have doubts.
>
> On Thu, Dec 9, 2010 at 12:41 PM, Jumping Mouse <kafriki@xxxxxxxxxxx> wrote:
> >
> > > Subject: Re: imapproxy with gmail
> > >
> > > On Thu, Dec 9, 2010 at 10:14 AM, Jumping Mouse <kafriki@xxxxxxxxxxx> wrote:
> > > >>
> > > >> On Wed, Dec 8, 2010 at 3:30 PM, Jumping Mouse <kafriki@xxxxxxxxxxx> wrote:
> > > >> > Hi everyone,
> > > >> > I am able to get squirrelmail to work with gmail without imapproxy.   I
> > > >> > have
> > > >> > enabled imapproxy on my machine and set squirremail to connect to
> > > >> > localhost
> > > >> > port 144
> > > >> > I get the following error in squirrelmail:
> > > >> > Error connecting to IMAP server: 127.0.0.1.
> > > >> > 111 : Connection refused
> > > >> > can anyone help with this.. I am having a hard time finding any
> > > >> > documentation.
> > > >>
> > > >> So IMAP Proxy didn't start up. For questions about IMAP Proxy, please
> > > >> use the squirrelmail-imapproxy mailing list. But, since you already
> > > >> started an off-topic thread here... Read your log files for hints.
> > > >> The biggest hint will be to read the IMAP Proxy README.ssl file --
> > > >> compare it to your configuration settings and/or download and use the
> > > >> latest snapshot of IMAP Proxy version 1.2.8 from the downloads page.
> > > >> It will give you some more helpful messages when you try to start it
> > > >> with these settings.
> > > >>
> > > >> > Here is my imapproxy.conf file:
> > > >> > ## imapproxy.conf
> > > >> > ##
> > > >> > ## This is the global configuration file for imapproxy.
> > > >> > ## Lines beginning with a '#' sign are treated as comments and will be
> > > >> > ## ignored.  Each line to be processed must be a space delimited
> > > >> > ## keyword/value pair.
> > > >> > ##
> > > >> > #
> > > >> > ## server_hostname
> > > >> > ##
> > > >> > ## This setting controls which imap server we proxy our connections to.
> > > >> > #
> > > >> > server_hostname imap.gmail.com
> > > >> >
> > > >> > #
> > > >> > ## cache_size
> > > >> > ##
> > > >> > ## This setting determines how many in-core imap connection structures
> > > >> > ## will be allocated.  As such, it determines not only how many cached
> > > >> > ## connections will be allowed, but really the total number of
> > > >> > simultaneous
> > > >> > ## connections, cached and active.
> > > >> > #
> > > >> > cache_size 3072
> > > >> >
> > > >> > #
> > > >> > ## listen_port
> > > >> > ##
> > > >> > ## This setting specifies which port the proxy server will bind to and
> > > >> > ## accept incoming connections from.
> > > >> > #
> > > >> > listen_port 144
> > > >> > #
> > > >> > ## listen_address
> > > >> > ##
> > > >> > ## This setting specifies which address the proxy server will bind to
> > > >> > and
> > > >> > ## accept incoming connections to.  If undefined, bind to all.
> > > >> > ## Must be a dotted decimal IP address.
> > > >> > #
> > > >> > listen_address
> > > >> > #
> > > >> > ## server_port
> > > >> > ##
> > > >> > ## This setting specifies the port that server_hostname is listening on.
> > > >> > ## This is the tcp port that we proxy inbound connections to.
> > > >> > #
> > > >> > server_port 993
> > > >>
> > > >> IMAP Proxy only does STARTTLS from a normal IMAP connection. Please
> > > >> read its documentation for more information.
> > > >
> > > >
> > > > Thanks Paul,  I read the documentation and it looks like imapproxy does not
> > > > support   port 993 SSL connections (IMAPS)  only  STARTTLS on port 143.   So
> > > > that would mean it will not work with GMAIL IMAP.
> > >
> > > No, that's incorrect. For proof, telnet to imap.gmail.com port 143
> > > and type "A CAPABILITY". IMAP Proxy *does* work with Gmail.
> > >
> >
> > Paul  when I telnet imap.gmail.com 143  I do not get any connection:
> > #telnet imap.gmail.com 143
> > Connecting To imap.gmail.com...Could not open connection to the host, on port 143: Connect failed
> > I have tried this from two locations behind different firewalls and no luck on both.  I tested another
> > imap server and I was able to connect.  This is what I based my conclusion that gmail Imap does
> > not support STARTTLS.
>
> That is faulty logic. "I cannot connect to a service" does not equate
> to "some feature of that service is not supported."

agreed. 


>
> >From my location:
>
> $ telnet imap.gmail.com 143
> Trying 74.125.127.109...
> Connected to imap.gmail.com (74.125.127.109).
> Escape character is '^]'.
> * OK Gimap ready for requests from ww.xx.yy.zz n14if21260b3fal.5
> A CAPABILITY
> * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA XLIST CHILDREN
> XYZZY SASL-IR AUTH=XOAUTH STARTTLS
> A OK Thats all she wrote! n14if21260b3fal.5
>
> There it is. As to whether or not their STARTTLS feature actually
> works, that's anyone's guess, since Google is famously unresponsive to
> help requests and provides little to no documentation of such
> services.
>

Sorry about the formated posting.       Where are you located that you can connect to imap.gmail.com port 143??  Here in my location in the US I cannot connect,  I have tried in three different locations via three different isp's  and no luck.
------------------------------------------------------------------------------
-----
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users

[Index of Archives]     [Video For Linux]     [Yosemite News]     [Yosemite Photos]     [gtk]     [KDE]     [Cyrus SASL]     [Gimp on Windows]     [Steve's Art]     [Webcams]

  Powered by Linux