| 1 |
white-guest |
110 |
Template: cyrus22-common/warnbackendchange |
| 2 |
white-guest |
10 |
Type: note |
| 3 |
|
|
_Description: Database backends have changed! |
| 4 |
white-guest |
110 |
Comparation between /usr/lib/cyrus/cyrus-db-types.txt and |
| 5 |
white-guest |
10 |
/usr/lib/cyrus/cyrus-db-types.active shows that database backends for |
| 6 |
|
|
Cyrus IMAPd have been changed. |
| 7 |
|
|
. |
| 8 |
|
|
This means that those databases for which the database backends changed |
| 9 |
|
|
might need to be converted manually to the new format, using the |
| 10 |
|
|
cvt_cyrusdb(8) utility. |
| 11 |
|
|
. |
| 12 |
white-guest |
110 |
Please refer to /usr/share/doc/cyrus22-common/README.Debian.database |
| 13 |
white-guest |
10 |
for more information. Do not start cyrmaster until you have converted |
| 14 |
|
|
the databases to the new format. |
| 15 |
|
|
|
| 16 |
white-guest |
110 |
Template: cyrus22-common/removespools |
| 17 |
white-guest |
10 |
Type: boolean |
| 18 |
|
|
Default: false |
| 19 |
|
|
_Description: Remove the Cyrus spools, and user sieve scripts? |
| 20 |
|
|
Should I remove the Cyrus mail and news spools, as well as the user's |
| 21 |
|
|
sieve scripts, when the package is purged ? |
| 22 |
|
|
. |
| 23 |
|
|
This question only applies to the default spools and sieve script |
| 24 |
|
|
directories in /var. If you modified their location in imapd.conf, the |
| 25 |
|
|
new locations will not be removed; just the old ones in /var. |
Parent Directory
| 
Revision Log