Unsolved
This post is more than 5 years old
7 Posts
0
11545
October 13th, 2008 23:00
Cannot Send Attachments in Outlook Express or IncrediMail Program
I have a Dimension 3000 Desktop, running Windows XP Home Edition. I am using Outlook Express 6, and IncrediMail Program for sending e-mail..
I tried to send a Screen Saver(in both e-mail programs) with an .exe file extension, to two recepients.
Both Recepients are using Outlook Express 6 for their e-mail programs. When they received my Screen Saver, one of the recepients Outlook Express removed the attachment with no explanation...the other recepient, did not receive the Screen Saver. The E-mail was returned to me with the following explanation:
Hi, This is the qmail-send program at trueband.net.
I'm afraid I wasn't able to deliver your message to the following addresses. This a permanant error.
Our system detected an illegal attachment on your message. Please visit http://mail.google.com/support/bin/answer.py?answer=6590.
When I went to the above web site it said as a security measure Gmail doesn't allow you to send or receive files ending in .exe that could contain damaging executable code.
Neither of the recepients uses Gmail, nor do I...how does their message have any relationship to my problem??? Why can't the two recepients open this Screen Saver Attachment..
Any help appreciated..
Dean Reed
mombodog
2 Intern
•
12.7K Posts
0
October 13th, 2008 23:00
2 ways to remedy this
1. Use a zip or winrar utility that allows password protection and "mask" file names, zip the exe file with password protection and file names are masked.
2. Change the file extension of the screen saver to screensaver.yyy then instruct the recipient to rename the extension to screensaver.exe after they receive it.
Raptor 1
3 Posts
0
October 14th, 2008 20:00
Larry R
2 Intern
•
1.7K Posts
0
October 14th, 2008 21:00
A lot of email servers with anti-virus packages automatically block executable files as attachements because there is really no way to be sure, unless you know the person sending you the file (and even then, you can't be positive), that the file itself is not 'bad'.
The method I used on those occasions I had to send a customer a Dell driver was to append .not to the end of the filename, with instructions to rename the file after it had been saved to the recipients hard drive. For example, if I was sending R123455.exe I would change the name to R123455.exe.not and then attach it to the email. Once they get the file, all they need to do is rename it back to R123455.exe and it should work just fine.
The other options people have listed work just as well, but may (or may not) be more 'complicated' to implement.