TIP: Click on subject to list as thread! ANSI
echo: nthelp
to: Geo
from: Ellen K.
date: 2005-02-05 23:31:42
subject: Re: safe vs. unsafe

From: Ellen K. 

In Agent it also does.

I don't mind when the rename is accurate.

On Sat, 5 Feb 2005 04:56:11 -0500, "Geo" 
wrote in message :

>Rich,
>
>don't we have a policy or something that prevents renaming threads with titles
that represent the subject? 
>
>I'm not sure why but when you do this it breaks it into a new thread in my OE
(I sort by subject).
>
>Geo.
>  "Rich"  wrote in message news:42048f95$1{at}w3.nls.net...
>     Nope.  The extension controls the action taken when the user opens or
runs the attachment which determines whether or not it is safe.  Being
unsafe doesn't imply something undesirable will happen only that something
undesirable may happen.
>
>     Now I may be assuming too much of you.  Nothing is safe from someone
determined.  If someone sent you a text file with the source code for a
trojan, you could very well save this, build, and run the resulting trojan
even though a text file is considered safe.
>
>  Rich
>
>    "Mike '/m'"  wrote in message
news:k3s70153e3tkvs6prmst408kh53p5bo5j7{at}4ax.com...
>
>    It is the content, not the extension, that determines whether or not a
file is
>    safe.
>
>      /m
>
>    On Thu, 3 Feb 2005 17:34:44 -0800, "Rich"  wrote:
>
>    >   What everyone I know does if they need to send unsafe files by email
is to rename them to have a "safe" extension and to send that. 
The recipient saves it and renames it back.
>    >
>    >   There are administrator controls but this comes up so rarely I can't
remember when the last person asked.
>    >
>    >Rich

--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
SEEN-BY: 633/267 270 5030/786
@PATH: 379/45 1 106/2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.