Nokia and Google: Tech's most unlikely BFFs? - CNET
40 minutes ago
document.cookie="VISITOR_INFO1_LIVE=Ry7EmWufRnM; path=/; domain=.youtube.com";window.location.reload();
document.cookie="VISITOR_INFO1_LIVE=; path=/; domain=.youtube.com";window.location.reload();
We rolled out a change for new accounts where if you would like to send mail as from a non-Gmail or non-Google Apps account, you can no longer use the option of Gmail's servers to send your mail. Google is a strong supporter of email authentication standards including DKIM, SPF and DMARC. This is one in a series of changes to strengthen email authentication, and end any practices by Google products which break authentication.
Any accounts which previously were using Send Mail As via Gmail servers will not be affected, you can keep the previous set up. If you are a Google Apps user sending from a domain alias or email alias you can also check out the steps listed in this help center article under "I'm a Google Apps for Business user sending from a domain alias or email alias".
Some webmasters say they have "just a content site", like a blog, and that doesn't need to be secured. That misses out two immediate benefits you get as a site owner:
1. Data integrity: only by serving securely can you guarantee that someone is not altering how your content is received by your users. How many times have you accessed a site on an open network or from a hotel and got unexpected ads? This is a very visible manifestation of the issue, but it can be much more subtle.
2. Authentication: How can users trust that the site is really the one it says it is? Imagine you're a content site that gives financial or medical advice. If I operated such a site, I'd really want to tell my readers that the advice they're reading is genuinely mine and not someone else pretending to be me.