search for: authmech1

...t up the enviroment in dovecot with post login scripting in which imapsync does sync between two mailservers on users login (on login sync mail from old to new mailserver) is there a alternative or different approach? something like #!/bin/bash /usr/bin/imapsync --syncinternaldates --nosyncacls --authmech1 PLAIN --host1 old.server.com --user1 $USER*master --password1 master --authmech2 PLAIN --host2 new.server.com --user2 $USER*master --password2 master exec /usr/lib/dovecot/imap "$@" thanx -- View this message in context: http://old.nabble.com/Post-login-scripting-and-imapsync-on-user-lo...

...ommand line options: /usr/local/bin/imapsync --noreleasecheck --useheader ALL --delete2 --expunge2 --tmpdir /var/vmail/cache --subscribe --subscribed --tls1 --tls2 --usecache --nofoldersizes --nocheckmessageexists --host1 oldserver.domain.com --authuser1 adminuser --user1 testuser at domain.com --authmech1 PLAIN --password1 <HIDDEN> --host2 newserver.domain.com --authuser2 adminuser --user2 testuser at domain.com --authmech2 PLAIN --password2 <HIDDEN> All email is copied over and stored in dovecot as you would expect. Then I switch the user to the new server on the imapproxy and restart...

I am trying to sync my mail on two different servers as testing for converting our business over to a server using dovecot. I am currently running dovecot version 2.0.11 While trying to sync the messages using Thunderbird and a program named imapsync, I run into an error stating that the dovecot server does not know how to handle messages with the FORWARD flag set. Is the FORWARD flag

Hello all, OK, I would really appreciate your help on this. I managed to do a pretty straight-forward and flawless migration on dovecot from one domain to another. However, I have this nagging problem with most of the thunderbird MTAs. When I try to delete some "test" messages I sent to make sure that everything works, it comes back with the following message on the bottom of the