Hi,
On Mon, 13 Sep 2010, Forrest Aldrich wrote:
I have an older system that crashed - cyrus version is a couple years or
so old. I have 1000's of messages in the spool that I need to preserve.
My question is about whether there's a way to import that huge tree of
messages into a new cyrus
Sorry for the delay getting back about this, I meant to let people know
that the reason for this:
Also when this happens the cyrus master process kills all other active
imapd processes and restarts, is there a reason for this?
I've never heard of master doing that in response to ANY child
Hello,
Strange problem:
-
Sep 14 09:18:12 mail cyrus/imap[21928]: TLS server engine: cannot load
CA data
Sep 14 09:18:12 mail cyrus/imap[21928]: unable to get certificate from
'/etc/apache2/ssl/mail_rcg_nl.crt'
Sep 14 09:18:12 mail cyrus/imap[21928]: TLS server engine: cannot load
On 09/14/2010 07:51 AM, Paul van der Vlis wrote:
Hello,
Strange problem:
-
Sep 14 09:18:12 mail cyrus/imap[21928]: TLS server engine: cannot load
CA data
Sep 14 09:18:12 mail cyrus/imap[21928]: unable to get certificate from
'/etc/apache2/ssl/mail_rcg_nl.crt'
Sep 14 09:18:12 mail
We've been running sync replication between two servers for a few months
now and everything has been working well. Recently, management has come
down and asked if it's possible to have the sync only perform additions
and to ignore deletions. The idea is that they would like our backup
server (or
Quoting Derek Chen-Becker dbec...@cpicorp.com:
We've been running sync replication between two servers for a few months
now and everything has been working well. Recently, management has come
down and asked if it's possible to have the sync only perform additions
and to ignore deletions. The
On Tue, Sep 14, 2010 at 08:03:47AM -0500, Derek Chen-Becker wrote:
We've been running sync replication between two servers for a few months
now and everything has been working well. Recently, management has come
down and asked if it's possible to have the sync only perform additions
and to
For Solaris SMF and Cyrus please use in your manifest for Cyrus IMAP:
property_group name='startd' type='framework'
propval name='ignore_error' type='astring' value='core,signal'/
/property_group
The imap service will not be restarted when an imap process is killed anymore.
Only
On 09/04/2010 07:41 AM, Jeroen van Meeuwen (Kolab Systems) wrote:
To allow some early feedback, I'm putting the page on the list now as opposed
to when I feel like I'm done documenting everything in full ;-)
Patrick Boutilier schreef:
On 09/14/2010 07:51 AM, Paul van der Vlis wrote:
Hello,
Strange problem:
-
Sep 14 09:18:12 mail cyrus/imap[21928]: TLS server engine: cannot load
CA data
Sep 14 09:18:12 mail cyrus/imap[21928]: unable to get certificate from
On 09/14/2010 08:53 AM, Bron Gondwana wrote:
With the new replication engine in 2.4, it will be possible - deleted
messages still get replicated for a week - and if you set an explicit
long expiry time on the replica (say, years!) then it wouldn't get
cleaned up any earlier.
That sounds like
Dear Dan,
If you're not concerned about your quota database, seen state, annotations,
and subscription information, and assuming you've already regenerated your
top level mailbox hierarchy, then you should be able to copy over the
individual email files from each mailbox to the new server and
We did a migration some months back from an old Kolab v1 (cyrus v2.1)
system to a new Kolab v2.2 (cyrus v2.2) system.
This was done by writing a script to
- dump the ldap database (you might not have this) and load it on the new
system
- rsync the mailboxes from their location on
On 14/09/10 22:41 +0530, Shuvam Misra wrote:
What other meta-data files other than mailboxes.db do I need to copy if
I want to restore everything (seen flags, other flags, etc)? And will it
be a generally good practice to convert all required database files to
flat first, then re-convert to the
On Tue, 14 Sep 2010, Derek Chen-Becker wrote:
On 09/14/2010 08:53 AM, Bron Gondwana wrote:
With the new replication engine in 2.4, it will be possible - deleted
messages still get replicated for a week - and if you set an explicit
long expiry time on the replica (say, years!) then it
On 09/12/2010 09:10 AM, Gavin McCullagh wrote:
The goal is to have a PDF library available at any time, with basic file
search on document/message name, so a file share doesn't solve my problem
(and I don't want any document management system, I just want access to
files).
I don't imagine
Hello,
I am having trouble converting a quota skiplist db back to quotalegacy
format (I know... this is probably not the most common Cyrus operation :-)
% cvt_cyrusdb /ssd/cyrs/imap/quotas.db skiplist /ssd/cyrs/imap/quota quotalegacy
Converting from /ssd/cyrs/imap/quotas.db (skiplist) to
Dear Dan,
See the manpage for imapd.conf for possible formats, but for my 2.3.12
installation, with configdirectory specified at /var/lib/cyrus (and no
customization to my *_db options), my database files are:
Got it. Thanks a lot for the details.
/var/lib/cyrus/annotations.db
What are
With the new replication engine in 2.4, it will be possible - deleted
messages still get replicated for a week - and if you set an explicit
long expiry time on the replica (say, years!) then it wouldn't get
cleaned up any earlier.
That sounds like it's what we want, so I'll plan
How difficult or easy would it be to modify Cyrus to strip all
attachments from emails and store them separately in files? In the
message file, replace the attachment with a special tag which will point
to the attachment file. Whenever the message is fetched for any reason,
the original
How difficult or easy would it be to modify Cyrus to strip all
attachments from emails and store them separately in files? In the
message file, replace the attachment with a special tag which will point
to the attachment file. Whenever the message is fetched for any reason,
the original
On Wed, Sep 15, 2010 at 12:13:03PM +1000, Rob Mueller wrote:
How difficult or easy would it be to modify Cyrus to strip all
attachments from emails and store them separately in files? In the
message file, replace the attachment with a special tag which will point
to the attachment file.
Dear Rob,
I had reservations about some of these things too. :( In particular,
I was wondering about having to remember and recreate the exact
transfer-encoding. If both of us forward the same attachment in two
emails, and one encodes in quoted-printable, the other in base64, Cyrus
had better be
Dear Bron,
http://www.newegg.com/Product/Product.aspx?Item=N82E16822148413
2TB - US $109.
Don't want to nit-pick here, but the effective price we pay is about
ten times this. To set up a mail server with a few TB of disk space,
we usually land up deploying a separate chassis with RAID
On 15/09/10 06:46 +0530, Shuvam Misra wrote:
What are annotations?
Annotations are defined in RFC 5257.
They allow an admin to add metadata to a mailbox (or the server). The
cyradm utility sets annotations with its internal info, mboxcfg, and
setinfo commands.
/var/lib/cyrus/tls_sessions.db
A 500-user company can easily acquire an email archive of 2-5TB. I don't
care how much the IO load of that archive server increases, but I'd like
to reduce disk space utilisation. If the customer can stick to 2TB of
It would be interesting to measure the amount of duplication that is going
26 matches
Mail list logo
