On Saturday 03 Sep 2011 Paul Kraus wrote: > On Fri, Sep 2, 2011 at 11:37 AM, Anne Wilson <cannewil...@googlemail.com> wrote: > > No. As I reported yesterday, that returns > > > > ls: cannot access > > /home/anne/.kde/share/apps/kmail/imap/.1687036093.directory/.INBOX.direct > > ory/Newsletters: No such file or directory > > Anne, > Typical troubleshooting something like this (a problem is reported > in a certain file or directory that you cannot later find) involves > walking the *entire* path, starting at the root (/) and seeing where > the trail ends. For example, start with: > > cd /home/anne/.kde > ls > and see what is there, does "share" exist, if so then > cd share > ls > and see if "apps" exists, if it does then > cd apps > ls > ... until you get to the point where the path component you are > looking for does NOT exist. The question then becomes why did it exist > in the past and it does not now. Perhaps you will find a similar > directory with a different number at the beginning. Perhaps the > application changes that number as part of the revision control > sequence on it's data. > > Just saying that ClamAV is reporting finding things in files that do > not exist is not a terribly helpful statement.
No, you are misunderstanding what I have said. If you look using a file manager, you will see the directory the report mentions. Try doing that in a terminal, and where you get beyond .kde/share/apps/kmail/imap you start getting "No such file or directory". They appear to be virtual directories and files of some sort, related to the files in ~/Maildir. Interestingly, if you look in Dolphin at the properties of first directory that bash says doesn't exist it says that it is 101.4 MB in 529 files, 141 sub-folders. I don't understand exactly how this is working, but once I had realised that, I could trace the directories within Maildir - the snag being that because ClamAV is pointing to the "virtual directory" it isn't indicating which mail message contains the problem. The whole explanation of this has only become apparent as I have dug deeper. Of course I first explored using your method - that was when I first came across this "No such file or directory" statement. At no point have I intended this to be a criticism of ClamAV - apart from the fact that it can't deal with this particular situation very well. It's probably not fair to expect it to either. I wanted some helpful hints as to how to find the offending messages. There has been some useful information about SaneSecurity which I had not previously known, but I'm still no nearer finding the offending messages, and it doesn't look as though I will be able to. I'll use the weekend to consider my options here - I don't want to erase a whole directory of messages for one that is merely spam in the eyes of SaneSecurity, so I may have to simply ignore the two remaining messages. Anne
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
