mmattson said:
more intensive option: both you and person you are
sending to need to change .exe from a type 1 extension
in outlook (won't even let you see that attachment) to a
type 2 attachment (you have to save it before opening).
There is some good info about this on microsoft's website
(changing outlook security settings) you create an
outlook.reg file that changes the extensions security. If
either of you runs a global.reg file at logon you can
just add this to your global.reg file and then change it
back to the original file (b/c .exe files should probably
be disallowed on regular basis becuase of virus issues).
[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0
\Outlook\Security]
"Level1Remove"=".adp;.bas;.exe;.inf;.lnk;.mdb;.msi;.reg;.s
cr;.url;.vbs"
you can add/remove the extensions as your company sees
fit.
hope this helps.
-----Original Message-----
I need to send exe files with the extension .exe
__________________________________________________________
__ __________________________________________________________
__
.
Since you can not enforce recipients to remove certain extensions from
the Level 1 list (unless you have physical access to them and/or their
computer and are willing to assault them and/or their computer to
enforce the change), do NOT assume the recipient will do is handy for
you as the sender. Simply circumvent the built-in security that
Microsoft added which is based solely on the extension of the file.
If you demand that you send .exe files as .exe extensions then realize
that you are likely to be viewed as a spammer, spyware proliferator, or
virus author or proliferator. You should be willing to rename your file
so the recipient doesn't accidentally execute it, from something like
myfile.exe to myfile.exx or myfile.exe.txt. If you are sending e-mails
with attachments to a destination that automatically receives the file
then it should be real easy to simply parse and strip an appended
extension or rename the extension back to .exe. Also, why are you using
e-mail to transfer files whether executable or not? E-mail servers are
throttled down and getting a file via e-mail is the slowest way to get
it online. Most recipients find it a real pain in the ass to receive
e-mails with large attachments, and even more so when they are
executables, since they have to wait for the slower transfer of a huge
attachment before they can even start downloading their other e-mails.
And forget about any resume capability when using e-mail to transfer
files. Put the file on your web site (you can get free ones) and put a
link to it in your e-mail. Your ISP may even have a file area where you
can save files (without having to setup a dummy web site just to have a
file structure in which you can save files). SMTP for e-mail is a
*messaging* venue. It is NOT intended to be a file transfer venue.
It's okay in a pinch as long as it isn't too big and doesn't exceed any
sender's or recipient's mailbox quota, and no recipient is going to
bitch in a one-time case on having to rename a file extension back to
..exe. Demanding that the extension be .exe means Randy has an ulterior
motive for sending this executable and for which he doesn't want to
protect his recipients.
If anyone, even my friends, refused to rename .exe attachments to
something more benign they soon get put on my shit list. How many times
does your friend get to slap you in your face before you decide they are
no longer your friend and you avoid them? If the recipient is willing
to go through the exercise of accepting your attached file and to store
in on their drive, they certainly can go through the tiny bit of effort
to rename the extension. And if you want to be sure they know what to
rename it back to then simply tell them in your e-mail.