Re: [Mailsync-list] Courier to Exchange - empty Inbox??

[Holger K. <hol...@gm...>]

> 1st, using "tls" rather than "ssl" mailsync cant connect to Courier 
> because it tries on port 143. Strange...

That is not strange, that is by design. tls uses same port as nonencrypted imap. ssl uses higher port. I need tls here.


> 2nd, using "us...@so...main" cause an authentication error, so I set it
> as plain "user".

That depends on server setup. If the server has more than one domain, it is wiser to use the complete email adress as login name.


> 3rd, the following config moved messages, but didn't preserve the 
> structure, which for me is very important because the executive types 
> who (want this Exchange server in the first place), have Gigabytes of 
> saved mail and will freak out if the structure blows up.

I hope you test with test accounts. 



> Can you suggest any changes that might make transfers keep the tree 
> structure intact?
> 

Maybe try to omit the prefix in exchange . Like

 
 store exch {
        server  {exchange.mycompany.com/user=test/ssl/novalidate-cert/norsh}
        ref     {exchange.mycompany.com}
        pat     *
        passwd  sectret_shake
 }

All servers i tried so far didn't need this. But i never used exchange with mailsync, so i don't know if the use a special layout.