Rich Wales wrote:
Earlier, I wrote:
What do I need to do in order for changes made on the replica
to get copied over to the master?
Bron Gondwana replied:
Impossible. You don't do this. What you can do (the simple
case of what we do) is set up two Cyrus instances on each
machine,
A common scenario when we are moving users between partitions is to
want to move their archived mail first, because there's less risk of
disrupting them, and then their top-level mailbox last.
So we want to do:
rename --partition new-partition user.name.box user.name.box
and then later
Hi,
We run a 35,000 mailbox system with no problems on Solaris. We did
a few years back have a bad time with using Berkeley DB and cyrus and
switching to skiplist fixed that. I believe that problem has been
solved though. I would recommend using multiple spools however, having
one big
On Mon, Nov 12, 2007 at 12:34:34AM +1100, Bron Gondwana wrote:
Anyway - here it is. A recovery() that copes if the logstart
parameter in the database header is wrong. No, I don't have a
clue how that happened unless lseek() lied. Maybe it sometimes
lies, I don't know. I'll be writing a
On Sun, Nov 11, 2007 at 08:41:04PM -0800, Rich Wales wrote:
Earlier, I wrote:
What do I need to do in order for changes made on the replica
to get copied over to the master?
Bron Gondwana replied:
Impossible. You don't do this. What you can do (the simple
case of what we do) is
On Mon, Nov 12, 2007 at 11:38:54AM +, Ian G Batten wrote:
A common scenario when we are moving users between partitions is to
want to move their archived mail first, because there's less risk of
disrupting them, and then their top-level mailbox last.
For a different approach - we use
Bron Gondwana wrote:
It doesn't work like that. Rolling replication gets events from
actions on mailboxes (lmtp deliver, imapd updates, etc) and logs
them - then the sync_client process running in the background
reads that log file and uses the actions to know what things to
check and sync
On Mon, 12 Nov 2007 09:37:12 -0800, Rich Wales [EMAIL PROTECTED] said:
Bron Gondwana wrote:
It doesn't work like that. Rolling replication gets events from
actions on mailboxes (lmtp deliver, imapd updates, etc) and logs
them - then the sync_client process running in the background
Bron Gondwana wrote:
[A mailbox list on the sync_client command line] works fine as a
one-off, but not for rolling, because rolling reads the log.
Understood.
That said, only users who have had any actions on that server will
create log entries.
Interesting. This actually suggests that I
hi,
I found here is an option sasl_pwcheck_method and a lot of ldap_xxx
like options.
and also this in 'man 5 imapd.conf':
allowapop: 1
Allow use of the POP3 APOP authentication command.
Note that this command requires that SASL is compiled with APOP support,
that the plaintext
Gary Mills wrote:
Thanks everyone for your responses. I don't want to clutter up this
technical mailing list with more management issues, although I'd
certainly be pleased to receive personal e-mail on this topic.
There appear to be two types of outsourcing. The Google example was
one
Our latency problems went away like a miracle when we detached one half of
the mirror (so it is no more a mirror).
Read-Rates are doubled (not per device, the total read rate!), latency is
cut off. No more latency problems.
When attaching the volume again, resilvering puts the system to a halt
OK, so I decided to try what I described earlier (replication in both
directions, with different users using different master servers) . . . .
But now I'm running into an authentication problem. One of my servers
(my original replica) simply refuses to authenticate to the other one
(my original
If we could ever get a decent calendar system that works together with
Cyrus or other software many people would be happy.
Rudy
--
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734
Directie ICT, afd.
14 matches
Mail list logo
