Hello,
  thanks for your help, you're right again :).
  I've some users, they are my test lab mouses.
I tried to use imapsync, but I wasn't able to migrate - some security reasons. On the syslog on old email server : Jul 21 13:35:18 machine saslauthd[2911]: DEBUG: auth_pam: pam_authenticate failed: Authentication failure Jul 21 13:35:18 machine saslauthd[2911]: do_auth : auth failure: [user=blackhol] [service=imap] [realm=] [mech=pam] [reason=PAM auth error] Jul 21 13:35:18 machine imaps[13753]: badlogin: email2.fnhk.cz [195.113.123.113] plaintext blackhol SASL(-13): authentication failure: checkpass failed

  command was:
/usr/bin/imapsync --noauthmd5 --syncinternaldates --subscribe --host1 email1 --user1 blackhol --user2 blackhol --ssl1 --authuser1 cyrus --password1 MASKED --host2 email2 --authuser2 cyrus --password2 MASKED --authmech1 LOGIN --authmech2 PLAIN

  Thanks
  J.K.

Cituji Eero Hänninen <f...@nohik.ee>:

Hi,

That's because You don't have copied over from old machine seen state files. They are located somewhere /var/imap/user/$user_letter/$username.seen or so. But if you copy them now, then you restore old mails states, but mails what arrived after migrating process will be marked again unread - so users will be confused again. Anyway, if you still plan copy seen state files over, then you must run reconstruct again.

P.S. This manual user migration is very complicated process and mistakes will happen very easy, so I strongly recommended, that you test with 1 or 2 mailboxes before such kind migration and make sure that after test migration mailboxes work correctly on new system. Its better use imapsync or such tool, to sync user mailboxes and mail states..

Rgrds,
Eero

On Thu, 21 Jul 2011 12:38:57 +0200, Josef Karliak wrote:
Hi,
 that's it ! This a right command that discovered me users and
recovered quota usage. So this is a next command after "reconstruct",
I must write it somewhere  :)
 Anyway - why are all mail unreaded after import and reconstruction
? Users will ask me ... :)
 Thanks
 J.K.

Cituji Eero Hänninen <f...@nohik.ee>:

Hi Josef,

On Thu, 21 Jul 2011 09:06:32 +0200, Josef Karliak wrote:
Hello,
after copying mails to the new server and reconstructing emails
with a command "sudo -u cyrus /usr/lib/cyrus/bin/reconstruct -r -f
user.<username>" seems to be all fine. But after some fights with
plugin for check quota in the Squirrelmail I tried a command for
listing quota in the "cyradm". Command mentioned above didn't
reconstructed usage. Reconstruction of the usage works fine only in
the "cyradm". But it doesn't accept wildcard "*" to reconstruct all
mailboxes. So there is a question - how to reconstruct all ? Any ideas
?

Try run after reconstruct:
sudo -H -u cyrus /usr/lib/cyrus/bin/quota -f

As I understand, cyrus uses unix philosophy, one tool must do on thing, but it must do it well :) So reconstruct tool is for reconstruct mailboxes so called filesystem (discover missing messages, folders, or remove them from indexes/internal db if they don't exist anymore, etc). Quota tool is for recalculate mailbox usage and there is no point to run quota fix after every mailbox reconstruct.

Please correct me, if I'm wrong.

Rgrds,
Eero






--
Ma domena pouziva zabezpeceni a kontrolu SPF (www.openspf.org) a DomainKeys/DKIM (with ADSP) . Pokud mate problemy s dorucenim emailu, zacnete pouzivat metody overeni puvody emailu zminene vyse. Dekuji. My domain use SPF (www.openspf.org) and DomainKeys/DKIM (with ADSP) policy and check. If you've problem with sending emails to me, start using email origin methods mentioned above. Thank you.

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Attachment: binIImOIBjNFm.bin
Description: Veřejný PGP klíč

----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

Reply via email to