Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 38

Thread: 4.0 RC1 imapsync with admin???

  1. #21
    Join Date
    Nov 2006
    Posts
    5
    Rep Power
    8

    Default

    Did you use perdition to make imapsync work? Could you list port that you use?
    Currently I am using
    zimbraImapBindPort: 7143
    zimbraImapProxyBindPort: 143
    zimbraImapSSLBindOnStartup: TRUE
    zimbraImapSSLBindPort: 7993
    zimbraImapSSLProxyBindPort: 993

    value for imap clear text login is true
    But it still not work? Imapsync stop with message

    Error connecting to mail.domain.com:7993:

  2. #22
    Join Date
    Nov 2006
    Posts
    5
    Rep Power
    8

    Default

    ok then I found the solution. It's simple I just need to send email ask for every user password. And I could use imapsync to copy their mailbox to the new server (I don't know why its difficult just to copy user mailbox from my zimbra 3 server to new zimbra 4 server). Next time, I would think twice installing zimbra on the new server. Installing from scratch I think much better, although it will not have nice administrator web UI like zimbra.
    Thanks anyway.

  3. #23
    Join Date
    May 2007
    Posts
    63
    Rep Power
    8

    Default

    Does this method still work under 4.5.5? I've been trying various combinations with no luck today. Works fine user -> user, but I'd like to use the admin functionality on zimbra, since I don't know the user's passwords (I'd have to set to a dummy pass, then reset to their crypt pass, which will take longer at migration time).

    Like.
    /usr/bin/imapsync --syncinternaldates --host1 fromhost --noauthmd5 --user1 fromuser --password1 fromuserpass --noauthmd5 --host2 tohost --user2 tohostuser --authuser2 tohostadmin --password2 tohostadminpassword

    This fails, dovecot is the source, zimbra is the destination. Zimbra doesn't pay attention to the authuser2, and fails auth, since the password for host2 is the admin's pass, with tohostuser's pass it works fine.

  4. #24
    Join Date
    Aug 2005
    Posts
    1,433
    Rep Power
    12

    Default --ssl2

    AUTHENTICATE PLAIN requires the --ssl2 switch, I believe.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  5. #25
    Join Date
    May 2007
    Posts
    63
    Rep Power
    8

    Default

    Yea, I had tried all the various combinations I saw on the forums. I discovered IMAPsync wasn't working with SSL, moved to a different machine and compiled all the perl modules myself (instead of Fedora RPM), and it worked as expected through SSL via the Master Admin login.

  6. #26
    Join Date
    May 2007
    Location
    Calgary
    Posts
    62
    Rep Power
    8

    Default Still Trying imapsync

    I have moved to another server and compiled imapsync again.
    I can log into the account into Zimbra with imapsync.
    I can login into the account with thunderbird.
    I can telnet to the imap port 143 and login
    I use TLS as well with the Thunderbird.
    No go with imapsync
    I can login successfully into my current courier imap server.

    I realized that the compiled script, although nice, I was not watching the packages that failed to compile properly. I'll try to get a test script done to test that the packages installed okay.

    Here are the different options I have tried, which option have I not tried? or maybe something else is wrong with imapsync?

    Thanks


    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --ssl2

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --ssl1

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --authuser2 PLAIN

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --authuser2 PLAIN --ssl2

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --port2 7143

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --authuser2 PLAIN --ssl2 --port2 7143

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --ssl2 --port2 7143

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --port2 7143

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --ssl2 --port2 7993

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --ssl2 --port2 7993

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --ssl2 --port2 7993

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --ssl2

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --authuser2 PLAIN

    imapsync --nosyncacls --subscribe --syncinternaldates --host1 192.168.0.50 --user1 name@domain.com --password1 passpass --host2 192.168.0.111 --user2 name@domains.com --password2 passpass --authuser2 PLAIN --ssl2

  7. #27
    Join Date
    Jul 2006
    Location
    New York, NY
    Posts
    122
    Rep Power
    9

    Default

    I ran into the same problem. Was there a version change in imapsync? I can hit the Zimbra server over the SSL port and i get this using:

    openssl s_client -connect mail.xxx.com:7993

    *OK mailbox.talkpoint.com Zimbra IMAP4rev1 service ready*

    But when using imapsync:

    imapsync --justconnect --host1 mailserver1 --host2 mailserver2 --ssl2 --port2 7993

    The first server responds and the second server (zimbra) just hangs

    Now could this be because of the self-signed certificate?

  8. #28
    Join Date
    May 2007
    Location
    Calgary
    Posts
    62
    Rep Power
    8

    Default imapsync more guessing

    Tried:
    [root@mail ~]# perl -c imapsync
    imapsync syntax OK

    So it seems imapsync is installed correctly.
    Looking back, it might have worked on previous versions of imapsync. It looks like the owner of this project removes all his past versions so I can't test an older version.

    I haven't gotten to part to watch the log files for imap activity, but it looks like I can get Thunderbird to connect to Zimbra successfully via imap both SSL(993) and normal(143).

    So, I think its imapsync thats the issue here. Not having past copies or knowledge to watch the imap log files, I will have to hang on for someone else to see what the issue might be.

    Cheers

  9. #29
    Join Date
    May 2007
    Posts
    10
    Rep Power
    8

    Default

    Me2 - I've tried picking up an old version of imapsync using the web archive at Internet Archive but have not yet managed to find anything. Is it known which is the latest version of imapsync to work (assuming it is an imapsync issue!)

    rm

  10. #30
    Join Date
    May 2007
    Location
    Calgary
    Posts
    62
    Rep Power
    8

    Default imapsync

    I am getting great help, and this is where I am at. Give this a try and let me know how you make out. I am using current version of imapsync ver 1.219

    imapsync --host1 192.168.0.1 --user1 name@domain.com --password1 pass \
    --host2 192.168.0.2 --user2 name@domain.com --password2 pass \
    --noauthmd5 --syncinternaldates

Similar Threads

  1. imapsync works to the zimbra admin user, but not others?
    By justanotheruser in forum Migration
    Replies: 3
    Last Post: 04-05-2007, 10:22 AM
  2. 4.0 Rc1
    By scalper in forum Administrators
    Replies: 3
    Last Post: 08-26-2006, 11:00 AM
  3. 4.0 RC1 Deferred queue problem
    By neilmc in forum Administrators
    Replies: 8
    Last Post: 08-26-2006, 03:31 AM
  4. Logger not working in 4.0 RC1
    By jdell in forum Administrators
    Replies: 11
    Last Post: 08-24-2006, 07:50 PM
  5. ZCS 4.0 RC1 to launch this week
    By KevinH in forum Announcements
    Replies: 1
    Last Post: 08-14-2006, 09:37 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •