Problem with syncing mail with attachments

[Nicolas Sebrecht]

On Sun, Feb 08, 2015 at 05:26:27PM -0500, Britt Anderson wrote:

> The downloading from remote to local works fine, and email without
> attachments still do what I want.
> 
> Appreciate any advice. -- Some of the info and debug files follows. I
> can post the entire debug output if advised. /Britt
> 
> 
> Here is the Offline Info output:
> 
> 
> OfflineIMAP 6.5.5
>   Licensed under the GNU GPL v2+ (v2 or any later version)
> Remote repository 'uwloo-remote': type 'IMAP'
> Host: connect.uwaterloo.ca Port: 993 SSL: True
> Establishing connection to connect.uwaterloo.ca:993

So, the IMAP server for OfflineIMAP is connect.uwaterloo.ca.

> Server welcome string: * OK The Microsoft Exchange IMAP4 service is ready.
> Server capabilities: ('IMAP4', 'IMAP4REV1', 'AUTH=NTLM', 'AUTH=GSSAPI', 'AUTH=PLAIN', 'UIDPLUS', 'CHILDREN', 'IDLE', 'NAMESPACE', 'LITERAL+')

<...>

> And here are some of the relevant lines of the end of debug file where the
> error messages appear and the tracing information is printed.
> 
> 2015-02-08 13:46:26 DEBUG: [imap]:   46:26.15 Account sync uwloo _get_untagged_response(CAPABILITY) => ['IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+']
> 2015-02-08 13:46:26 DEBUG: [imap]:   46:26.15 Account sync uwloo _untagged_response(OK, ?, CAPABILITY) => ['IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+']
> 2015-02-08 13:46:26 INFO: ERROR: Saving msg in folder 'archives/y2015', repository 'uwloo-remote' failed (abort). Server responded: command: APPEND => socket error: <class 'socket.error'> - [Errno 14] Bad address
> Message content was: Received: from mailchk-m05.uwaterloo.ca (129.97.128.141) by
>  connhub2.connect.uwaterloo.ca (129.97.149.119) with Microsoft SMTP Server
>  (TLS) id 14....DQolJUVPRg0K

I don't know how Exchange works but here is what I understand from the
logs:

- You locally change a mail of folder, with pdf attachment.

- OfflineIMAP tries to propagate this change back to the IMAP server
  (connect.uwaterloo.ca).

- connhub2.connect.uwaterloo.ca (129.97.149.119) (another server?) send
  a request to mailchk-m05.uwaterloo.ca (129.97.128.141) about that
  change but this internal exchange request fails.


And here is what I understand from all above:
- the exchange IMAP server looks more like a gateway to a more complex
  mail infrastructure;
- when trying to propagate the change internally, exchange fails (a
  unexpected assumption/limitation somewhere?, we don't know);
- the IMAP gateway breaks the socket while it should only send a message
  Error.

It's impossible for us to know what's happening but it really looks like
the Exchange is failing internally at some point, then breaking the
socket and providing a weird message. This message might make sense for
the Exchange admin, though.

Can't tell more, sorry.

-- 
Nicolas Sebrecht