Laine Houghton wrote:
<heuser.marcus@freenet.de> wrote in message 1108750735.054375.95570@f14g2000cwb.googlegroups.com">news:1108750735.054375.95570@f14g2000cwb.googlegroups.com...I had an email bounced by a client's antiviral mailbot because it had a zip file attached, named blahblah.zipp, and one of the files inside it was a unix shell script that contained a series of files uuencoded as ASCII garble, one of those files would decode to blah.exe if the script were run. I was absolutely gobsmacked that the bot found that file under 3 levels of obfuscation.Sometimes you can fool the servers by double-zipping the files...I've been fooling them with various methods. They respond in kind.I suggested BINSCII because they should have no reason to fear ASCII characters. And I have a windows decoder. I could extend it to encode as well but if there is a hue and cry for this perhaps there should be some discussions on a header format to accomodate various systems.
I asked the script developer to rename the uuencoded file to blah (no file extension), then after it was reconstituted the script could then rename blah to blah.exe. I'm not working with that client now so I can't say if this change would work or not.
Martin