Важни съобщения, публикации, новини и друга полезна информация.

hitsol.net получи официален статут на директен оторизиран търговски представител на Google Apps.

As the dramatic growth of the mobile web changes the way people consume content, it’s becoming increasingly important for publishers to provide a good mobile experience. With this in mind, we just added automatic mobile rendering in Google Sites for iOS 3.0+ and Android 2.2+ devices, and a mobile version of the Google Sites lists.

By going to General settings under More actions > Manage site and clicking on Automatically adjust site for mobile phones, your Google site will be automatically adjusted whenever it’s viewed from an iOS or Android 2.2+ device:

Before	After

The most noticeable automatic adjustments include:

• Aligning the header layout and top bar
  
• Fitting the width of the site to match the device’s width
  
• Smart handling of sidebars, horizontal navigation, and dropdown links

After you’ve enabled this feature, you can preview the page from your computer as a mobile viewer using More actions > Preview as viewer then select Mobile from the yellow Preview page as viewer (Mobile | Desktop) box at the top of the page.

You can also choose to hide some of the links in your site’s footer to save vertical space.


It’s also important for you to be able to access and search your own sites on the go, which is why Google also added mobile versions of the site list, sites search, and browse sites categories.


Just navigate to http://sites.google.com from any iOS 3.0+ or Android 2.2+ device for quick access to your sites.

As more people unplug from their desks and interact with content on the go, new doors are opening for everyone. Google hope these tools will empower you to meet the challenges of publishing in a mobile world using Google Sites.

От 10 Май 2011 година Google Apps става платен за нови организации с над 10 потребителя.
Съществуващите организации с над 50 потребителя също ще преминат на платена версия.
Вече е възможно да се избере и месечен план за плащане, който е $5 на потрбител.

2-step verification adds an extra layer of security to your users' Google Apps accounts by requiring them to enter a verification code in addition to their username and password, when signing in to their account.

The Google Apps Service Level Agreement does not apply to any services used in connection with 2-step verification if the verification process relies on third-party voice or data providers to deliver the verification code.

Why should I enable 2-step verification for my domain?

2-step verification helps protect a user's account from unauthorized access should someone manage to obtain their password. Even if a password is cracked, guessed, or otherwise stolen, an attacker can't sign in without access to the user's verification codes, which only the user can obtain via their own mobile phone.

Requirements

• A mobile phone that can receive the verification code via text message or phone call. See how to view the list of supported countries.
Or
• An Android, BlackBerry, or iPhone. These devices use the Google Authenticator mobile app to generate the verification code.
• Note: 2-step verification can't be used for accounts using a SAML single sign-on service (SSO). See SAML SSO Service for Google Apps.
• 2-step verification is only available in US English in the next-generation version of the Google Apps administrator control panel. See Current vs. Next generation control panel for more information.

How it works

1. You enable 2-step verification for your domain in your Google Apps control panel. See Setup 2-step verification for your domain for how to enable 2-step verification for your account. We recommend that you notify your users of this new security process and include instructions on how to get started.
   
   Note: You can't force your users to use 2-step verification, they must opt-in themselves.
   
   
2. The user enrolls in 2-step verification, and selects the method for receiving their verification code on their mobile phone: the Google Authenticator app, text message, or phone call. How quickly they get their code via text message or phone call depends on their service provider and location. We recommend users with smartphones to use the Google Authenticator app which can generate codes without a network connection.
   
   See Set up 2-step verification for your Google Account.
   
   
   • If this link doesn't take you to the 2-step verification page, you need to follow these steps:
     
     
     1. Sign in to your Google Apps Gmail Account and click Settings (in the top right corner).
     2. Under the Accounts tab, click Google Account settings.
     3. Under Personal Settings, click Using 2-step verification
     4. Follow the steps in the 2-step verification guide to set up 2-step verification.
   
   Administrators can point users to Getting started with 2-step verification for step-by-step instructions.
   
   
3. The next time the user signs in to their Google Apps account on a new browser or device, they enter their username and password as usual. They're then prompted with a second page to enter a verification code. When your user checks Remember verification for this computer, they're only prompted to enter a verification code once every 30 days per browser or after deleting their browser's cookies. Your users should not check this if they're at a public or shared computer.
   
   
   
   
4. Depending on how they opted to receive their code, the user gets their time-based, one-time code from the Google Authenticator app on their smartphone or via text message or phone call. They then enter the code to successfully sign in.
   
   
   • If a user loses their phone, they can use backup codes to sign in. See Frequently Asked Questions - Backup codes.

Signing in to mobile devices with application-specific passwords

Once your users enroll in 2-step verification, they may need to use application-specific passwords in addition to their verification codes. For installed applications that don't have a 2-step verification field, your users will need to enter an application-specific password once per device or application in place of their regular password to access their Google Account.

Common devices and applications that require application-specific passwords are: Gmail and Google Calendar on Android-based phones, ActiveSync for Windows Mobile and iPhone, and IMAP clients such as Thunderbird. See Sign in to mobile or desktop apps for more details.

Remember that good security practices are critical to the integrity of your user's Google Account. Learn more at Keeping your account secure.

Desktop notifications for email and chat are now available for all Google Apps domains. These are HTML5 desktop notifications which display pop-ups whenever a chat message or new email arrives.

Editions included:
Google Apps, Google Apps for Business, Government and Education

Languages included:
All languages supported by Gmail

How to access what's new:
In your Gmail “Settings”, go to the ‘General’ tab and scroll down to the new ‘Desktop Notifications’ section. Click on the link to opt-in to this feature. Once enabled, choose if you want notifications just for chat, email or both. You can also choose just to be notified for email in Priority Inbox if you have that enabled.

Note: This functionality is currently only available for people using Google Chrome, but Google is working to make notifications part of the standard Web platform.

For more information:
http://gmailblog.blogspot.com/2011/01/desktop-notifications-for-emails-and.html
http://mail.google.com/support/bin/answer.py?hl=en&ctx=appsfeed&answer=1075549

Google has been an early and consistent supporter of email authentication technologies, which help ensure senders are who they say they are, and in turn help to curb spam. Since we launched Gmail in 2004, Google have supported email-signing standards such as DomainKeys and DomainKeys Identified Mail (DKIM) to help validate outbound mail with digital signatures. On the inbound side, to help Google users identify email from verified senders, in 2008 Google worked with eBay and PayPal to authenticate their mail with DKIM and block all unsigned messages purportedly from those companies destined for Gmail users.

But the spam and phishing epidemics aren’t letting up – every day Gmail filters out billions of unwanted messages from our users’ inboxes – so Google’ve been focused on creating helpful tools and working with the email industry to bring solutions that will help Google customers. Email authentication is an important mechanism to verify senders’ identities, giving users a tool to recognize potential spam messages. In addition, many mail systems can display whether a received message is DKIM-verified, which helps spam filters verify and assess the overall reputation of the sender’s domain: messages from untrusted senders are treated more skeptically than those from good senders.

Today, Google mark another notch in the spam-fighting belt: Google’re making it possible for all Google Apps customers to sign their outgoing messages with DKIM, so their sent mail is less likely to get caught up in recipients’ spam filters. Google Apps is the first major email platform – including on-premises providers – to offer simple DKIM signing at no extra cost. Once again, the power of the cloud has made it possible for Google to bring this feature to millions of customers quickly and affordably.


“We help the most-phished brands on the Internet manage their mail authentication programs, and the Google Apps solution is the simplest that we've encountered. Configuring DKIM for in-house systems requires plug-ins or additional gateway servers, making a company's mail environment more complex and difficult to manage. As a Google Apps customer, this feature took us only a few clicks in the control panel and an update of our DNS," said Kelly Wanser, CEO of eCert, an industry leader in providing critical protection against email fraud.

Starting today, all Google Apps administrators can enable DKIM signing in the “Advanced Tools” tab of the control panel. As more email providers around the world support DKIM signing, spam fighters will have an even more reliable signal to separate unwanted mail from good mail. We’re pleased to let millions more organizations use DKIM with this improvement.

Google Apps administrators can now create policies specifying who their users can communicate with over email, and administrators can tailor these policies for different groups of users.

For example, school faculty and staff can have unrestricted email access while students have the freedom to send and receive emails within the school community but are protected from unwanted email interactions with outsiders.

Editions included:
Google Apps for Business, Government and Education

Languages included:
US English Only (Next Generation Control Panel)

How to access what's new:
In the administrator control panel, select ‘Advanced tools’ and scroll down to the bottom of the page to see the new option ‘Restrict email delivery’. To restrict email to just within the domain, administrators will still need to add the domain name here.

For more information:
http://googleenterprise.blogspot.com/2011/01/set-limits-on-email-use-within-your.html
Help Center: http://www.google.com/support/a/bin/answer.py?hl=en&answer=177482

The following new feature is now available in Google Calendar for all Google Apps domains:

Event timezones - You can now specify the time zone for a given event. You can even set up events which start in one time zone and end in another.

Previously this feature was only available to domains with ‘pre-release features’ enabled in the Administrator Control Panel.

Editions included:
Google Apps, Google Apps for Business, Government and Education

Languages included:
All languages supported by Google Calendar

How to access what's new:
Event timezones: Click the “Time zone” link to the right of the date and time fields on the event page. Events will appear on your calendar according to the current time zone you’re in, and when you change to your destination time zone they’ll be in the right place.

For more information:
http://gmailblog.blogspot.com/2010/12/event-time-zones-in-google-calendar.html

Chrome delivers the fastest Google Apps experience and protects users against phishing and malware on the web. This browser is now available for download with support for the following administrator functionality:

MSI Installer: A standalone installer that allows admins to install the Chrome browser at a system-level across the organization.

Group Policies: These allow admins to configure common behaviours across the organization such as default search provider, default homepage and many more.

Policy Templates: ADM and ADMX templates are included in order to help admins easily configure these policies that manage security and privacy including the ability to disable auto-updates.

Editions included:
Google Apps, Google Apps for Business, Government and Education*

How to access what's new:
Download Google Chrome for Business

For more information:
http://googleenterprise.blogspot.com/2010/12/chrome-is-ready-for-business.html

*Support is available to Google Apps for Business, Government and Education customers for Chrome browser administrator issues only.

Email delegation is now available to all Google Apps customers. This Gmail feature was previously only available to Google Apps for Business.

Editions included:
Google Apps and Google Apps for Education

Languages included:
All languages supported by Gmail

How to access what's new:
Administrators must first enable mail delegation by checking the 'Mail Delegation' checkbox under 'Email Settings' in the administrator control panel.

To enter a delegate, users can select the 'Accounts' tab under 'Settings' in Gmail and click 'Add another account' to enter their delegate's email address.

Once the delegate is signed into their own own Gmail account, they can then access the other person's account from the account selection menu at the top of Gmail.

For more information:
http://googleenterprise.blogspot.com/2010/12/email-delegation-now-for-all-customers.html
http://mail.google.com/support/bin/answer.py?hl=en&ctx=mail&answer=138350