Re: [Evolution] Snooping on a snoop ...
- From: Not Zed <notzed ximian com>
- To: Dan Winship <danw ximian com>
- Cc: Brian <brianb sboss com>, evolution ximian com
- Subject: Re: [Evolution] Snooping on a snoop ...
- Date: 09 Apr 2002 17:09:00 +0930
Presumably any full body files (not .HEADER) that were created at that
time are ones that were downloaded (i.e. viewed). The HEADER files are
downloaded as part of just building the list of messages.
Note that if you have filtering on new messages, they will be downloaded
anyway, in which case they wont tell you anything and it probably wont
help. (maybe the access time?)
On Mon, 2002-04-08 at 23:02, Dan Winship wrote:
When I considered this, I ssh'ed into my machine, did a 'killev;
oaf-slay'
Grumble. One of my pet peeves. "oaf-slay" does everything "killev" does
and more. So running "killev; oaf-slay" is *always* redundant. If you're
going to oaf-slay, don't bother to killev too.
and went looking in the evolution cache of the folder in
question. Doing an 'ls -lt | less' I see lots of files accessed at the
time in question, but only a few messages where the full headers were
pulled. My question is, how do I determine which messages were read
based off the contents of the cache?
By "only a few messages where the full headers were pulled", I assume
you mean "there are only a few #.HEADERS files". But that's expected.
Cyrus supports UIDPLUS, meaning Evo can reliably cache the complete
message body when it appends the message, and if it has the complete
message in the cache, it won't bother to cache the headers separately.
If every file that either has no extension or has a .HEADERS extension
was accessed, then that means evo had to regenerate the summary, and in
that case you're probably not going to be able to get any further info.
Otherwise, it seems to me that any file whose access time is in the
right range was probably looked at.
-- Dan
_______________________________________________
evolution maillist - evolution ximian com
http://lists.ximian.com/mailman/listinfo/evolution
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]