RE: Moving data from Cyrus 2.3.7 (RHEL) to 2.3.16 (Invoca)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Quoting "Simpson, John R" <john_simpson@xxxxxxxxxx>:



John Simpson
Senior Software Engineer, I. T. Engineering and Operations
All the basics seem to be working, thank you again for your help.

One last question. With rolling replication, should the replica automatically catch up to the master or do I need to "seed" the replica with rsync (or a batched sync_client)?

You should use sync_client -u to bring the replic in sync with the master.
This will also take care of sieve scrtipts and mailboxes that don't change
often.

I can replicate individual mailboxes with "sync_client -m <mailbox>" and mailboxes are replicated when they receive a new message, but if neither of those actions takes place the replica is not populated.

Yes



--------------------------------------------------------------------------------
M.Menge                                Tel.: (49) 7071/29-70316
UniversitÃt TÃbingen                   Fax.: (49) 7071/29-5912
Zentrum fÃr Datenverarbeitung mail: michael.menge@xxxxxxxxxxxxxxxxxxxx
WÃchterstraÃe 76
72074 TÃbingen

Attachment: smime.p7s
Description: S/MIME Signatur

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

[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux