I sent a friend an email with an attached Zip file. It bounced, with a message from “System Administrator” that read
Your message did not reach some or all of the intended recipients.
Subject: xxxxxxxxxxxxxxxx
The following recipient(s) could not be reached: xxxxxxxxxxxxxxx …552 5.7.0 review our attachment guidelines. u14sm9443132gvf.20
I figured maybe the note is from my friend’s system – maybe the file was too large? So I resent it to him to another mail address, with the same outcome. Then it occurred to me to mail the file to myself… long story short, eventually I went to the source of all wisdom – ironically, Google – and discovered that Google Mail, through which I was sending, has a policy forbidding any zip file that contains an executable (which my attachment, quite lawfully, did).
So I sent the file via yousendit, and that was that. But it did occur to me that I would’ve saved a lot of time had Google Mail elected to phrase their bounce message in human-friendly informative terms, such as:
Your message did not reach some or all of the intended recipients.
- – -It was blocked by GMail’l outgoing mail server, because it has a zip attachment containing an executable file. GMail does not allow this. For more info, see http://…..
Not as succinct as u14sm9443132gvf.20, but rather more useful, don’t you think?
I had the exact same problem. I wish they could say it like that, it would have saved me a half hour of confusion and it would have reached my recipient a few hours ago!
happened to me too but with some php files inside the zipped archive. so we now know it’s not limited to *.exe
I had the same problem. My zip archive contain sources of asp.net web-site – some .js, .vb, .dll
I get around this by just renaming files to exclude the extension, and tell the recipient to re-add the extension after saving the file. Good enough for occasional use.