File: o-otherdatabases.rst.txt

package info (click to toggle)
cyrus-imapd 3.10.0~beta1-3
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 86,332 kB
  • sloc: ansic: 284,810; perl: 135,824; javascript: 9,562; sh: 5,728; yacc: 2,565; cpp: 2,147; makefile: 2,133; lex: 662; xml: 621; awk: 303; python: 279; asm: 262
file content (20 lines) | stat: -rw-r--r-- 1,029 bytes parent folder | download | duplicates (18)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Can I use MySQL (or another SQL database) as the primary mail store?
--------------------------------------------------------------------

Using a database as the main message store for Cyrus is not currently 
supported. According to discussions on the mailing list, there is little 
benefit in adding such support (given typical IMAP access patterns, 
optimizations in the current mail store that make it fast, and the 
amount of effort involved to retrofit a different mailstore into the 
backend), so it's unlikely to ever be written. 

The Cyrus mail store is a normal directory tree, with mailboxes stored 
as directories and messages stored as individual files. Some additional 
information, eg index data, is kept in the "cyrus.*" files in the 
mailboxes. 

Cyrus DOES have the option of using databases of various types for 
storing some other information, such as authentication data, mailbox 
lists, etc. There may be reasons to add a SQL backend to these databases 
in the future (in addition to flat, and skiplist).