Kolab2

Bradley Alexander storm at tux.org
Fri Dec 10 04:36:23 CET 2004


I just had to do a forced upgrade on my kolab installation from 20041122 to 
20041201. Last week I upgraded from 20040809-full to 20041122, and realized 
that kolab was bouncing mail to my server. (I have tux.org forwarding my mail 
to my internal domain.) As far as I can tell, it was because I used just the 
hostname for my mailserver instead of the FQDN as I had before.

In trying to get it working, I changed the myhostname entry 
in /kolab/etc/postfix/main.cf. when I restarted kolab, my imapd store 
-disappeared-...Anybody know why this happened? (Luckily, I backed up my 
entire kolab installation before I upgraded to 20041122, so I only lost a 
week's mail.)

Unfortunately, I was at work ssh'ed into the mailserver when this happened. 
Also, in backing up the imap store, should the entire /kolab/var/imapd 
directory tree, or is there a more elegant way to do it?

Thanks,
-- 
--Brad
========================================================================
Bradley M. Alexander                       |
IA Analyst, SysAdmin, Security Engineer    |   storm [at] tux.org
Debian/GNU Linux Developer                 |   storm [at] debian.org
========================================================================
Key fingerprints:
DSA 0x54434E65: 37F6 BCA6 621D 920C E02E  E3C8 73B2 C019 5443 4E65
RSA 0xC3BCBA91: 3F 0E 26 C1 90 14 AD 0A  C8 9C F0 93 75 A0 01 34
========================================================================
There are three simple rules for making a smooth landing.
Unfortunately no one knows what they are.
     --Rules of the Air, #15




More information about the users mailing list