IOError: closed stream (cannot recover)

[Red]

So, I just tried out larch.

It connected to both servers, fetched the message headers from the old
server, which took about a minute, that spit out the error in the
subject with each copy:

[Sep 08 14:04:25] [info] copying message: stefan...@haidlmair.at -
Re: [wpkg-users] How do I configure WPKG so it automatically updates?
[Sep 08 14:04:25] [error] IOError: closed stream (cannot recover)
[Sep 08 14:04:25] [info] copying message: bugzill...@wpkg.org -
[wpkg-users] [Bug 169] New: Network info in logfile
[Sep 08 14:04:25] [error] IOError: closed stream (cannot recover)

The destination server is MailEnable.

On my source server, it also butchered the read/unread status of all
the messages... they all show as read, now, which is clearly not
desirable.

thanks.

[Ryan Grove]

On Tue, Sep 8, 2009 at 11:13 AM, Red<dw...@cornell.edu> wrote:
> So, I just tried out larch.
>
> It connected to both servers, fetched the message headers from the old
> server, which took about a minute, that spit out the error in the
> subject with each copy:
>
> [Sep 08 14:04:25] [info] copying message: stefan...@haidlmair.at -
> Re: [wpkg-users] How do I configure WPKG so it automatically updates?
> [Sep 08 14:04:25] [error] IOError: closed stream (cannot recover)

This may indicate that either the source or destination server
terminated the connection abruptly when Larch tried to transfer the
message.

If you run Larch with the "-V insane" command line option, it will
output the full IMAP protocol log, which would help me determine where
the error occurred (this log will include usernames and passwords
though, so be sure to remove those before sending).

> [Sep 08 14:04:25] [info] copying message: bugzill...@wpkg.org -
> [wpkg-users] [Bug 169] New: Network info in logfile
> [Sep 08 14:04:25] [error] IOError: closed stream (cannot recover)
>
> The destination server is MailEnable.
>
> On my source server, it also butchered the read/unread status of all
> the messages... they all show as read, now, which is clearly not
> desirable.

I haven't tested Larch with MailEnable, so it's possible there are
issues there. What software is the source server running?

Larch operates in read-only mode on the source server and only peeks
at the message body (by requesting BODY.PEEK[]) when downloading
messages. If the source server implements IMAP properly, it should
never set a message's \Seen flag when a client requests BODY.PEEK[].
It may remove the \Recent flag, but a properly-implemented client
should use the \Seen flag to indicate read/unread status, not \Recent.

- Ryan