Another less known fact is that gmail blocks zip files/archives that contain executable extensions, scrips, or encrypted filenames. I few months ago I tried sending a document that contained my PII and I was unable to send it because gmail couldn't determine the content inside the archive. This feature that should have a on/off option IMO.
Never Send Your CV via Gmail
31–40 of 47 posts
Re: Never Send Your CV via Gmail
#32I do not understand, why we put emails in spam folders instead of rejecting them (as some providers do, e.g. mailbox.org, posteo.de). It may seem weird at first, but at least if something important would end up in Spam, the sender is going to get a notice.
The same reason we shadowban people or give vague responses to incorrect passwords guesses. You don't want to give bad faith users information that makes their job easier. Telling spammers whether their emails were received or not would be incredibly valuable in interrating ways around the filters.
Does that really help, when the spammer can make their own email account on the target's email service (eg. Gmail), send the spam email to this email account and see if it gets through the filter?
Re: Never Send Your CV via Gmail
#33I am wondering what happened to paragraphs?
This one line one sentence style seems to be popular on Medium.
But there is no rhythm. There is no flow.
Each sentence must have started on separate index cards.
Why wouldn't you weave them together?
So much white space, so many long pauses.
Do people enjoy reading this kind of writing?
Re: Never Send Your CV via Gmail
#34I do not understand, why we put emails in spam folders instead of rejecting them (as some providers do, e.g. mailbox.org, posteo.de). It may seem weird at first, but at least if something important would end up in Spam, the sender is going to get a notice.
Then your mailserver (if you aren't Google) will be blacklisted for spewing out hundreds of thousands of "rejection messages" an hour.
Re: Never Send Your CV via Gmail
#35Perhaps there should be an interstitial when loading Gmail if there are items in your spam that you haven't seen 1-2 days after receiving them.
Re: Never Send Your CV via Gmail
#36Earlier quoted context omitted.
The same reason we shadowban people or give vague responses to incorrect passwords guesses. You don't want to give bad faith users information that makes their job easier. Telling spammers whether their emails were received or not would be incredibly valuable in interrating ways around the filters.
Does that really help, when the spammer can make their own email account on the target's email service (eg. Gmail), send the spam email to this email account and see if it gets through the filter?
I don't know. Although I would be mildly surprised if there was a single universal spam filter applied to all Gmail accounts. I would also think there are more inputs to the system than just the sender and the body of the email. Gmail being so big allows other variables like the rate that address is sending to all of Gmail as well as how users engage with those emails. Therefore getting a single test email through the filter probably isn't proof that you have defeated the overall filter.
Re: Never Send Your CV via Gmail
#37I have sent my CV containing both my phone number and email address to various companies and have never encountered this problem. I don't think the PDF containing your personal information was the problem, but potentially the individual dealing with your information.
Re: Never Send Your CV via Gmail
#38I am wondering what happened to paragraphs? This one line one sentence style seems to be popular on Medium. But there is no rhythm. There is no flow. Each sentence must have started on separate index cards. Why wouldn't you weave them together? So much white space, so many long pauses. Do people enjoy reading this kind of writing?
I would much rather a paragraph. But these days, I see spelling errors on some of the most popular news publication websites and have just come to accept that the quality of writing online is diminishing.
Re: Never Send Your CV via Gmail
#39The fact that this so called developer doesn't understand the difference between a sender and a receiver of email makes me think there are other things in the CV that caused them to not be hired.
Understanding Gmail's spam/quarantine policies (which was both the sender/receiver here) is not really relevant to engineering roles, unless maybe you're on the marketing team.
Seeing a system and getting somewhat of an accurate understanding of how the parts work is, though.
And it's not like "email" is some esoteric thing he's only now come into contact with.
For example, don't say "GMail". This is about email. To misquote Babbage: "I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a conclusion".
This conclusion screams of not being able to understand the logical effect of a known fact. I wouldn't want this person troubleshooting anything, for example.
And I didn't see many comments about the rest of his statements. It's a mess. He seems somewhat angry at GMail's suggestions (this would be on the sender side) because sometimes he doesn't want to say what GMail suggests. Again… confusion of ideas.
Actually, now that I think about it I'm seriously suspecting this was written by a bot. More articles than you'd expect are written by bots, and this is close enough to making sense (on multiple points), but without an actual logical point, that it's a possibility.
Re: Never Send Your CV via Gmail
#40Earlier quoted context omitted.
Understanding Gmail's spam/quarantine policies (which was both the sender/receiver here) is not really relevant to engineering roles, unless maybe you're on the marketing team.
Seeing a system and getting somewhat of an accurate understanding of how the parts work is, though. And it's not like "email" is some esoteric thing he's only now come into contact with. For example, don't say "GMail". This is about email. To misquote Babbage: "I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a conclusion". This conclusion screams of not being able to understa…
Gmail is decreasingly an email client an increasingly a protocol. Gmail-to-gmail messages get treated quite differently, and ultimately OPs conclusion that gmail intercepted their email because it determined that CVs are suspicious is correct.
I would add that I think it's a bit fickle and unkind for internet strangers to pass judgement on a person's ability to do their job based on a post like this. This individual did not ask for our opinion on their ability to do a job, but instead gave (a useful) warning about how the gmail client handles CVs.