4 ms·
My favorite LinkedIn feature is how invitations are not sent by linkedin.com, but your friend/colleague/etc. This way, marking it as spam doesn't hurt them. I
by prezjordan 12y ago
My favorite LinkedIn feature is how invitations are not sent by linkedin.com, but your friend/colleague/etc. This way, marking it as spam doesn't hurt them.
I had to go through several rounds of customer support to get my information off of their site. "You don't have an account" they would repeat - of course I don't, which is why it bothers me that I still get invitations and show up in your "recommended" lists.
Not to mention the fake endorsements.
- sbov 12y agoThere's protections against this sort of thing that major isps implement. You can't just set your from address to whatever you want. Well you can, but it would be likely be rejected, or at least wouldn't reach your target's inbox.
- MichaelGG 12y agoSPF allows you to fake the From header, so long your Return-Path is your own domain and passes checks. DMARC can pass if SPF passes. To end users, there's no discernible difference when there's another Return-Path domain. DKIM does allow you to force the From header to be signed, so hopefully that'll continue to pick up steam. It does break some things, like some mailing lists, and that probably contributes to why it's taken so long to get such things going. There's also a lot of "business critical" software out there that just assumes it can send as any user.
- _delirium 12y agoIt depends on how the spam-filtering is implemented, but mark-as-spam should still hurt them in a well-designed system. The 'From' is set to the person in question, but the envelope sender is correctly identified as LinkedIn (or else the mails would often fail SPF checks), and you can filter based on that.