M
mike hotel
Greetings,
I was sent a .webloc (a text/xml file) attachment and received it in the
newly installed Entourage 2008. Entourage blocked the attachment with
the "friendly" note "Entourage has blocked the following potentially
unsafe attachments: [name] <Remove them> <Learn more...>"
The "Learn more..." option provides the following.
<being Help>
Cause: For security reasons, Entourage blocks attachments that could
potentially harm your computer.
Solution: If you do not trust that the attachment is safe, delete it
from your computer.
Solution: If you trust the message sender and want to receive the
attachment, ask the sender to compress the file and then send it to you
again.
<end Help>
It seems to me that this is not a reasonable procedure for handling this
situation. Entourage should warn me there might be a risk, but it should
not unilaterally strip the file off and tell me later to tell the sender
to resend. In fact if the file were malware it could be just as risky
when unzipped as when it is uncompressed. So the stripping and warning
serve only to annoy the user.
It looks like we are stuck with this situation and I imagine there is
nothing you can do about it. I just wanted to make this visible
complaint.
I was sent a .webloc (a text/xml file) attachment and received it in the
newly installed Entourage 2008. Entourage blocked the attachment with
the "friendly" note "Entourage has blocked the following potentially
unsafe attachments: [name] <Remove them> <Learn more...>"
The "Learn more..." option provides the following.
<being Help>
Cause: For security reasons, Entourage blocks attachments that could
potentially harm your computer.
Solution: If you do not trust that the attachment is safe, delete it
from your computer.
Solution: If you trust the message sender and want to receive the
attachment, ask the sender to compress the file and then send it to you
again.
<end Help>
It seems to me that this is not a reasonable procedure for handling this
situation. Entourage should warn me there might be a risk, but it should
not unilaterally strip the file off and tell me later to tell the sender
to resend. In fact if the file were malware it could be just as risky
when unzipped as when it is uncompressed. So the stripping and warning
serve only to annoy the user.
It looks like we are stuck with this situation and I imagine there is
nothing you can do about it. I just wanted to make this visible
complaint.