On Sat, Sep 3, 2011 at 4:50 AM, Anne Wilson <cannewil...@googlemail.com> wrote:
> No, you are misunderstanding what I have said. If you look using a file
> manager, you will see the directory the report mentions.
This is the first time I recall you mentioning use of a "file manager".
On Aug. 31 you said: "Those are (empty) directories, created by KMail.
" referring to
"/home/anne/.kde/share/apps/kmail/imap/.1687036093.directory/.INBOX.directory/Newsletters:"
and one other.
Then on Sep 1 you said: "ls: cannot access
/home/anne/.kde/share/apps/kmail/imap/.1687036093.directory/.INBOX.directory/Newsletters:
No such file or directory"
and
"Since these folders are created by KMail, I assume they act as some sort of
pointer but I can't see any clue as to exactly what they are."
> Try doing that in a
> terminal, and where you get beyond .kde/share/apps/kmail/imap you start
> getting "No such file or directory".
So you are saying that a file manager and a command line shell are
returning different information? That implies that you are running
each with different rights (as a different user or as part of
different groups).
Or that the file manager has something cached that no longer exists.
Did you try asking the file manager to refesh it's view of the
directory?
If you are logged in as root and the filesystems are all local, you
should be able to see everything via the shell.
> They appear to be virtual directories and
> files of some sort, related to the files in ~/Maildir.
There are a limited number of ways to have "virtual directories" in
Unix-like OSes, all of which will show up via a shell just as much as
via a file manager.
> 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.
If KMail is using MBox format to store local copies of the IMAP
messages, then they (the messages) will not be in directories, but in
one file per IMAP folder (not one directory per folder and one message
per file, that would be MDir format). I do not know the workings of
KMail, so I do not know if this is the case, but it would explain the
path that ClamAV is reporting.
> 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.
And you did not share that knowledge, such as "I can see directory X
but when I try to look at directory X/Y ls cannot list it" would have
gone a long way to clarify what you were doing.
> 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.
Then you need to dig into how KMail manages it's local copies of IMAP 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.
--
{--------1---------2---------3---------4---------5---------6---------7---------}
Paul Kraus
-> Senior Systems Architect, Garnet River ( http://www.garnetriver.com/ )
-> Sound Designer: Frankenstein, A New Musical
(http://www.facebook.com/event.php?eid=123170297765140)
-> Sound Coordinator, Schenectady Light Opera Company (
http://www.sloctheater.org/ )
-> Technical Advisor, RPI Players
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
