Click here to Skip to main content
15,893,508 members
Articles / Outlook

Sending an executable file via Outlook

Rate me:
Please Sign up or sign in to vote.
4.00/5 (1 vote)
24 Dec 2010CPOL 7.2K   1  
I've renamed files to *.ex_ and they seem to be accepted by Outlook. As a last resort, I zip the *.ex_ and then send the zip. The same thing happens with *.msi (renamed to *.ms_) and other files recognized as containing executables.

Alternatives

Members may post updates or alternatives to this current article in order to show different approaches or add new features.

Please Sign up or sign in to vote.
21 Dec 2010David Crow 5 alternatives  
Please Sign up or sign in to vote.
6 Jan 2011GPUToaster™
Just password protect the zip files. Note that even gmail filter outs the .exe files. Password protecting the zip files can be passed through outlook.
Please Sign up or sign in to vote.
24 Dec 2010maq_rohit
One more thing... You can try to send executable file by remaining extension to .doc. I don't know why this will not be blocked by Outlook. But you can try it for any EXE to convert extension to .doc.
Please Sign up or sign in to vote.
5 Jan 2011Tieske8
Outlook blocks certain files it finds to be dangerous. There has been plenty written about that. What the server stops from passing, either exchange, lotus notes or any firewall directly examining SMTP protocols on the wire for example, is a whole different story.I wrote some VBA code to...
Please Sign up or sign in to vote.
5 Aug 2011Robin Imrie
For the past 18 months I have been using You send it. This service will allow you to upload your file to their server where is will remain for x days or y downloads, and you send a download link.The whole procedure is simplified by installing the you send it plugin for outlook, with this...

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Engineer Comport Computing
United States United States
I am a software developer specializing in technical and numerical software systems and also a PhD Petroleum Engineer.
I started programming in IBM 1620 machine code in 1967, then FORTAN on CDC mainframes mainframes in 1970. I later used ALGOL, BASIC, FORTH, Pascal,Prolog, C, F#, C#, etc.
I generally use whatever language available thatallows me to accomplish what is neccesary.

Comments and Discussions