[Kde-pim] Need to find archived message

Jörg Schaible Joerg.Schaible at scalaris.com
Wed Aug 15 09:07:56 BST 2012


Hi Anne,

Anne Wilson wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 14/08/12 19:18, Kevin Krammer wrote:
>> On Tuesday, 2012-08-14, Anne Wilson wrote:
>>> On 13/08/12 08:57, Kevin Krammer wrote:
>>>> On Monday, 2012-08-13, Anne Wilson wrote:
>>>>> Some time ago some of my messages were deleted, in one of
>>>>> those accidents.  I know that they are backed up on a
>>>>> separate partition of my IMAP server, but opening thousands
>>>>> of messages, one by one, in kwrite is a daunting task.
>>>>> 
>>>>> Ideally I'll like to make an account in KMail that displays
>>>>> the messages in
>>>>> /mnt/server-name/Data2/Maildir/mailbox-name/cur - in fact the
>>>>> whole of the Data2 Mildir would be fine if that is easier.
>>>>> 
>>>>> Is that possible?
>>>> 
>>>> I am not sure if you can access all folders in one go, the
>>>> maildir resource assumes a certain directory structure for
>>>> subfolders.
>>>> 
>>>> You could try pointing a maildir resource to
>>>> /mnt/server-name/Data2/Maildir
>>>> 
>>>> One thing that should work from how the path looks like is to
>>>> access single folders, i.e. pointing a maildir resource to
>>>> /mnt/server-name/Data2/Maildir/mailbox-name
>>>> 
>>>> For additional safety during experiementation you could
>>>> consider mounting the server's export as read-only.
>>> 
>>> Possible complication - if I open the new resource and try to
>>> search for a message, it tells me that it can't search because
>>> the Nepomuk-something isn't available, and that I can activate it
>>> in SystemSettings.  It is activated, and searching other
>>> resources works fine, so does this mean that the read-only part
>>> is interfering with searching?  Not a huge deal, if that's so,
>>> because I can always backup the backup :-) then remove the
>>> read-only bit.
>> 
>> I doubt that the read-only character of the underlying file system
>> has any effect on the indexing. Check with Akonadiconsole that the
>> Nepomuk feeder agent is running and "online". Maybe remove and
>> re-add the maildir resource and list the folder content again.
>> 
>> The feeder agent should get notified about the new mails and start
>> to index them.
>> 
> Not really sure what I'm looking for, or where to look for it, Kevin.
> Akonadiconsole seems to have many tabs, almost all of them totally
> empty.  The Raw socket says "* OK Akonadi Almost IMAP Server [PROTOCOL
> 28] ".
> 
> Actually, as I dig deeper, there is something very strange here.  My
> search would not have found the message I wanted, because the mail
> folder in question is not listed.  When I looked at the properties I
> found that I was offered the top-level Maildir directory, cur, new,
> tmp and Inbox.Family.  I have no idea why Inbox.Family is different
> from any other subdirectory, but even that isn't enough.  Going back
> to reading mail, I realise that I'm really only seeing Inbox/cur - not
> even Family.  There is no possibility in the resource setup for
> connecting to the sub-folder I really need,
> /mnt/Data3/anne/Maildir/Inbox.Archives.

Maildirs seem to be not so standard as expected. Do you have a standard 
local Maildir resource? For me it points to "~/.local/shared/local-mail/". 
When I look into the file system, I can see that this folder has only the 
usual cur/new/tmp folders. However, all my subfolders are located in 
"~/.local/share/.local-mail.directory/" and their subfolders are again in 
subfolders that follow this naming pattern, e.g. "~/.local/share/.local-
mail.directory/.Projects.directory/", so you have something like:

=========== %< ==========
rootdir
+ Maildir
| + cur
| + new
| + tmp
+ .Maildir.directory
  + Sub
  | + cur
  | + new
  | + tmp
  + .Sub.directory
    + Sub2
    | + cur
    | + new
    | + tmp
    + .Sub2.directory
      + Sub3
        + cur
        + new
        + tmp
=========== %< ==========

However, I have the Maildir structure you're describing when I look into the 
file system of my Courier IMAP server (i.e. all folders are inthe same 
directory and the hierarchy is defined by the dots):

=========== %< ==========
rootdir
+ Maildir
  + cur
  + new
  + tmp
  + Sub
    + cur
    + new
    + tmp
  + Sub.Sub2
    + cur
    + new
    + tmp
  + Sub.Sub2.Sub3
    + cur
    + new
    + tmp
=========== %< ==========

Based on this information, it should be possible to convert the existing 
structure with a script into one that the Akonadi Maildir resource 
understands.

Cheers,
Jörg

_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/


More information about the kde-pim mailing list