Actions required to prepare for Postini End of Life


Actions required to prepare for Postini End of Life (EOL)


Google Postini EOL


As of June 15, 2015, Google will halt all mailflow through Postini systems. We are sending all migrating customers email notifications regarding steps required to prevent mailflow issues on or after that date. We explain those actions here.

Note for GMD customers: Even if the GMD phase of your transition has not completed, the changes below must be made as Google Apps supports mail filtering and archiving during GMD transition. You’ll continue to have access to your archive until 30 days after your GMD transition completes.

Starting on June 15, 2015, Google will take the following action(s) that will affect your service:

Disable Exchange Journaling through Postini. If you’re a GMD customer using Exchange Journaling, and you haven’t configured your server to forward journal messages to Google Apps Vault, your Journal deliveries will fail and your mail will not be archived.

Temporarily redirect all Postini DNS records for inbound mail to point at Google Apps. If you haven’t migrated to Google Apps, your inbound mail will be rejected. Even if you’ve migrated to Google Apps, you should update your MX records to point to Google Apps to avoid mailflow problems in the future.

Modify Postini Outbound mail routing and DNS records. If you’re a Google Apps customer—They’ll end support for mail routing through Postini Outbound service. Google Apps customers who are still sending traffic to the Postini Outbound service will have their Outbound Gateway setting adjusted to remove Postini Outbound.

If you have a non-Google Apps system—If you have a local mail server configured to use Postini Outbound, they’ll temporarily redirect all Postini DNS records for Postini Outbound to point at the Google Apps SMTP relay service. If you haven’t migrated to Google Apps, your outbound mail will be rejected. Even if you’ve migrated to Google Apps, you should adjust your local server’s configuration so that you’re sending traffic directly to the SMTP relay service, not Postini Outbound, to avoid mailflow problems in the future.

All customers—We highly recommend that you check your SPF records to ensure that they include Google IPs for a better mail filtering experience. Incorrect SPF records could result in your mail being marked as spam by your recipients.

Contact G4Cloud for the right solution to migrate your mail smoothly.

















G4CloudAssist Professional Cloud Services


Hot of the press!






G4CloudAssist our professional services organisation is established to meet future demand for high quality technical cloud skills from Enterprises and Organisations on their journey to the Public Cloud.

G4CloudAssist has created a support structure and method to develop and maintain a Public Cloud Solution.

The methodology represents a Cloud roadmap presenting different stages, like: Assessment/Total Cost of Ownership (TCO) study, Proof of Concept (PoC) and Development, Leverage/Optimize and Maintenance/Managed Service.

The method is called "G4Cloud Optimization Cycle"

More info on our webpage here







G4Cloud accredited as an Amazon Consulting Partner


Latest News!!

G4Cloud|Go For Cloud has been officially accredited by Amazon Web Services as consulting partner.




G4Cloud|Go For Cloud  offers consulting services on the Amazon Web Services (AWS) Public Cloud platform. The professional services are delivered by G4CloudAssist our support organisation.


We support you with:

 Disaster Recovery, Backup and Storage Solutions

 Enterprise Application Integration and Data Migration

 DevOps Solutions

 Big Data Solutions

 Data Warehouse Solutions

 Web Optimization

 Cloud Security

 App Development


G4Cloud|Go For Cloud works closely together with BlazeClan for international customers and we can offer an 24x7x365 Managed Service Solution on AWS.



For more info visit our site