SMTP and ESMTP error code list

/in

It is important to figure out why your email bounces. If you receive an email bounce, you can look in the bounce message to find the proper error code that will give you the reason for the bounce. Below is a list of the Standard SMTP error codes and the Extended SMTP (ESMTP) error codes.

SMTP and ESMTP error codes

SMTP Error Codes

This list of codes is the standard SMTP error codes you will find in most email bounces.

Specific Explanation of the 400 Error Codes occurring on our servers:

450 4.1.8 : Sender address rejected: Domain not found

Our inbound servers require that the hostname for the sender server should have valid MX or A records in order to accept emails from it. You need to contact the sending server’s email admin to add valid DNS records for his server.

450 4.7.1 Client host rejected: cannot find your reverse hostname

Our inbound servers require reverse hostname for sender server IP to be present in order to accept the email. Please ensure that the valid PTR records are added for all outbound server IP’s. Post adding the required rDNS records our inbound servers will accept mails from the remote mail hosting server.

450 4.7.1 : Recipient address rejected: Policy Rejection- Quota Exceeded

This error comes from our incoming mail server if user is receiving excessive amounts of mails.

450 4.7.1 Recipient address rejected: Access denied.

This occurs when the recipient address is invalid. i.e., not in form of user@domainname OR if the Recipient address is blocked on server.

451 4.3.5 Server configuration problem – try again later;

451 4.7.1 Service unavailable – try again later;

This error most likely occurs if there is a configuration error with our servers. If you encounter any of the above messages, please contact our support helpdesk with the details.

452 4.5.3 Error: too many recipients

The error message is encountered when the user is exceeding the limit of more than 50 recipients in an email. The list of recipients is inclusive of To, Cc, and Bcc. If you encounter the above error, reduce the number of recipients in the email and try again.

Specific Explanation of the 500 Error Codes occurring on our servers:

522 5.7.1 :  Recipient address rejected: Requested mail action aborted: exceeded storage allocation

This error comes if the user is overquota.

530 5.7.0 Recipient address rejected: Authentication Required.

This error comes when your sending mails to remote domain without using SMTP authentication.

550 5.1.1 Recipient address rejected: User unknown in virtual alias table;

This is the bounce back message that is received by the sender from our server if the destination email address does not exist.
The same error message is received if the recipient has a mail loop. That is, if the recipient has set a forward to another email address and that email address is forwarded back to the original one. In this case, you need to remove the loop in order to receive the emails.
If there is a forward set for an account, and an email is sent to that account, if for some reason the forwarded email is not sent, the original sender may get the above error.
For example, abc@domain.com if forwarded to abc@dom.com, if a third user xyz@dom2.com emails to abc@domain.com, he may get the above error if the forwarded email is bounced.

550 5.1.1 Protocol error

This error code ideally suggests that the sender has used SMTP protocol instead of ESMTP, thus the outbound mail of the sender was rejected. In short, the sending client doesn’t properly communicate and makes errors in the SMTP protocol.

550 5.3.2 Service currently unavailable

The error code 5.3.2 usually means that the system is not accepting network messages. We would thus need to look outside Exchange for a connectivity problem.
The error code ideally occurs ideally for two reasons which are listed below:
1). The sending IP is blacklisted at an RBL or blacklist monitoring site. (You may verify the same by inputting the IP via this link: http://mxtoolbox.com/blacklists.aspx )
2). There is a temporary block on the IP on our Inbound server due to multiple mails from this IP. Feel free to contact our support desk for more information and regarding de-listing the same.
3). If sending IP does not have a reverse PTR record configured. Reference URL: http://mxtoolbox.com/NetworkTools.aspx

550 5.4.5 Recipient address rejected: Hourly domain sending quota exceeded

This is the error message that you get if your domain name exceeds the hourly quota set for the domain name. Here, the term ‘hour’ refers to the last 60 minutes.

550 5.4.6 Recipient address rejected: Hourly sending quota exceeded

This is the error message that you get if the user (that particular email address) exceeds the hourly quota set. Here, the term ‘hour’ refers to the last 60 minutes.

550 5.7.1: Helo command rejected: You aren’t localhost.
550 5.7.1: Helo command rejected: You aren’t localhost.localdomain.
550 5.7.1: Helo command rejected: You are not me

Our servers do not accept SMTP HELO command as HELO localhost or HELO localhost.localdomain or HELO . We accept HELO from a valid Domain Name or your computer name which is other than your domain name. Please check with your ISP or Mail administrator for this issue.

551 5.7.1 The message was rejected due to classification as Virus, Spam or high bulk ratio.

This is a bounce-back message that you receive when an email is classified as spam while sending out. If you feel that a genuine email is rejected as spam, you need to send the same email with the full headers and the content to our support team. That email in question will be reviewed manually.

552 5.3.4 Message size exceeds fixed limit

A 552 email error is typically encountered when there is a problem related to an attachment in your email. Either it has exceeded the size limits of the remote server, or the file-type isn’t allowed by the remote server.
1. For file extensions not allowed on our servers, please do refer to the following link: http://support.mailhostbox.com/file-extensions-that-are-not-allowed-as-attachments/
2. For mail (including attachment) sent across from our servers, we allow clients to send up to 30 MB of data.

Solution: Examine the size of the message including attachments. Try zipping the file content.

553 5.7.1 Sender address rejected: not owned by user user@domain.com

This is the error message that is received when you are trying to send an email as a different user. This error message is seen by the users who are using Exchange servers with our system.

You need to add an identity for the same in the webmail. For example,

Log into the webmail of user1@domain.com
Add the identity from the settings tab for user@domain.com (If the from address is user@domain.com). For more information, please refer: http://support.mailhostbox.com/email-users-guide/sender-identities
Once the identity is added and confirmed, you should be able to send the emails.

554 5.7.1 Service unavailable; Client host X.X.X.X blocked using zen.spamhaus.org;

This is the error message that is received of the IP address of the sender is listed at zen.spamhaus.org
For further details, please check http://www.spamhaus.org/zen
OR check http://www.spamhaus.org/query/bl?ip=<your_ipaddress> and contact zen.spamhaus.org to get the IP De-listed.

554 5.7.1: Relay access denied;

There are couple of reasons for this error while sending an email

If the domain is in the status “Pending Verification” in the control panel.
If the user has not checked the option “Our server requires authentication” option while setting up the account. For more information on setting up the email account, please refer: http://support.mailhostbox.com/email-users-guide/configure-your-desktop-…

554 5.7.1: Recipient address rejected: USER IS SUSPENDED

This error comes if a user is suspended in Control Panel.

554 5.7.1: Sender address rejected: Access denied.

This error comes when the sender address is blocked on our server. Generally, this is done if spam has originated from this user.

554-mx1.mailhostbox.com ESMTP not accepting connections OR 554-us2.mx1.mailhostbox.com ESMTP not accepting connections OR 554-in.mx1.mailhostbox.com ESMTP not accepting connections

When sending an email to a recipient within our mail hosting servers, sender may receive a bounce back stating ESMTP not accepting connections. The error indicates senders IP address is suspected of sending spam and is blacklisted.
Example Error:
Delivery has failed to these recipients or groups:
xyz@xyz.com
A problem has occurred during the delivery of this message to this e-mail address.Try sending this message again. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: mx1.mailhostbox.com
xyz@xyz.com
554-mx1.mailhostbox.com ESMTP not accepting connections

To resolve this issue, please perform the steps below:
1. Check sender’s IP address, if it is blacklisted in any RBL (Realtime Black List): http://mxtoolbox.com/blacklists.aspx. Ask sender to submit an IP removal request to RBLs.
2. Check IP reputation on mail filters by contacting CSI and get the IP delisted by visiting the following URL: https://csi.cloudmark.com/en/reset/ by providing the sender’s IP address.

200 Codes

  • 211 – System status/system help reply
  • 214 – Help message
  • 220 – Domain service ready
  • 221 – Domain service closing transmission channel
  • 250 – Requested mail action completed and OK
  • 251 – Not Local User, forward email to forward path
  • 252 – Cannot Verify user, will attempt delivery later
  • 253 – Pending messages for node started

300 Codes

  • 354 – Start mail input; end with.
  • 355 – Octet-offset is the transaction offset

400 Codes

  • 421 – Domain service not available, closing transmission channel
  • 432 – Domain service not available, closing transmission channel
  • 450 – Requested mail action not taken: mailbox unavailable. request refused
  • 451 – Requested action aborted: local error in processing Request is unable to be processed, try again
  • 452 – Requested action not taken: insufficient system storage
  • 453 – No mail
  • 454 – TLS not available due to temporary reason. Encryption required for requested authentication mechanism
  • 458 – Unable to queue messages for node
  • 459 – Node not allowed: reason

500 Codes

  • 500 – Syntax error, command unrecognized
  • 501 – Syntax error in parameters or arguments
  • 502 – Command not implemented
  • 503 – Bad sequence of commands
  • 504 – Command parameter not implemented
  • 510 – Check the recipient address
  • 512 – Domain can not be found. Unknown host.
  • 515 – Destination mailbox address invalid
  • 517 – Problem with senders mail attribute, check properties
  • 521 – Domain does not accept mail
  • 522 – Recipient has exceeded mailbox limit
  • 523 – Server limit exceeded. Message too large
  • 530 – Access Denied. Authentication required
  • 531 – Mail system Full
  • 533 – Remote server has insufficient disk space to hold email
  • 534 – Authentication mechanism is too weak. Message too big
  • 535 – Multiple servers using same IP. Required Authentication
  • 538 – Encryption required for requested authentication mechanism
  • 540 – Email address has no DNS Server
  • 541 – No response from host
  • 542 – Bad Connection
  • 543 – Routing server failure. No available route
  • 546 – Email looping
  • 547 – Delivery time-out
  • 550 – Requested action not taken: mailbox unavailable
  • 551 – User not local; please try forward path
  • 552 – Requested mail action aborted: exceeded storage allocation
  • 553 – Requested action not taken: mailbox name not allowed
  • 554 – Transaction failed

Extended SMTP (ESMTP) standards

The Extended SMTP error codes work in 3 digit combinations. For example, 5.2.1 is a Permanent Error where the receiving email is not accepting messages. The first number is the email message status. The second 2 numbers pinpoint the exact information about the error.

  • 2 Successfully sent the email;
  • 4 Temporary problem when sending the email. The email server typically will try to send it again till it reaches retry timeout.
  • 5 Permanent or Fatal error. This can be caused by a nonexistent email address, DNS problem, or your email was blocked by the receiving server.

Below is a list of the Extended SMTP error codes.

Reference by mailboxhostbox

Tips to Keep Kids Safe Online

/in

Tips to Keep Kids Safe Online

The task of protecting our children online is a challenge that grows in complexity every day. Just a few years ago, parents mostly worried about the risks of “stranger danger” and online predators. Recently, research from the Harvard University-based Berkman Center downgraded online predators to a much lower risk category, but we still have many online risks to educate our children about. These risks can be categorized into three groups.

Cybercrime

The first category is cybercrime–or the threats caused by financially motivated strangers. Whether in the form of computer viruses, Trojan horses,phishing attacks, or spam emails, cybercrime keeps growing and changing each year. It’s so important for parents to stay on top of the varied threats. This can be daunting, especially if you feel you aren’t tech savvy or don’t know where to look for help. Fortunately there are several steps you can take to keep cybercrime in all its forms away from your computer, your home network, and your family’s information. Follow these tips yourself, and pass them along to your kids.
1. Use an Internet security suite, like Norton 360 or Norton Internet Security, on all computers you own. Using plain antivirus is just not enough protection. You need a full firewall, antispyware, and other protection a suite can provide.
2. Keep your home network secured with a good password and security settings.
3. Learn to avoid clicking links, responding to ads, and opening emails when they come from someone you don’t know or appear suspicious. Just take that extra moment to call your friend (“Did you post that link?”), type the URL for your bank, or otherwise display your worldly wisdom by not falling for these social engineering tricks.
4. Use a good password (unique and complex) on all accounts and devices. The two most important account passwords are for your social network and your email account. If a hacker gets control of your social network, he can scam your friends. If he has your email, he can reset the password on all your other accounts by using the ubiquitous “forgot my password” link.
5. Talk to your kids about avoiding cybercrime. They need to be just as cautious as you. It’s also important that they know if they can talk to you when they make an online mistake, like falling for a scamware alert and downloading something dangerous to the computer. Many kids are savvy enough to realize when they’ve downloaded a virus, but few are comfortable admitting their mistake to their parents.

Cyberbullying

The second category is the harm that can befall your child from people they know. Typically, this means cyberbullying, the single most common online harm our children will experience. Statistics vary, but at least 20 percent of kids will receive harassing, hateful, or insulting messages via social networks, emails, instant messages, videos, and texts.
Interestingly enough, unlike its non-tech relative, cyberbullying inherently allows roles to be reversed almost instantaneously. The victim can become the bully just by responding to a mean email with another verbal volley.

We have much work to do in our schools and online communities to promote online civility and kindness. We also need to promote appropriate responses when a child is confronted with cyberbullying. A great resource for information about all forms of bullying can be found at http://www.stopbullying.gov/ and specifically about cyberbullying at http://www.cyberbullying.us/ .
6. Advise your kids never to share passwords, not even with a close friend. If they think they did, they should change the password.
7. Teach your children to log out of computers when they finish their work, even at home. This will prevent a friend or sibling from posting or emailing using their account–even as a joke.
If your child is being cyberbullied, teach them to not respond, to keep a copy of all the messages, and to report it to the school or website. If the messages include threats, report this to the police. If you report the cyberbullying to the school, be sure to follow up in person and ask for a written plan on how the school will respond to the problem. Most states have laws against this form of abuse, and schools have an obligation to address the issue when made aware of it.

Online Reputation

The third category of online risk is the harm we cause ourselves. This can take many forms, including sexting (sending sexual content by photo, video, or text message); posting information or images of a private, embarrassing, or controversial nature; and even neglecting to set privacy settings.
Sexting is definitely not something we want our underage kids to engage in. Child pornography and other laws may require teachers, parents, and law enforcement to get involved if they become aware of these messages. Kids may think they are sharing these images within a private relationship, but too often the recipient shares the images, for any number of reasons. Perhaps the relationship has ended, maybe the recipient is bragging to friends, or perhaps a friend saw the images on the phone and forwarded them to others. (That is another reason to put a password on all devices!)

“Online reputation” is a term for all the information available about you on the Internet, whether through conducting a search or by viewing your profile on a social network. That composite portrayal of you can serve as a digital dossier, telling a story that may distort the real facts of who you are. We’ve often heard of young people self-sabotaging their academic, career, and romantic futures with silly posts, photos of underage drinking, or membership in controversial online groups.
The issue of privacy on the Internet is a growing concern for many. We each need to take steps to keep our personal information protected by securing our online accounts, limiting the information we post in public forums, and opting out of unused or unwanted online services. Our lives are being publicly documented to a degree that is increasingly uncomfortable. Just do an online search of yourself and you’ll see your 10K race scores, your home’s mortgage information, and your tagged photos on your social network. Private information can be used in numerous annoying and harmful ways, so it is increasingly worthwhile to pay attention to privacy issues–and to pass along good advice and habits to your kids.

8. Use the security and privacy settings on your social network and all accounts to limit who can access your posts.
9. Learn about parental control settings for your phones, gaming devices, tablets, and all computers. A great tool is the free Norton Family for PCs and Macs.
10. Talk to your kids regularly about how to use technology. Set rules and limits, and keep technology out in the open. Learn about “The Talk,” and make it an annual discussion, or for whenever you introduce new technology into your family life.

 

 

Courtesy :- Symantec

More menu improvements in Google Docs and Slides

/in

Based on usage data and your feedback, we’re making some changes to the menus and toolbars in Google Docs and Slides on the web. These are similar to some previous changes we made and will make it easier to find certain items. Among other things, these changes include:

To add a line or page break in Docs:
Before: Insert > Page break or Column break
After: Insert > Break > Page break or Column break
See Help Center for more details: Add, edit, or remove a link, bookmark, or page break.

To add Alt text to a shape in Docs or Slides:
Before: Select shape > Format > Alt text. This option will be removed from the menu.
After: Right click on shape > Alt text. This is the new way to add alt text to a shape.
See Help Center for more details: Make your document or presentation accessible.

To change a shape in Slides:

Before: Select shape > Format > Change shape. This option will be removed from the menu.
After: Right click on shape > Change shape. This is the new way to change a shape.

The HTML view in Slides is being removed from the menu.
Before: View > HTML
After: Ctrl+Alt+Shift+P
See Help Center for more details: Make your document or presentation accessible.

These changes will only affect the visual menu. All options will still be available via keyboard shortcuts and the search box in the Help menu.

Launch Details
Release track:
Launching to Rapid Release, with Scheduled Release coming in two weeks

Editions:
Available to all G Suite editions

Rollout pace:
Gradual rollout (up to 15 days for feature visibility)

Impact:
All end users

Action:
Change management suggested/FYI

 

Reference by Google.com

How to create own Bundle file from CRT Files

/in

How do I make my own bundle file from CRT files?

Answer: You may do this using your favourite text editor or by using the command line.

Example:

# Root CA Certificate – AddTrustExternalCARoot.crt
# Intermediate CA Certificate 1 – ComodoRSAAddTrustCA.crt OR ComodoECCAddTrustCA.crt
# Intermediate CA Certificate 2 – ComodoRSADomain/Organization/ExtendedvalidationSecureServerCA.crt OR ComodoRSAECCDomain/Organization/ExtendedvalidationSecureServerCA.crt
# Intermediate CA Certificate 3 – ComodoSHA256SecureServerCA.crt
# Your SSL Certificate – yourDomain.crt

Note: You will not need your SSL certificate for this exercise.

 

There are two ways to create ca bundle file.

1.Using GUI Text Editor

1. Open All files in a text editor. (Remember, not your domain certificate.)
2. Create a new blank text file.
3. Copy contents of all files in reverse order and paste them into the new file.
Example: Intermediate 3, Intermediate 2, Intermediate 1, Root Certificate.
4. Save the newly created file as ‘yourDomain.ca-bundle‘ or ‘yourDomain.ca-bundle.crt’.

 

2.Using Command Line

Linux or UNIX-like Operating Systems:
— cat ComodoRSAAddTrustCA.crt ComodoRSADomain/Organization/ExtendedvalidationSecureServerCA.crt AddTrustExternalCARoot.crt > yourDomain.ca-bundle

Or

— cat ComodoSHA256SecureServerCA.crt AddTrustExternalCARoot.crt > yourDomain.ca-bundle

Windows or DOS:
— copy ComodoRSAAddTrustCA.crt + ComodoRSADomain/Organization/ExtendedvalidationSecureServerCA.crt + AddTrustExternalCARoot.crt yourDomain.ca-bundle

Or

— copy ComodoSHA256SecureServerCA.crt + AddTrustExternalCARoot.crt yourDomain.ca-bundle

Note: ‘yourDomain.ca-bundle‘ is only a placeholder file name. You may call it anything you want.

 

 

how to migrate emails from cPanel to Gsuite accounts

/in

The following is the step to do email migration from cPanel to Gsuite

 

  1. In Linux cPanel check for mx entry . There keep email routing setting as Local mail exchange server
  2. Check whether all username and password given to you is correct or not. If not do correction of the password.
  3. Open Customer’s Google Admin console (at admin.google.com) with super admins rights
    Go to Data migration.
    Select the Email option and click Continue.
    On the Email Migration screen:
    From the Migration source list, select I don’t know/Other IMAP server.
    From the Connection protocol list, select IMAP, then choose an option:
    Enter the IMAP server name (for example, imap.yourdomain.com).
    Enter the IMAP server name and port number in this format: Name: Port.
    Enter the email address and password for your role account(use email id from where you want to migrate ).
    Tip: For help with this, see Connection information for common webmail providers.

Click Connect.
(Optional) If the connection fails, verify that the role account and connection protocol information is correct. Then, click Connect again.
In the Migration start date and Migration options sections, accept the default options or choose to exclude data that doesn’t need to be migrated.
Click Select Users.
Next: Go to Migrate email for a single user or Migrate email for multiple users.

All migration will be completed without fail.

 

 

How to install SSL in IIS 7.x

/in

The Following is the step to install SSL certificate in ISS  7.0

 

1. Open Internet Information Services Manager (IISM) to the appropriate Server
Start -> Administrative Tools -> IISM -> Server Name

2. Open the Server Certificates icon.

3. Open ‘Complete Certificate Request’ Wizard

From the ‘Actions’ Menu on the right select ‘Complete Certificate Request’

4. Proceed to Complete Certificate Request’ Wizard

Fill out all appropriate information. You may need to browse to the location of the certificate or you may enter it in the provided box. The friendly name is not part of the certificate itself, but is used by the server administrator to easily distinguish the certificate.

Note: There is a known issue in IIS 7 giving the following error: “Cannot find the certificate request associated with this certificate file. A certificate request must be completed on the computer where it was created.” You may also receive a message stating “ASN1 bad tag value met”. If this is the same server that you generated the CSR on then, in most cases, the certificate is actually installed. Simply cancel the dialog and press “F5” to refresh the list of server certificates. If the new certificate is now in the list, you can continue with the next step. If it is not in the list, you will need to reissue your certificate using a new CSR (see our CSR creation instructions for IIS 7). After creating a new CSR, login to your Comodo account and click the ‘replace’ button for your certificate.

Assign to Website

1. Navigate back to the root of the appropriate website. The center of the window should say “Default Website Home” or whatever the name of the website is.

2. Select ‘Bindings’ from the ‘Edit Site’ sub menu.

3. Add Port 443

In the ‘Site Bindings’ window, click ‘Add’. This will open the ‘Add Site Binding’ window.

Under ‘Type’ choose https. The IP address should be the IP address of the site or All Unassigned, and the port over which traffic will be secured by SSL is usually 443. The ‘SSL Certificate’ field should specify the certificate that was installed using the above steps.

Click ‘OK’ to save changes.

Note: There may already be an ‘https’ entry in this area. If so, click ‘https’ to highlight it. Then click ‘Edit’ and in the ‘SSL certificate’ area select the friendly name that was generated earlier. Click ‘OK’ to save changes.

 

Click ‘OK’ on the ‘Web Site Bindings’ Window to complete the install.

Important: You must now restart IIS / the website to complete the install of the certificate.

Configure Junk E-Mail Filter Settings With Junk E-Mail Options

/in

Set junk e-mail filter level

The junk E-mail Filter in Outlook is turned on by default, and its protection level is set to No Automatic Filtering. If you feel that Outlook moves too many incoming messages, or too few to the Junk E-mail folder, you can take the follow steps to adjust the filter sensitivity of Outlook:

1. In Outlook 2010/2013, click Home > Junk > Junk E-mail Options.

doc-configure-junk-email-1

Note: In Outlook 2007: click Actions > Junk E-mail > Junk E-mail Options.

2. The Junk E-mail Options dialog will then show up. There are four different levels of junk mail filter settings, please choose the level you want and click OK.

doc-configure-junk-email-6

Notes:

  • • No Automatic Filtering: This option can block messages from addresses which have been added to the Blocked Senders list.
  • • Low: This level will only filter the most obvious junk.
  • • High: Filters all messages suspected as junk.
  • • Safe Lists Only: Any message that is sent from someone not on your Safe Senders list or to a mailing list on your Safe Recipients list is automatically considered as junk email.

Create Junk- E-mail filter lists

There are five different junk e-mail filter lists in the Junk E-mail Options that can determine whether the emails will be moved to the junk folder or not.

  • • Safe Senders List: Email addresses and domain names of the senders in this list are never treated as junk.
  • • Safe Recipients List: You can add addresses and domain names from the mailing lists and distribution lists to this list so that they will never be marked as spam.
  • • Blocked Senders List: If you add an email address or domain to this list, messages will automatically sent to the Junk Email folder.
  • • Blocked Top-Level Domains List: You can add country/region codes to this list to block messages from another country or region.
  • • Blocked Encodings List: To block messages that contain special encoding or character set, you can add encodings to this list.

To set these junk e-mail filter lists, you can do as follows:

1. Click Home > Junk > Junk E-mail Options in Outlook 2010/2013, and click Actions > Junk E-mail > Junk E-mail Options in Outlook 2007.

2. In the pop up Junk E-mail Options dialog box, click Safe Senders tab, and click Add button to add the address or domain that you don’t want to treat as spams. See screenshot:

xdoc-configure-junk-email-2

 

 

 

Making Google prompt the primary choice for 2-Step Verification

/in

In July, we began inviting users to try Google prompt as their 2-Step Verification (2SV) method, instead of SMS text messages. Google prompt is an easier and more secure method of authenticating an account, and it respects mobile policies enforced on employee devices.

Sign In- Google Prompt

With that in mind, we’re now making Google prompt the first choice when users turn on 2SV (previously, SMS was the primary choice). Once 2SV is enabled, users will still have the option to set up SMS, the Google Authenticator app, backup codes, or Security Keys as their alternative second step.

My Account

This will only impact users who have not yet set up 2SV. Current 2SV users’ settings will be unaffected. In addition, if a user attempts to set up 2SV but doesn’t have a compatible mobile device, he or she will be prompted to use SMS as their authentication method instead.

Users can set up 2SV from their My Account page.

A few things to note:

  • A data connection is required to use Google prompt.
  • Users with iOS devices will need to install the Google app in order to use Google prompt.
  • G Suite Enterprise domains can choose to enforce Security Keys to meet more advanced security requirements.
Launch Details
Release track:
Launching to both Rapid Release and Scheduled Release

Editions:
Available to all G Suite editions

Rollout pace:
Gradual rollout (up to 15 days for feature visibility)

Impact:
All end users

Action:
Change management suggested/FYI

Time for a refresh: meet the new Google Calendar for web

/in

Check your schedule. Starting today, a fresh look and new features are coming to Google Calendar on the web to help you manage your time more efficiently and get more done.

We’re taking a lot of what you know and love from Calendar’s mobile application, like the modern color palette and sleek design, and bringing it to the web with a responsive layout that auto-adjusts to your screen size. We’ve also added more features for enterprises to help teams schedule and prepare for meetings.

EventDetails-05 (1)

Over the years, you’ve shared valuable feedback on how we can enhance Calendar to better fit your needs and we’re excited to bring new improvements. Now, it’s even easier to manage your schedule at your desk. In the new Calendar for web, you can:

  • See conference room details when booking a room. G Suite admins can now enter detailed information about their organization’s meeting rooms—so employees know where a conference room is located, how large it is, and whether it has audio/video equipment or is wheelchair accessible. Employees can simply hover over the room name in Calendar when they want to book a space, and a hovercard will pop up with details about the conference location and resources.
    CalendarSRI-blog (2)
  • Add rich formatting and hyperlinks to your Calendar invites. Link to relevant spreadsheets, documents or presentations in your Calendar invite and open them directly from the new “Event Detail” view. This can help you create more detailed agendas and ensure all materials are in one place before your meeting starts.
    MeetingDetails
  • Manage multiple calendars side by side in “Day” view. Now you can view and manage calendars in separate columns. This makes it easier for employees who manage multiple calendars, like administrative assistants, to schedule meetings on behalf of their teams. Click “Day” view and select the calendars you want to compare.
    DayView
  • There are a number of other changes in Calendar, too. Now you can see contact information of meeting participants when you hover over their names in a Calendar invite. There’s also a new way to view and restore deleted items in one place in case you accidentally delete a meeting invite. Additionally, “Day,” “Week,” and “Month” views are now more accessible, featuring better compatibility with screen readers. For more detail on changes, check out this post.Additional information for G Suite admins

    To help you and your users transition to the new Calendar web UI, we’re offering two rollout options to choose from (see the Help Centerfor more information):

    • Automatic—Automatic is the default option. Starting Nov. 14, 2017, for Rapid Release domains and Nov. 28, 2017, for Scheduled Release domains, we will gradually transition your users to the new UI. The transition will take about 8 weeks (including opt-in and opt-out stages). No action is required on your part for the Automatic option.
    • Manual—Alternatively, you can choose to manually control when to move your users to the new UI in the Google Admin console. For example, though we’ve worked with the developers of the most popular Calendar Chrome extensions to prepare for the new UI, you might have users who depend on an extension that hasn’t been updated yet. Or you might like to check out the new UI in your test domain or organizational unit (OU).

    To choose the Manual option, go to Apps > G Suite > Calendar > New Calendar. Here, you can set by organizational unit when you’d like your users to access the new version of the Calendar UI. If you choose the Manual rollout option, please plan to transition all your users to the new UI before Feb. 28, 2018. Any users who are still accessing the old Calendar UI on Feb. 28, 2018, will be transitioned to the new UI, with no ability to opt out.

    We recommend sharing this guide, as well as the resources below, with your users to help them understand the new layout changes.

    For more information on how to add structured data to your rooms and resources, check out the Help Center. Note that this feature will work with both the classic Calendar UI and the new Calendar UI.

     
    Launch Details
    New Calendar web UI, rich formatting for invites, side-by-side “Day” view
    • Automatic rollout option (recommended) to start on Nov. 14, 2017 for Rapid Release and Nov. 28, 2017 for Scheduled Release
    • Manual rollout option available starting today for admins on both Rapid Release and Scheduled Release

    Structured room and resource data

    • Rolling out gradually over the coming weeks for admins on both Rapid Release and Scheduled Release to start uploading

    Editions:
    Available to all G Suite editions

    Rollout pace:
    Extended rollout (potentially longer than 15 days for feature visibility)

    Impact:
    Admins and end users

    Action:
    Admin action suggested/FYI

Reference by Google.com

KRACK WiFi WPA2 security vulnerability threatens all networks

/in

Security researchers have found a devastating flaw in WPA2 WiFi encryption protocol that makes it possible for hackers to intercept your sensitive information. This vulnerability named KRACK (Key Reinstallation Attack) affects Wi-Fi protocol and not a specific product or impentation. An attacker within range of a victim can exploit these weaknesses.

KRACK targets the third step in a four-way authentication “handshake” performed when a WI-FI client attempts to connect to a protected network. This can lead to stealing of information by the attackers including your credit card and confidential data.

To protect against this flaw, major OSes and routers are working round the clock to provide a patch. Apply the patch as soon as possible. Meanwhile, do not share any personal or confidential information on a non secure website and only use secure or HTTPS sites.

Also avoid using free hotspots or use a secure VPN or connection like GajShield Enterprise Cloud, if you must use a Wifi network.

Our research team is working in our labs to gain more information about the latest KRACK attacks and will keep you updated on future course of action. Until then keep a close tab on any latest updates or patches released for your affected products and apply them as soon as possible

 

Reference by gajshield.com