From roman at rs-labs.com  Mon May  4 11:30:15 2009
From: roman at rs-labs.com (Roman Medina-Heigl Hernandez)
Date: Mon, 04 May 2009 17:30:15 +0200
Subject: [imapproxy-info] Imapproxy quitting when IMAP server is unavailable
Message-ID: <5002_1241451020_n44FUIUI029695_49FF0A07.3010503@rs-labs.com>

Hello,

I filed a Debian bug on imapproxy package some time ago:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517331

Basically, when starting imapproxy, it quits inmediately when IMAP server
is unavailable, so if you have a network outage just in the same moment
when you're trying to start imapproxy, it will refuse to start. IMHO, the
logical behaviour should be not to die but instead keep daemon in
background and retry connection to imap server later.

I'd like to know your opinion about this, whether or not this is a known
bug and finally if perhaps (luckily) the bug is already solved (in this
case, which imapproxy version? Any patch available for the stated problem?)

Cheers,
-Roman

From dave64 at andrew.cmu.edu  Mon May  4 11:32:48 2009
From: dave64 at andrew.cmu.edu (Dave McMurtrie)
Date: Mon, 04 May 2009 11:32:48 -0400
Subject: [imapproxy-info] Imapproxy quitting when IMAP server is
	unavailable
In-Reply-To: <5002_1241451020_n44FUIUI029695_49FF0A07.3010503@rs-labs.com>
References: <5002_1241451020_n44FUIUI029695_49FF0A07.3010503@rs-labs.com>
Message-ID: <49FF0AA0.2060505@andrew.cmu.edu>

Roman Medina-Heigl Hernandez wrote:
> Hello,
> 
> I filed a Debian bug on imapproxy package some time ago:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517331
> 
> Basically, when starting imapproxy, it quits inmediately when IMAP server
> is unavailable, so if you have a network outage just in the same moment
> when you're trying to start imapproxy, it will refuse to start. IMHO, the
> logical behaviour should be not to die but instead keep daemon in
> background and retry connection to imap server later.
> 
> I'd like to know your opinion about this, whether or not this is a known
> bug and finally if perhaps (luckily) the bug is already solved (in this
> case, which imapproxy version? Any patch available for the stated problem?)

That's been fixed since 1.2.4.  It will now try to connect to the imap 
server forever upon startup.

Thanks,

Dave

From roman at rs-labs.com  Tue May  5 03:37:45 2009
From: roman at rs-labs.com (Roman Medina-Heigl Hernandez)
Date: Tue, 05 May 2009 09:37:45 +0200
Subject: [imapproxy-info] Imapproxy quitting when IMAP server is
	unavailable
In-Reply-To: <49FF0AA0.2060505@andrew.cmu.edu>
References: <5002_1241451020_n44FUIUI029695_49FF0A07.3010503@rs-labs.com>
	<49FF0AA0.2060505@andrew.cmu.edu>
Message-ID: <5006_1241509067_n457bjwi015796_49FFECC9.6000100@rs-labs.com>

Dave McMurtrie escribi?:
> Roman Medina-Heigl Hernandez wrote:
>> Hello,
>>
>> I filed a Debian bug on imapproxy package some time ago:
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517331
>>
>> Basically, when starting imapproxy, it quits inmediately when IMAP server
>> is unavailable, so if you have a network outage just in the same moment
>> when you're trying to start imapproxy, it will refuse to start. IMHO, the
>> logical behaviour should be not to die but instead keep daemon in
>> background and retry connection to imap server later.
>>
>> I'd like to know your opinion about this, whether or not this is a known
>> bug and finally if perhaps (luckily) the bug is already solved (in this
>> case, which imapproxy version? Any patch available for the stated
>> problem?)
> 
> That's been fixed since 1.2.4.  It will now try to connect to the imap
> server forever upon startup.


Hello Dave,

I saw this in imapproxy's changelog (2003-10-09 entry):

	* main.c: Changes to allow configurable tcp keelalive support.
	  Added retry logic for the initial socket connection to the
	  real imap server (patch submitted by Gary Mills
	  <mills at cc.UManitoba.CA>).

But I'm suffering the problem in Debian 5.0 (Lenny), which comes with
imapproxy 1.2.6 (which it's supposed to be fixed). :-? Do you have any
similar reports?

Is the fix perhaps disabled by default or maybe I need to set up some
configuration option to enable/tune the retrying action?

I have keepalives disabled (Debian default):
send_tcp_keepalives no
Maybe the retry logic depends on this? (IMHO it shouldn't...).

Cheers,
-Roman


From mfisch at mfisch.com  Fri May 22 14:29:31 2009
From: mfisch at mfisch.com (Matthew Fisch)
Date: Fri, 22 May 2009 14:29:31 -0400
Subject: [imapproxy-info] imapproxy yahoo imap support
In-Reply-To: <F0F2C0AB-3CE2-4086-AC2F-72DE6619685F@mfisch.com>
References: <F0F2C0AB-3CE2-4086-AC2F-72DE6619685F@mfisch.com>
Message-ID: <0F950373-DAF2-4718-8BA7-1BF76FE27ACD@mfisch.com>

I was able to get on Yahoo!'s IMAP server by creating a hacked proxy  
out of datapipe.c.

const char id_str[] = "DATAPIPE ID (\"GUID\" \"1\")\r\n";
^^ I sent that after connect and then bit-bucketed the reply.

I don't know enough C to create an acceptable patch. Maybe someone  
else will feel inspired.

Yahoo! only accepts LOGIN and some weird yahoo-specific secure-cookie  
(need to use SOAP to get it I think). But their server listens on  
imap.mail.yahoo.com (143) and imap-ssl.mail.yahoo.com (993).

Cheers and thanks if you DO feel inspired.
-Matt

ps, I'm not a list member, you'll have to copy me on replies.