| 1 |
On August 11, 2016 7:51:29 AM GMT+02:00, Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 2 |
>On Wednesday 10 Aug 2016 19:26:56 Mick wrote: |
| 3 |
> |
| 4 |
>> Peter, I recall you being a long term sufferer of Kmail2 problems, |
| 5 |
>which I |
| 6 |
>> do not experience here. |
| 7 |
> |
| 8 |
>Yes, I have some old archives preserved as tar.bz2 files, but I can't |
| 9 |
>import |
| 10 |
>them into KMail because of some internal damage to many of the |
| 11 |
>messages. I |
| 12 |
>think the damage was caused by a gradually developing hardware problem |
| 13 |
>(which has eventually forced me into replacing the whole box), and |
| 14 |
>KMail, |
| 15 |
>akonadi and friends can't handle the mess. They aren't what I would |
| 16 |
>call |
| 17 |
>defensively programmed. They either throw wobblers or refuse to |
| 18 |
>co-operate |
| 19 |
>at all. |
| 20 |
> |
| 21 |
>So I have the basic data and can use standard tools to examine them if |
| 22 |
>necessary; that will have to do for now. Meanwhile, KMail is working |
| 23 |
>happily |
| 24 |
>with stuff originating on the new box - apart from the apparently |
| 25 |
>inevitable |
| 26 |
>duplicate messages of course. |
| 27 |
> |
| 28 |
>> Have you tried running a stand alone SQL? I am running postgresql |
| 29 |
>and |
| 30 |
>> things have been quite uneventful since I made the switch. |
| 31 |
> |
| 32 |
>Is there some documentation on how to do that? I doubt it would help me |
| 33 |
> |
| 34 |
>because the problem smells like higher up the stack, but you never |
| 35 |
>know... |
| 36 |
|
| 37 |
For a howto, check archives on this list for this year. I should really write it all down into a howto. But as with many things, there is not enough time. |
| 38 |
|
| 39 |
-- |
| 40 |
Joost |
| 41 |
-- |
| 42 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Archives