Rudolf Sykora <[email protected]> wrote:
 |I am trying s-nail to read gmail mail via IMAP.
 |While being at work, it works. But when I leave
 |work to come back the next day, I get:
 |
 |? inc
 |IMAP: error:00000000:lib(0):func(0):reason(0)
 |IMAP write error: error:00000000:lib(0):func(0):reason(0)
 |IMAP write error: Bad file descriptor
 |IMAP connection closed
 |IMAP connection closed
 |IMAP connection closed
 |...
 |
 |I do have a line
 |
 |set imap-keepalive=240
 |
 |in my .mailrc. Still it happens.

Seriously?

 |Thanks for comments!

Maybe it's an administrator who drives OpenBSD and doesn't want
people wasting resources, cutting your connection after some time
/ of only no-op communication?  I don't know.

But above you see one reason why i'll throw away all involved
layers after v14.9.  I've used this IMAP code, too, and it is
"stable" except for what is mentioned in BUGS.
But unfortunately it is very dumb and has been implemented on the
same code that works with local file-based messages, which is why
you'll get that many error messages, just as many as messages
exist in the box, as surely has been shortened above.

So i'll _try_ to reinstantiate the IMAP code for v14.9 since
people seem to use it, but i cannot recommend using it except for
"fetchmail"-like operation.  Note that Gunnar Ritter i think had
in mind to overcome those problems by using the IMAP-cache and
doing successive `disconnect' and `connect'.  Like this you can
somehow "deal" with this, but please see BUGS for restrictions!

Shall IMAP ever come back after v15 things as above won't happen.
You'd see only one error message, then, at least, or you get
a transparent automatic reconnection.  But that is far future.
Ciao,

--steffen

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
__________________________________
[email protected]

Reply via email to