On 9/21/04 9:40 AM, "Bryan R Harris" <[EMAIL PROTECTED]> wrote:
>
>
> Oh, Allen, just reading this I get a pit down in my stomach. I'd really
> hate to lose a bunch of messages, especially if I don't know which ones they
> are.
>
I only lost the two or three that were invisible...the rest all exported
okay, and imported into my new identity. You can be sure that the developers
are working for fixes both to correct and to prevent this problem. They have
sample databases and have isolated the problem, so it's only a matter of
time. I'd say, if you can hold out, hold out. I went for months with a few
invisible messages that migrated from place to place, disappearing for days
at a time after I did a rebuild, only to crop up again a few days later. I
rebuilt once or twice a week. Since I archive regularly and keep mostly
messages two weeks or less old, my database only weighs in at 44 MB, so the
rebuilds were quick.
I just got impatient when the invisibles showed up in my junk mail folder so
that I couldn't purge it automatically, and stayed there after a rebuild. I
never realized how big a chore transferring to a new identity would be. The
intent of my message was not to give anyone knots in their stomach, it was
meant to advise patience, and to warn people that the only available cure
might be worse than the disease. Better to wait for the _real_ fix.
> Out of curiosity, do you ever use a script to mark all as read? I'm
> thinking my corruption seems to correspond to having just run a script that
> does that...
>
> Wishing I hadn't upgraded to '04.
>
I very much doubt your script would cause this problem. It could _uncover_
it, because pretty much any script that accesses properties of all, or a
large portion, of your messages can discover the problem when it hits one of
these invisible messages.
> - B
>
> ps. Here's the script I run... Do you have anything similar?
>
> As a side note, this doesn't always work with 'rage '04. It seems to work
> on all the subfolders of the inbox except my "macos x" folder. On that one,
> it doesn't mark them all as read, it just goes to the next folder.
>
My guess is that that folder is meeting this test when you don't expect it
to:
if theFldrs does not contain {myFldr} then
Do any of the other folders have a space in its name?
>
> **************************************
> tell application "Microsoft Entourage"
>
> set theFldrs to every folder of in box folder
> set N to count of theFldrs
> set myFldr to displayed feature of main window
>
> set found to false
> set i to 1
>
> if theFldrs does not contain {myFldr} then
> set found to true
> else
> try
> set read status of (every message of myFldr whose read status is
> untouched) to read
> end try
> end if
>
> repeat while not found
> if item i of theFldrs is myFldr then set found to true
> set i to i + 1
> if i > N then
> set displayed feature of main window to in box folder
> return
> end if
> end repeat
>
> set found to false
>
> repeat while not found
> if unread message count of item i of theFldrs > 0 then
> set found to true
> else
> set i to i + 1
> if i > N then
> set displayed feature of main window to in box folder
> return
> end if
> end if
> end repeat
>
> set displayed feature of main window to (item i of theFldrs)
>
> end tell
> **************************************
--
To unsubscribe:
<mailto:[EMAIL PROTECTED]>
archives:
<http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/>
old-archive:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
