DoubleSixx

As part of National Cyber Security Awareness Month, we recently posted about how to pick a smart password. Having a strong password goes a long way in helping to protect your data, but there are a number of additional steps you can take to help you keep your Gmail account secure:

1. Remember to sign out. Especially when using a public computer, be careful to sign out of your Google account when you’re finished. Just click the “Sign out” link at the top right corner of your inbox. If you’re using a public or shared computer and want to be extra thorough, you can also clear the browser’s cache, cookies and history. Then, completely close the browser. On your personal computer, you can also lock your computer with a password-protected screensaver if you need to step away momentarily. Learn the best ways to lock your screen in Windows or in Mac OS X. Forgot to sign out? Open up a new Gmail session on another computer and use Gmail’s remote sign out feature to close any sessions that might still be open elsewhere.

2. Be careful about sending certain sensitive information via email. Once you send an email, you’re no longer in control of the information it contains. The recipients, if they so choose, could forward the email or post its contents in a public place. Even if you know and trust the people you’re emailing, that information may become exposed if their accounts become compromised or they get a virus on their machines. As a rule of thumb, should you need to provide a credit card number or financial account number to respond to a message, provide it over the phone or in person — not over email. And never share your password with anyone. Google does not email you to ask you for your password, your social security number, or other personal information — so don’t send it!

3. Enable “Always use HTTPS.” Any time you visit a webpage, your computer needs to send and receive information across the Internet. HTTPS is used to encrypt data as it is transmitted between computers on the Internet, so look for the “https” in the URL bar of your browser to indicate that the connection between your computer and Gmail’s servers is encrypted. We use HTTPS on the Gmail login page, and you can choose to protect your entire Gmail session with HTTPS as well. HTTPS can make your mail slower, so we let you make the choice for yourself. Open Settings and choose “Always use HTTPS” on the General tab if you want to turn it on.

4. Be wary of unexpected attachments.To help protect you from viruses and malware, Gmail automatically scans every attachment when it’s delivered to you, and again each time you open a message. Attachments you send are also scanned. That said, no system is foolproof, so if you happen to get an email from a friend with an attachment you didn’t expect, don’t be afraid to ask the sender what it is before you decide whether to open it.

5. Make sure your account recovery information is up-to-date. Your account recovery information helps you regain access to your account if you ever forget your password, or if someone gains access to your account without your permission. We currently offer several paths to account recovery. Every Gmail user must select a security question and answer — be sure to choose a combination that is easy for you to remember, but hard for others to guess or come across by investigating. Don’t choose a question like “What is my favorite color?” as others may easily guess the answer. We also encourage you to provide a secondary email address and/or a mobile phone number, so we can send you a link to reset your password if you lose access to your account. You can find additional security tips for Gmail in our Help Center. Learn more about protecting your computer, website, and personal information by checking out our security series on the Google blog or visiting http://www.staysafeonline.org.

Source :
http://gmailblog.blogspot.com/2009/10/gmail-account-security-tips.html

When’s the last time you got an email from a stranger asking, “Are you sure you meant to send this to me?” and promptly realized that you didn’t? Sometimes these little mistakes are actually quite painful. Hate mail about your boss to your boss? Personal info to some random guy named Bob instead of Bob the HR rep? Doh!

“Got the wrong Bob?” is a new Labs feature aimed at sparing you this kind of embarrassment. Turn it on from the Labs tab under Gmail Settings, and based on the groups of people you email most often, Gmail will try to identify when you’ve accidentally included the wrong person — before it’s too late.

If you normally email Bob Smith together with Tim and Angela, but this time you added Bob Jones instead, we’ll warn you that it might be a mistake. Note that this only works if you’re emailing more than two people at once.

While we were at it, we also changed the name of “Suggest more recipients” to “Don’t forget Bob” — the two related Labs features just kind of went together better this way.

If you want to test “Got the wrong Bob?” out, try faking a mistake like this:
1) Think of three people you often email together.
2) Compose a message to two of them.
3) Start typing the third member of the group (for help you can use one of the people we suggest in “Don’t forget Bob”), but then auto-complete on the wrong name.

If you have suggestions please let us know. And if “Got the wrong Bob?” happens to save you from making a really bad mistake, we want to hear about that too.

Source :

http://gmailblog.blogspot.com/2009/10/new-in-labs-got-wrong-bob.html

CNET News reporter Tom Krazit joins today’s podcast to talk about what caused Tuesday’s Gmail outage and what it means as we move more of our businesses and personal lives into the cloud. Also in today’s podcast: Oracle’s acquisition of Sun could be delayed by an antitrust inquiry by the European Commission, Sony unveils a new smartphone and Netbook in Berlin, and more.

Listen now: Download today’s podcast



Source : http://news.cnet.com/8301-11424_3-10336483-90.html?part=rss&subj=news&tag=2547-1_3-0-20

Gmail’s web interface had a widespread outage earlier today, lasting about 100 minutes. We know how many people rely on Gmail for personal and professional communications, and we take it very seriously when there’s a problem with the service. Thus, right up front, I’d like to apologize to all of you — today’s outage was a Big Deal, and we’re treating it as such. We’ve already thoroughly investigated what happened, and we’re currently compiling a list of things we intend to fix or improve as a result of the investigation.

Here’s what happened: This morning (Pacific Time) we took a small fraction of Gmail’s servers offline to perform routine upgrades. This isn’t in itself a problem — we do this all the time, and Gmail’s web interface runs in many locations and just sends traffic to other locations when one is offline.

However, as we now know, we had slightly underestimated the load which some recent changes (ironically, some designed to improve service availability) placed on the request routers — servers which direct web queries to the appropriate Gmail server for response. At about 12:30 pm Pacific a few of the request routers became overloaded and in effect told the rest of the system “stop sending us traffic, we’re too slow!”. This transferred the load onto the remaining request routers, causing a few more of them to also become overloaded, and within minutes nearly all of the request routers were overloaded. As a result, people couldn’t access Gmail via the web interface because their requests couldn’t be routed to a Gmail server. IMAP/POP access and mail processing continued to work normally because these requests don’t use the same routers.

The Gmail engineering team was alerted to the failures within seconds (we take monitoring very seriously). After establishing that the core problem was insufficient available capacity, the team brought a LOT of additional request routers online (flexible capacity is one of the advantages of Google’s architecture), distributed the traffic across the request routers, and the Gmail web interface came back online.

What’s next: We’ve turned our full attention to helping ensure this kind of event doesn’t happen again. Some of the actions are straightforward and are already done — for example, increasing request router capacity well beyond peak demand to provide headroom. Some of the actions are more subtle — for example, we have concluded that request routers don’t have sufficient failure isolation (i.e. if there’s a problem in one datacenter, it shouldn’t affect servers in another datacenter) and do not degrade gracefully (e.g. if many request routers are overloaded simultaneously, they all should just get slower instead of refusing to accept traffic and shifting their load). We’ll be hard at work over the next few weeks implementing these and other Gmail reliability improvements — Gmail remains more than 99.9% available to all users, and we’re committed to keeping events like today’s notable for their rarity.

Source :

http://gmailblog.blogspot.com/2009/09/more-on-todays-gmail-issue.html