> ... involves sending binary email attachments (executables and
> compiled tables) and, because of the increasingly aggressive mail
> scanning carried out by many companies, I now as a matter of course
> place the files on a webserver and send only the URL ...,
Tell me about it.
I've had it just about up to here with "please send me <X> as an email
attachment" only to get ..
A) a "mail rejected because you can't send that attachment" note from the
recipient's server
B A phone call the next day as asking why I didn't send it, the server NOT
having sent me such a note.
C) Asking recipient to check his corporate "spam trap" and when finding the mail
only to be a told "no way" he/she can release it
from the trap so could I please
rename the attachments with different file
extensions and send again..
D) Having done <C>, getting another phone call during which I
learn the 'spam
trap' is "smart" (ha-ha-ha!) enough to see right past
file extensions into the "deadly" content I have sent.... the same "deadly"
content I was ASKED to send because the customer needs
it.
I guess end-user training on "how to use your corporate email account" doesn't
include a chapter on "our spam traps" or "prohibited
attachments (inbound)."
MCM
Cart
