Sorry, Sven, there was a misunderstanding here. All your points are
perfectly reasonable. The way your last message read might have been
misunderstood by more people than just me, and might have given a wrong
impression of Entourage which you didn't intend at all, and weren't aware
of, but might make people afraid to using Entourage when they needn't be..
What you are actually saying here makes perfect sense.
On 9/13/01 3:01 AM, "Sven Ryen" <[EMAIL PROTECTED]> wrote:
> On 13.09.2001 02:41, "Paul Berkowitz" <[EMAIL PROTECTED]> wrote:
>
>> Why do you doubt it?
>
> What I meant was "I really doubt _the contents of_ the message caused the
> corruption." Should the sender resend the message, I doubt it'll end up
> unreadable again. Do you really think something inside the message confused
> Entourage and caused data corruption? This seems very unlikely to me. Should
> this be the case, the message will be on its way for inspection by
> Microsoft...
You're almost certainly correct that the contents of the message did not
cause the corruption. (If there were an attachment, that would be a
different matter.) Here we are agreed 100%, and I simply understood you to
mean "the message as it arrived on your computer", rather than the content.
As far as message content goes, you are right that it would be almost
impossible to cause corruption . But it is possible that something in the
way the sender's email program constructed the message has made it corrupt
already when it left his computer. That's why I suggested that you ask him
or her to copy and paste the contents into a new message rather than resend
the original, even though this scenario may be less likely than others.
>
>> It happens frequently that messages corrupt the
>> database.
>
> "frequently" must be a relative term. This has only happened once to me.
Yes, I did not mean that it happened frequently, if ever, to individual
users but rather that, in reports here and elsewhere when there are known
cases of corruption, corrupted messages account for a significant
_proportion_ of the total number of these cases. I.e., we have certainly
heard of it happening several times before now. This was my imprecision not
to have made this clearer.
>
>> Do you think the excellent rebuilder just arbitrarily
>> deletes any old thing?
>
> No, I'm perfectly aware that it'll delete unreadable messages when
> rebuilding. And yes, I agree that the the rebuilder did an excellent job.
>
>> If the problem is that you did not notice who the sender was, or have no
>> idea which message got deleted, then try that utility which checks the
>> server if your message is still on the server.
>
> The message is not still on the server, and as I said previously, I will
> contact the sender of said message and have him resubmit it. I don't really
> see how you can conclude that the format of the message caused corruption,
> as I have indications that a background app caused the crash while Entourage
> was saving the message to disk, then after restart, the message was
> unreadable.
That sounds extremely likely. If there was some sort of crash as messages
were downloading, that would be the most likely of corruption. And since you
know you the sender is, great! maybe you have had it resent already by now?
>
> I was simply looking for help here, in case anybody knew of a trick to
> somehow reach the contents of the message, but instead, I'm met with a
> hostile attitude, and people trying to be ironic and making fun of my
> messages. That's not my idea of a helpful community. I'll be looking for the
> unsubscribe address now...
That would be a shame. I think you'll find that there are a lot of helpful
people here, even if you don't find me to be one of them. Like all mailing
lists, it is a public venue, so things everyone says can have a wider
repercussion than in a private conversation. The reason I took offence on
Entourage's behalf is that since you hadn't made clear that you were
referring just to the _contents_ of a message, people might well have
concluded that you meant received messages in any shape or form (as I did),
and that therefore the cause must be Entourage acting up irresponsibly and
arbitrarily. You didn't intend that meaning, so that's fine. Thank you very
much for making that clear now.
>
>> If you no longer have
>> the message on the server, then you've lost it, but saved several thousand
>> other messages by doing so.
>
> I'll have the sender resend the original, if the message is still
> unreachable when saved to the database, I will submit it to Microsoft to
> have it inspected, in order to help prevent corruption in similar cases.
>
MS can't prevent background crashes in other applications from happening,
nor can they prevent background crashes from interfering with internet
events that are taking place at the time. So I'm not sure they'll be able to
do too much with your evidence. In OS X there should be a lot less of this
sort of thing taking place, we're told, so maybe Office 10, when it is
released, will be more protected from this particular sort of corruption
occurring.
--
Paul Berkowitz
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
