Kolab2

[Bernhard Reiter]

On Friday 10 December 2004 04:36, Bradley Alexander wrote:
> 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.

Envelope and from  has to match for the mail domian that Kolab
maintains.

> 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.)

No.

> 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?


As far as I know this is the right way.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2145 bytes
Desc: signature
URL: <http://lists.kolab.org/pipermail/users/attachments/20041210/09ccc7ab/attachment.p7s>