On Monday 22 February 2016 04:15:02 Lisi Reisz wrote: > On Monday 22 February 2016 00:05:41 Gene Heskett wrote: > > On Sunday 21 February 2016 15:39:57 Thierry de Coulon wrote: > > > On Sunday 21 February 2016 01.41:18 Glen Cunningham wrote: > > > > Reply to my own post for the archives. > > > > > > > > On Sunday 21 February 2016 09:38:25 Glen Cunningham wrote: > > > > > Thanks for the try, Nik, > > > > > > > > > > On Sunday 21 February 2016 03:39:15 Dr. Nikolaus Klepp wrote: > > > > > > Hi! > > > > > > > > > > > > It's that simple :-) > > > > > > > > > > NO! It is not that simple. > > > > > > (...) > > > > > > > Laboriously copied the above 6 files/directories from .kde3 on > > > > the old box to .trinity on the new one. > > > > That did not work! Kmail failed to start. > > > > Deleted the 5 config files, restarted kmail, at least kmail > > > > started this time and my old mailboxes seem to have survived. > > > > > > > > There has gotta be a better way! > > > > Cheers, > > > > Glen > > > > > > It should - almost - work the way Nik indicated. > > > > > > There are possibly a few things to edit when you move to .trinity > > > (but that will be only once). Mainly, did you edit > > > /.trinity/share/config/kmailrc ? In the last part of the file > > > (after the mailboxes), you have the path to your mail directory. > > > > > > In (very) old time this would have been ~/mail , but somwhere in > > > KDE history it was relocated to a ./kde3 subdirectory, usually > > > $HOME/.kde3/share/apps/kmail/mail. You must change that to > > > $HOME/.trinity/share/apps/kmail/mail > > > > > > As far as I remember that's all I had to do (apart from copyinf > > > the directory). > > > > > > Thierry > > > > That might not be 100% good info, here on a wheezy system, its > > ~/Mail, and I can't remember when it was different. > > Sorry, Gene - this is the not 100% correct information. You have not > got a standard Wheezy system by any manner of means. It was possible > to keep mail in ~/Mail. which is where it was before, but only by > deliberately hacking one's system. It is NOT where it is on a standard > Wheezy/TDE system. E.g., it is not on mine. I migrated my mails, > with help from the community, I did not hack and set up links or > whatever in order to keep ~/Mail, although that was a possibility. > ISTR that I tried and made a mess of it. > > Lisi I didn't "hack" anything to put it there, Lisi. Thats where my first EMC2 install put it, from one of Paul Conners Brain Dead Installers 15 years ago put it, that is where the Lucid 8.04 LTS install put it, thats where the Hardy 10.04 LTS install put it and thats where the install iso based on Wheezy put it. All I had to do was copy the email corpus from the old drive to the new one each time I made a new install on a new drive. Sure I write scripts to take care of stuff the installer should have taken care of but didn't, and cannot because the choices would exceed the size of the dvd. All I am doing is scrattching an itch. To me its not hacking, its polishing the apple. I don't build/buy these machines to be told how I have to conform to them, particularly if the job is only being half-assedly done, and email is one of those things where there simply is no way to satisfy any of the people even 50% of the time. It can't be done, so I make them conform to me. If I have a function I need to do, then I might install something, but except for my scripts, and of course amanda for backups, even that is wrapped in my own helper scripts because it puts a bare metal recovery capability at my finger tips. If the main drive in this machine died in the next hour, its a trip to town to get a fresh drive, install from the same cd on it, install or build amanda, and once its running, I can have this system fully restored to its state as of 3 hours ago, and will only have lost those emails that have come in since the backup, and will be back to 100% normal operation by noon if I don't go back to bed. Which I am going to do as I'm up way to early for me. To you, even changing a password is hacking I guess. But to make a machine do something it is fully capable of doing, even if its not on the menu at your favorite "greasy spoon"/"distribution" is not hacking, its making the machine do what I need it to do AND bought it or built it to do. I think you need to find a better word than "hacking". Its usually called programming. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>