Bug 22231

imapsync-1.255-alt1

Now the source and the destination for imapsync can only be network ports:

$ imapsync --help | head -20

usage: /usr/bin/imapsync [options]

Several options are mandatory. 

--host1       <string> : "from" imap server. Mandatory.
--port1       <int>    : port to connect on host1. Default is 143.
--user1       <string> : user to login on host1. Mandatory.
--authuser1   <string> : user to auth with on host1 (admin user). 
                         Avoid using --authmech1 SOMETHING with --authuser1.
--password1   <string> : password for the user1. Dangerous, use --passfile1
--passfile1   <string> : password file for the user1. Contains the password.
--host2       <string> : "destination" imap server. Mandatory.
--port2       <int>    : port to connect on host2. Default is 143.
--user2       <string> : user to login on host2. Mandatory.
--authuser2   <string> : user to auth with on host2 (admin user).
--password2   <string> : password for the user2. Dangerous, use --passfile2
--passfile2   <string> : password file for the user2. Contains the password.
--noauthmd5            : don't use MD5 authentification.
--authmech1   <string> : auth mechanism to use with host1:
$ 

It would be quite convenient if one could use imapsync with a local imap server through a local socket, so that the imap server runs completely privately, without any exposure to unpredictable connections on the network port.

(This would be useful for creating and maintaining a local copy of a remote mailbox on a computer which is not supposed to be set up as an IMAP server accepting untrusted incoming connections, doing authentication etc.)