The Google Apps Email Audit API allows Google Apps administrators to audit a user’s email, email drafts, and archived chats. In addition, a domain administrator can retrieve account login information and download a user’s mailbox. This API only applies to Google Apps for Business, Education, and ISPs accounts. It is not used with a Google Apps or Gmail account not hosted by the Google Apps products.
Administrators can download mailbox accounts within their domain for audit purposes. To prepare a mailbox for export, the Email Audit service creates an encrypted copy of a user’s mailbox. When the export preparation is completed, the system returns the URLs to the encrypted mailbox files which, when downloaded and decrypted, are available in mbox format.
The downloading steps are:
- Upload a public key
- Create an export version of a user’s mailbox
- Retrieve the mailbox download status
Upload a public key:
The administrator provides a public encryption key for downloading mailboxes. The creation of this public key is only done once.
Steps for generating public key :
1. install GNUPG
2. run gpg –gen-key –expert to generate a new key, selecting option 8 “RSA (set your own capabilities)” and toggling the sign capability.
3. accept all default options to complete the key generation process.
4. run gpg –armor –export to export the key. Please make sure you are only exporting the single key you just generated.
5. visit http://www.motobit.com/util/base64-decoder-encoder.asp to base64-encode the key. Double check you are copying all the lines, including the header and not adding any extra line.
After creation of public key, now we will upload public key.
To upload the public key, start by creating an XML entry with the base64 encoded public key as shown in the example below:
Send an HTTP POST request to the ‘publickey’ feed URI in your Google Apps domain:
If successful, the server returns a 201 CREATED status code.
Let’s take code example for uploading a public key.
Create an export version of a user’s mailbox:
To prepare a copy of a user’s mailbox for export and downloading, use the Email Audit API’s export feed.
Send a POST request to the export feed’s URI.
If successful, the server returns a `201 CREATED` status code
There are 5 properties in xml entry which are as:
beginDate – The beginDate is the date for the first email included in the exported mailbox. This is an optional element. If you want all emails starting from when the account was created, do not enter a value for this field.
endDate – The endDate is the date for the last email included in the exported mailbox. This is an optional element. If the endDate is not specified or an empty string, the exported emails go up to the current date.
searchQuery – The mailbox is filtered using this searchQuery value and only the filtered search results will be available for download. This is an optional element.
includeDeleted – The includeDeleted parameter determines whether or not deleted messages are included in the mailbox export file. This is an optional element
packageContent – It determines whether the full email or the email’s header are used in the mailbox export file.
FULL_MESSAGE — The full email text, including attachments, is copied to the export file. This is the default setting for the packageContent element.
HEADER_ONLY — Only the email’s header is copied to the export file.
Let’s take example code :
Note : In above code, downloadMailBox(userID) function again called in catch block. Because some times it gives time out error and control shifts towards catch block. In catch block, we are calling it again. So after retrying 2 or 3 times, it successfully executes.
Retrieve the mailbox download status :
Use the mailbox export request ID to get the status of the pending request. Once the mailbox is copied and prepared for export, the response returns a status of COMPLETED along with the list of encrypted mailbox files as HTTP URLs. Use this set of URLs to download the mailbox files.
To retrieve status details for a mailbox prepared for export, send an HTTP GET request with the mailbox’s requestId to the export feed’s URI
These are the possible values of status :
PENDING – The request is being processed.
ERROR – The request failed due to some error.
COMPLETED – The request has been processed completely and the encrypted mailbox files are ready for download.
MARKED_DELETE – The request is marked for deletion next time the Google cleanup job runs.
DELETED – The mailbox files were successfully deleted by the admin
EXPIRED – The mailbox files were deleted by Google after the 3 week retention limit.
Lets take a code example
To learn more about Email Audit API, see documentation
Hello,
I’ve successfully followed the tutorial but I have provided authentication failed to load the public key, but only for that function yet for all monitors an account authentication is successful.
In both functions use the same form but I login via oauth to load the public key fails.
function cargarClavePublica(){
var dominio = “demotiga2.com”;
var base=’https://apps-apis.google.com/a/feeds/compliance/audit/’;
var xmlRaw=
”+
”+
”;
var name = “audit”;
var fetchArgs = {oAuthServiceName:name, oAuthUseToken:’always’, method:’POST’, payload:xmlRaw, contentType:’application/atom+xml’, muteHttpExceptions: true};
var oAuthConfig = UrlFetchApp.addOAuthService(name);
oAuthConfig.setRequestTokenUrl(“https://www.google.com/accounts/OAuthGetRequestToken?scope=”+base);
oAuthConfig.setAuthorizationUrl(“https://www.google.com/accounts/OAuthAuthorizeToken”);
oAuthConfig.setAccessTokenUrl(“https://www.google.com/accounts/OAuthGetAccessToken”);
oAuthConfig.setConsumerKey(KEY);
oAuthConfig.setConsumerSecret(SECRET);
var url = base+’publickey/’+dominio;
Logger.log(url);
var urlFetch;
var status;
try{
urlFetch = UrlFetchApp.fetch(url,fetchArgs);
status = urlFetch.getResponseCode();
Logger.log(status);
}
catch(e){
Logger.log(“No se pudo cargar la clave pública : ” + e.message);
}
return status;
}
function cargarClavePublica(){
var dominio = “demotiga2.com”;
var base=’https://apps-apis.google.com/a/feeds/compliance/audit/’;
var xmlRaw=
”+
”+
”;
var name = “audit”;
var fetchArgs = {oAuthServiceName:name, oAuthUseToken:’always’, method:’POST’, payload:xmlRaw, contentType:’application/atom+xml’, muteHttpExceptions: true};
var oAuthConfig = UrlFetchApp.addOAuthService(name);
oAuthConfig.setRequestTokenUrl(“https://www.google.com/accounts/OAuthGetRequestToken?scope=”+base);
oAuthConfig.setAuthorizationUrl(“https://www.google.com/accounts/OAuthAuthorizeToken”);
oAuthConfig.setAccessTokenUrl(“https://www.google.com/accounts/OAuthGetAccessToken”);
oAuthConfig.setConsumerKey(“demotiga2.com”);
oAuthConfig.setConsumerSecret(“F3FMHUED68LImercuczNnYME”);
var url = base+’publickey/’+dominio;
Logger.log(url);
var urlFetch;
var status;
try{
urlFetch = UrlFetchApp.fetch(url,fetchArgs);
status = urlFetch.getResponseCode();
Logger.log(status);
}
catch(e){
Logger.log(“No se pudo cargar la clave pública : ” + e.message);
}
return status;
}
var xmlRaw= “”+
“”+
“”;
Does the “includeDeleted” parameter used for mail box export include permanently deleted mails or the mails in trash folder ?
Anybody read this posting? If so reply, I need some help badly.
A common input wireless display screenn foor dismounted Soldier applications woulpd be an ability enabler.