I know I have mentioned this one before, but I've come up with another idea.
Basically the problem is that the 'a' right specifies whether you can change
the ACL on mailbox. This can be a one way trapdoor though, if you give a
user 'a' access on a mailbox, and they accidentally remove it, they ca
Using cyrus 2.1.9, it seems that each time you rename a folder, it adds to
any quota that folder is under...
Connected to xyz.com.
Escape character is '^]'.
* OK xyz.com Cyrus IMAP4 v2.1.9 server ready
. login blah
. OK User logged in
. getquotaroot inbox
* QUOTAROOT inbox user.blah
* QUOTA user
I was doing an strace of some cyrus processes, and noticed quite a few
fsync() and fdatasync() calls in there. We're using mostly skiplists for
mailbox and seen state, and I noticed this in the source code.
if (getenv("CYRUS_SKIPLIST_UNSAFE")) {
do_fsync = 0;
}
And then:
> But "checkpoints" don't happen every N seconds---they happen when the
> skiplist file has reached a certain size (due to so much write volume)
> and merely serve to keep the size of the file down (skiplist files can
> grow to twice the size they "should" be).
>
> Recovery isn't guaranteed to suc
> However observationally we find that under high email usage that
> above 10K users on a Cyrus instance things get really bad. Like last
> week we had a T2000 at about 10,500 users and loads of 5+ and it
> was bogging down. We moved 1K users off bringing it down to
> 9,500 and loads dropped to
> So you will have a choice of 3 commercial Outlook plug-ins,
What are the 3 commercial Outlook plugins? Obviously the Toltec one, but
which others?
I've actually always liked the idea of what toltec + bynari were doing. It's
basically using the IMAP server as a database where folders = tables
> Not a bug, but a feature :) Outlook makes a clear distinction between
> storage and transport. In IMAP this gets a bit blurred as the INBOX is
> also
> the mechanism for receiving new mail. Using the POP3 moves the mail from
> the
> IMAP4 INBOX to the Outlook Inbox. This is handled by both Kont
>> I didn't test but doesn't a symlink work?
>
> Yes, it does (just tried it on a development system).
Definitely, we use it on all our machines.
lrwxrwxrwx 1 root root 23 Oct 26 10:50 proc ->
/tmpfs/imapproc-slot101
Rob
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FA
> About 30% of all I/O is to mailboxes.db, most of which is read. I
> haven't personally deployed a split-meta configuration, but I
> understand the meta files are similarly heavy I/O concentrators.
That sounds odd.
Given the size and "hotness" of mailboxes.db, and in most cases the size of
ma
>> About 30% of all I/O is to mailboxes.db, most of which is read. I
> Solaris 10 does this in my case. Via dtrace you'll see that open() on the
> mailboxes.db and read-calls do not exceed microsecond ranges. mailboxes.db
> is not the problem here. It is entirely cached and rarely written
> (
> This is where I think the actual user count may really influence this
> behavior. On our system, during heavy times, we can see writes to the
> mailboxes file separated by no more than 5-10 seconds.
>
> If you're constantly freezing all cyrus processes for the duration of
> those writes, and
> So, the problem has nothing to do with IMAP, and everything to do with
> message handling before delivery to the mailbox.
If I've assimilated everything right, I think the summary of the problem is:
Outlook handles some email messages specially (the example Joon has used is
iTIP emails). To a
> I do have one ZFS machine, and I don't use it to anywhere near its
> capabilities - it's just backups.
ZFS really did raise the bar on file systems by a big jump, and it's created
a new level of expectation.
For ages we lived with non-journaled file systems and then when we went to
journaled
> There is some system (on freshmeat?) that has a special folder in IMAP
> for storing calendar events. The program uses the IMAP defined protocol
> though.
http://www.kolab.org/documentation.html
It's a reasonably interesting idea. Basically use a sort of folder=table and
email=row database map
> Yes, but that will block possibly valid mail. Of course I don't accept
> mail with non-ASCII RCPT TO addresses because Cyrus doesn't allow it, but
> I should accept non-ASCII MAIL FROM addresses if they are valid. But Cyrus
> also refuses them. That's the real problem.
Can you turn off the 8BIT
>> Can you turn off the 8BITMIME extension that postfix advertises? It seems
>> from the RFC (http://tools.ietf.org/html/rfc4952), if 8BITMIME isn't
>
> That seems to be the right logic but I can't find the proper way to do it
> with postfix.
>
> Anyway, I'm not sure about the whole 8BITMIME thing
> Okay, so you confirm my impression that message content and envelope seem
> to be treated the same way now (for example with postfix). Then, wouldn't
> it make sense to do the same with Cyrus? Could parseaddr() be relaxed to
> do this?
It sounds like the right approach, but there's probably quit
Does Cyrus-imapd take advantage of Dual and\or Quad core processors? We are
looking at upgrading our server to either 2x Dual core Xeon's or 1 x Quad core
Xeon processor. Does Cyrus have the ability to take advantage of this?
Since it uses a multi-process model, yes it does.
However that's no
> but all attempts to simulate
> a client load-pattern are devilishly difficult to get right.
I can atest to this as well.
I created an "imapstresstest" tool a few years back to attempt to stress our
cyrus installs. It attempts to emulate all the main actions of a running
IMAP server like lots
> With your patch applied on my 2.3.11 installation, I now get a number
> of these messages in my logs:
>
> Mar 28 12:57:15 petole imap[25561]: skiplist: /home/cyrus/user/n/niko.seen
> is already open 1 time, returning object
> Mar 28 12:57:18 petole imap[25561]: skiplist: /home/cyrus/user/n/niko
> Squirrelmail on localhost:. very fast, in the blink of an eye,
> likewise with Outlook Express (perish the thought).
>
> So I guess it's Thunderbird. That sucks. I guess I'll take this to a
> Thunderbird forum. Thanks for pointing me in the right direction. Some
> days after troubleshooting every
> opposed to 1.5 - 1.9 MB per process. I've even seen cyrus processes with
> up
> to 30MB.
cyrus uses mmap a lot. The processes probably aren't actually really
growing, they just look bigger because a user has a folder selected and the
cyrus.index file has been mmaped into the process space. If
Ok, so lets get some more details here.
> We've got about 12,000 users, many of whom spend most of the day in
> lectures, and tend to read their email at lunch time. Some staff with
> large
> mail folders tend to stay logged on all day.
> Currently we have four OSX 10.4 servers with 6GB of RAM e
>> Usually we have around 700k simultaneous pop connections on the real
>> servers now with perdition we have 3000+ connections
>
> Er, I didn't write that. That was Ram, the OP. Different person, different
> institution, similar issues. We don't offer POP here.
Ah oops, got a bit mixed up there
> On current production platform the frontends use swap massively but the
> impact is far less than on the new platform.
It's not so much how much swap is actually used, but how much is being paged
in or paged out at any time. If there are memory pages not being used at
all, the OS will swap th
> To get a tiny statistic we are going through all mailboxes and use
> GETANNOTATION to retrieve possible annotations, which is a time consuming
> progress. GETANNOTATION does not like wildcards like LIST.
Yes it does.
Bah, seems the draft is up to -13 now, and they've actually changed the IMAP
> Moving the /var/spool/imap directories, and /var/lib/user/{}.seen
> files to the new server and reconstructing works fine except that all the
> mail shows up as "not read" on the new sever.
The seen state is keyed on the mailbox "uniqueid", so if that changes, the
seen state becomes invalid.
> I have a problem with a high memory consumption using cyrus-imap 2.2 on
> FreeBSD 7.0.
> Each processes of imapd consume 30mb of ram ! I believe that this is not
> normal.
> Is there a way to adjust this?
This is probably fine.
cyrus mmap's lots of files, which often make the process look b
> Is it possible to run several cyrus imap instances (with different
> cyrus.conf
> and imapd.conf files) on the same server?
>
> I will like to have all related files for imap server A in one directory
> (/imapA) and all the related files for imap server B in another directory
> (/imapB). Is it
> The mail is delivered to the INBOX (user.fri)
> The delivery is tried to user.fri.t&-APY-ster, NOT user.fri.t&APY-ster
>
> Any hints where the error occurs?
Yes.
Sieve scripts are in utf-8. You now have to use the true utf-8 name of the
folder in your sieve script, and it's automatically conv
> Is this a bad joke or am I missing something? Sieve scripts of most
> non-English-speakers are intentionally broken due to a BC breaking
> change in a bugfix release version?
I'm afraid you're not missing anything. It bit us as well :(
Fortunately for us, there weren't that many people with no
> Not out of my head, but we probably need to add a configuration
> setting in Ingo to switch between the old and new behavior. Please add a
> request on http://bugs.horde.org.
Might be worth trying to make it an imapd.conf option for cyrus as well to
choose between the old or new behaviour to
We're pretty sure this is related to the timezone being represented as a
short name, as opposed to in numeric format (+0400, etc.). The IMAP spec is
vague on whether or not this format should be accepted. I believe that this has
to do with the way the function from the C Library converts the
> We have a moderately sized Cyrus installation with 2 TB of storage
> and a few thousand simultaneous IMAP sessions. When one of the
> backup processes is running during the day, there's a noticable
> slowdown in IMAP client performance. When I start my `mutt' mail
> reader, it pauses for sever
> I'd probably use imtest to connect, get the PID of the server process
> that I'm connected to, and then attach to that process with ktrace
> (or whatever) with timestamps enabled. Then I'd select the mailbox
> -- this is assuming that mutt is only issuing a select when it says
> "Selecting INBO
> There are /lots/ of (comparative) tests done: The most recent I could
> find with a quick Google is here:
>
> http://www.phoronix.com/scan.php?page=article&item=ext4_benchmarks
Almost every filesystem benchmark I've ever seen is effectively useless for
comparing what's best for a cyrus mail se
> Now see, I've had almost exactly the opposite experience. Reiserfs seemed
> to
> start out well and work consistently until the filesystem reached a
> certain
> size (around 160GB, ~30m files) at which point backing it up would start
> to
> take too long and at around 180GB would take nearly
> Running multiple cyrus instances with different dbs ? How do we do that.
> I have seen the ultimate io-contention point is the mailboxes.db file.
> And that has to be single.
> Do you mean dividing the users to different cyrus instances. That is a
> maintenance issue IMHO.
As Bron said, yes it
> Ext4, I never tried. Nor reiser3. I may have to, we will build a brand
> new
> Cyrus spool (small, just 5K users) next month, and the XFS unlink
> [lack of] performance worries me.
>From what I can tell, all filesystems seem to have relatively poor unlink
performance and unlinks often cause
>> We've found that splitting the data up into more volumes + more cyrus
>> instances seems to help as well because it seems to reduce overall
>> contention points in the kernel + software (eg filesystem locks spread
>> across multiple mounts, db locks are spread across multiple dbs, etc)
>
> Make
> Since I upgraded to 2.3.13 (Invoca RPM rev 4) I've been running into a
> mysterious replication bug. In some circumstances, creating a user with a
> three
> letter long username causes the sync master process to choke, on either
> signal
> 11 or 6. Like this:
Interestingly, we just encountered
> I would like to add a *lot* more storage so that we can increase our email
> quotas (currently 200MB per user). It seems like the proper way to scale
> up is to split the Cyrus metadata off and use some large SATA drives for
> the message files. I was considering adding a shelf of 1TB SATA dri
> I have inherited a cyrus / postfix server, which is generally
> well-behaved.
> However, there is an intermittent error when delivering messages to a
> certain
> mailbox. It is infrequent, and generally the message is delievered on the
> user's next attempt in his MUA. The log is something l
> Our plan is to throw 12-16GB at it, with the purpose of vastly increasing
> the FS buffer cache (and decreasing I/O). Or, will that just be a waste
> of RAM?
>
> Some indications are that, yes, it does improve performance notably:
>
> http://blog.fastmail.fm/2007/09/21/reiserfs-bugs-32-bit-vs-6
>> I am blocked with websieve.pl vacation/out-of-office because when users
>> are entering accents the script fails with an error...
>>
>> Does anyone has a suggestion on how to make accents work ?
>
> Yes, but I haven't committed it to CVS yet. I'm working on full
> UTF8 support in sieve scripts
>> - IMAP protocol extensions (most needed thing would be to "idle" on
>> every folders, not just inbox)
>
> Yeah, good luck with that one. It's a pretty major "protocol extention",
> and everything's very folder centric. It would be a rather large SMOP
> (small matter of programming) for this.
> I think the problem with apple mail client not displaying shared folders
> in the subscription list is well known ...
>
> My question is: can something be done on the cyrus side to work around its
> problems? Google seems to have implemented something ...
Use the "altnamespace" option.
You c
Check out the "auditlog" patches we have here:
http://cyrus.brong.fastmail.fm/
It syslogs every message/folder create/delete in a fairly regular format. eg
things like:
auditlog: create sessionid=<...> mailbox=<...> uniqueid=<...>
auditlog: delete sessionid=<...> mailbox=<...> uniqueid=<...>
au
> We also wanted to use -U 1 so we could be sure changes to imapd.conf
> would be used more quickly since there wouldn't be imapd procs hanging
> around with old settings.
FYI, another way of doing this without forcing -U 1 is to touch the imapd
executable file.
The cyrus master notices if the
> Also, does anyone know what this means for searches on material that has
> changed since the last squatter run? I have assumed, and hope, that the
> search procedure is something like this:
> search in the squatter index
> remove results referring to deleted items
> do an unindexed search on ite
> - cyrus-imapd-2.3.7 (from RHEL5/CentOS-5) with some minor patches in the
> popd (UUID format and an enhancement to the authentication - both
> shouldn't have any impact on the storage part)
As I'm sure others will mention, this is a quite old cyrus now with many
known bugs.
You chould defini
> Well - it's theoretically possible. But I don't know anyone who's done
> it, and it has the potential to get ugly if you're delivering to the
> same mailboxes at each end. There's nothing I can see that would
> actually stop it working.
I think Bron failed to put sufficiently large warning si
> i'm very surprised that there is not really official point from cyrus-imap
> dev team against using cyrus in cluster active/active mode
I can't comment, but I guess they're busy.
> Since serverals years the messaging service become very important and the
> clustering system is the right way
> Client A: upload message to Inbox, gets UID 100
> At the same time, Client B: upload message to Inbox, gets UID 100
>
> You can't have two messages with the same UID.
>
> There's 3 solutions I can see:
>
> 1. Mysql solves this by having interleving id's on separate servers (eg.
> auto-incremen
> it seems that running squatter nightly on all mailboxes takes too long for
> us. I'm thinking of splitting the mailboxes over different nights or
> doing
> the job over the weekend.
Are you using the new incremental mode david carter added?
-i Incremental updates where squat indexes alre
>> > It's quite likely, that these mailboxes will grow to 50 or even
>> > more then
>> > 1M mails per mailbox.
>> >
>> > Does anybody have experience with such big mailboxes?
>>
>> Is the I/O cost of message adding relative to O(n), n being the number of
>> msgs
>> already in the mailbox, o
>> For low bandwith connections this could be useful but I don't know if
>> that's a typical case nowadays. Together with the IMAP IDLE command it
>> should be fine for mobile devices...
>>
>> [1] http://tools.ietf.org/html/rfc4978
>
> I thought that this was supported in 2.3.16.
It's definitely
Also check out the Fastmail auditlog patches.
http://cyrus.brong.fastmail.fm/
Rob
- Original Message -
From: "Dr. Tilo Levante"
To:
Sent: Friday, May 28, 2010 7:59 PM
Subject: Log all actions
>
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.
Hi
I'm just testing out upgrading from cyrus 2.1.9 to cyrus 2.2.3. So far
everything seems to work pretty much fine, except for one thing. On some
existing folders, when you try to 'expunge' them, imapd segfaults. It's not
all folders, only some folders, though it is reproduceable for the "broken"
> This sounds a *lot* like the bug I fixed right before release. And if
> thats the case, delivering message to the folder is also highly likely to
> fix the problem.
Hmmm, is it a variation on the same bug perhaps?
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x08074b41 in mail
> If you're using v2.2.3, its fairly easy. In mailbox.h, bump
> MAILBOX_CACHE_MINOR_VERSION to 3 and in mailbox.c add an entry like
> {"Xmyheader", 3} to the mailbox_cache_headers array. Any new messages
> added to the mailbox will have this header cached. If you want all of
> the messages to h
> You are getting very similar results because you are using "*" as the
> reference argument. Cyrus concatenates the reference and pattern. Try
> these and see the difference:
>
> . LIST "" *
>
> . LIST "" %
Sure, but should a 'list' command ever return the same mailbox name multiple
times. It j
A while ago I wrote an IMAP client interface in PERL for a project I was
working on. At the time I looked at Net::IMAP, Mail::IMAPClient and
Mail::Cclient, but they all had problems that made them annoying in some way
(broken literals in envelopes, non-structured bodystructure responses, etc).
Most
You can't. There isn't any support for cross-domain ACLs. The biggest
impediment to adding this is how to handle 'anyone' and 'anonymous'. Are
these pseudo users inter-domain or intra-domain only?
As a suggestion, you could use "anyone/anonymous" for inter-domains, and
"[EMAIL PROTECTED]/[EMAI
This is what originally occurred to me, but consider the case of a
single domain server which then upgrades to virtdomains. Any mailbox
which uses anyone/anonymous in an ACL is now open to anyone/anonymous in
ANY domain on the server. I don't think we can assume that this is what
the admin in
Reiser also has a nolog option, which I didn't try. There are quite a
few more knobs to tweak for all the filesystems.
Try mounting with:
noatime,nodiratime,notail,data=journal
That's what we use and consistently get the best performance with. I've
posted previous experiences and thoughts wi
We are using 2.3.7 on Debian Sarge.
We will maybe move to solaris because of the features of ZFS.
Does anyone know the status of ZFS + fsync performance problems?
http://www.irbs.net/internet/info-cyrus/0610/0058.html
Rob
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: ht
Jeff and I have already discussed pushing out a 2.3 release soon -- as
soon as we iron out all of the wrinkles in our 2.3 deployment on campus.
We found a few small buglets in the IMAP proxy code that we didn't
expect. Either nobody else has a 2.3 Murder running, or they didn't
notice the random
the usual reason for allowing the "anyone" ACL is to allow for +
addressing to
work.
is there another way to do this?
The admin user can still set the anyone acl, it's just non-admin users can't
change/set it. The way we do this to allow + addressing is when we create
the users top level f
but this is in conflict with the the idea that in a large installation of
people who don't know each other the 'anyone' permission doesn't make
sense.
what is really desired for + addressing is to say that messages that
arrive via the lmtp interface are allowed to write to all folders (not
ju
Ok, I thought that 'post' pre-dated lmtp and was the IMAP function to
write a message into the folder.
i.e. a program like imapsync would need the 'p' permission to write the
messages, (but would need other permissions to check for messages, set
flags, etc)
I think the only way to add a mess
as fastmail.fm seems to be a very big setup of cyrus nodes, I would be
interested to know how you organized load balancing and managing disk
space.
Did you setup servers for a maximum of lets say 1000 mailboxes and then
you use a new server? Or do you use a murder installation so you can move
May I ask how you are doing the actual replication, technically
speaking? shared fs, drbd, something over imap?
We're using the replication engine in cyrus 2.3
http://blog.fastmail.fm/?p=576
Rob
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.ed
Thanks, that was interesting reading.
Is there any specific reason you didnt opt for a cluster filesystem?
Internal knowledge mostly. We very were familiar with the performance and
overall usage implications of a local filesystems on locally attached
SATA-to-SCSI RAID boxes that we've been u
Attached is our operation group's notes on the subject. It makes
reference to the tool we use to manage the OS of the machines
(radmind), but it should be pretty clear what they are talking about
without any radmind knowledge.
As an FYI, we have a similar procedure to this, the main differences
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2871
I also found out that delayed_expunge doesn't help if a whole folder got
deleted. So if something like your proposed solution gets included that
would really be a very nice feature.
Agreed. This would also allow for "complete" backups of al
I already mailed the author of imapsync about that some days ago but
without having an idea how to fix it. I also checked Mail::IMAPClient and
found that it lacked the functionality needed here but it seems
Mail::IMAPClient isn't maintained anymore (at least there is no
development for long time n
so I wonder, will skiplist be a better choice? obviously running
quota(8) will be a very cheap operation, but I'm worried about
contention on the quota database during delivery etc. (these users are
for the most part not actively using the system -- they get less than
one message per day each(
Interesting, I have some folders with ~100'000 messages and cyrus handles
it very nice. Did you say you have a problem with 10'000 messages in a
mailbox?
And I dealt with a user the other day with 280,000 in their inbox.
Filesystem and cyrus were fine, though our web interface was a bit slow.
Fastmail dont use SAN, as I understand they use external raid arrays.
There are many ways to lose your data, one of these being filesystem
error, others being software bugs and human error. Block-level replication
(typically used in SANs) is very fast and uses few resources but doesnt
protect f
I agree of course about avoiding SPOFs, but I do like a multi-tiered
approach, I mean multiple lines of defense. I use SAN for its speed,
reliability, and ease of administration, but naturally I replicate
everything on the SAN and have "true" backups as well.
So you have multiple SAN's? Or y
I agree that storage and replication are orthogonal issues. However, if a
lump of storage is no longer a single point of failure then you don't have
to invest (or gamble) quite as much to make that storage perfect.
Yes, that old maxim that each extra 9 in 99.99... reliability costs 10 times
mo
So how can I help to find this bug. I had i look at bugzilla, but found
nothing related.
I think this bug is actually in the regex library, not in cyrus. I do wish
cyrus would use PCRE if it was available though, PCRE seems much more robust
than the GNU posix regcomp/regexec stuff. Hmmm, I ju
As of RFC 2045, Content-Type syntax should be:
content := "Content-Type" ":" type "/" subtype *(";" parameter)
Shouldn't cyrus still interpret this as text/html, despite the illegal "
boundary..." line following Content-Type ?
I've noticed this too, and while it clealy is broken with respect t
You can view the load average and process counts for these servers at:
https://secure.onid.oregonstate.edu/cacti/graph_view.php?action=tree&tree_id=4
OT, but I found this interesting... I wonder when school starts and ends and
when holidays are :)
https://secure.onid.oregonstate.edu/c
see the output of the command "iostat -x sdb 5" (where 'sdb' is the device
you have cyrus on) on your system. Even if you aren't saturating your
Gigabit Ethernet link to the ATA-over-Ethernet storage, you may be
exceeding the number I/O operations per second.
I thought ATA-over-Ethernet had h
After running iostat on my cyrus partition (both config and mail spool
are
kept on a SAN), I'm wondering if I should separate them out as well.
This
sounds related to the new metapartition and metapartition_files options
that were added in v2.3.x.
Does anyone have any recommendations or guidanc
Can values way above 100% be trusted? If so, it's pretty bad (this is
from a situation where there are 200 lmtp processes, which is the
current limit I set):
I've never seen over 100%, and it doesn't seem to make sense, so I'm
guessing it's a bogus value.
avg-cpu: %user %nice %system %i
I had to reduce the default value of
"lmtp_destination_concurrency_limit" in postfix to 10 (the default is
20), and change the value of "queue_run_delay" on some servers to avoid
having them all run their queues at the same time, because that ends up
causing the lmtpd process limit to be reached.
I am trying to control whether when sorting by the recipient or sender
whether it sorts by the name or by the email address. Is this possible?
It's defined by the IMAP sort extension.
http://tools.ietf.org/html/draft-ietf-imapext-sort-19
FROM
[IMAP] addr-mailbox of the first
Is it safe? - we calulated that with one billion messages you have a one
in 1 billion chance of a birthday collision (two random messages with
the same UUID). They then have to get in the same MAILBOXES collection
to sync_client to affect each other anyway.
Isn't the case: UUIDs span al
With hindsight I should probably have defined message UUIDs to be the full
MD5 hash: 128 bits isn't that much worse than 96 bits per message. What is
the CPU overhead like for calculating MD5 sums for everything on the fly?
That would have been nice, and from an integrity point of view as well,
The provided Cyrus tool "make_md5" is for validating replication. It
would, for instance, have found the recently discussed bug in sync_server
that caused random files to be overwritten in the event that sync_server
reused a stale staging file. It would probably be cool if there were
doc
I manage a single-instance server running v2.2.12 with a reasonably
large number of mailboxes, using "mboxlist_db: flat":
Why are you using "flat"? The flat db implementation is pretty basic/kludgy
and not designed for large database files. I bet it's doing something stupid
like re-reading t
You perhaps think we are adding Perdition to the mix, and assuming we
have a single box that might get overloaded. No, we've had Perdition
running on a load-balanced pool of 4 Linux boxes for about a year and a
half. This was our abstraction to hide the 10+ UW-IMAP servers from the
user pop
> I don't have something to consume make_md5 data, yet, either. My
> plan is to note the difference between the replica and the primary.
> On a subsequent run, if those differences aren't gone, then they
> would be included in a report.
Rather than make_md5, check the MD5 UUIDs patch below. Using
>I run it directly, outside of master. That way when it crashes, it
> can be easily restarted. I have a script that checks that it's
> running, that the log file isn't too big, and that there are no log-
> PID files that are too old. If anything like that happens, it pages
> someone.
Ditto, we
> does the IMAP spec specify how large a UUID can be?
UUIDs aren't part of the IMAP spec. It's an addition to cyrus to help
replication. By default, there's no way to access UUIDs via IMAP at all
since they're not part of the IMAP spec.
The UUID size chosen was done by David Carter when he impl
> I suspect that the problem is with mailbox renames, which are not atomic
> and can take some time to complete with very large mailboxes.
I think there's some other issues as well. For instance we still see
skiplist seen state databases get corrupted every now and then. It seems
certain corrup
> So, as I understand it, when reconstructing mailboxes, internal dates
> will be lost. It this intentional, or did I miss something in the
> docs/manual ?
This is why we created this patch.
http://cyrus.brong.fastmail.fm/#cyrus-receivedtime-2.3.8
Rob
Cyrus Home Page: http://cyrusimap.web.
1 - 100 of 161 matches
Mail list logo
