dotMobi Switch On! Email Guide

Version 1.0
Revision 1
Status External Draft
Date 25-September-2006
Editors Ronan Cremin

1. Document Information

1.1 Status

This document has the status "External Draft". The lifecycle of the dotMobi Switch On! Guide is discussed in [Lifecycle]

1.2 Time Limits

There are no time limits associated with compliance to this document.

1.3 Document History

This is the first draft of this document. The document will be updated from time to time. DotMobi registrars will be notified when the document is updated.

The latest version of this document is available at:

This version can be found at

1.5 References

dotMobi Switch On! Guide Lifecycle
RFC822 - Standard for the Format of ARPA Internet Text Messages
RFC1939 - Post Office Protocol (POP) Version 3
RFC2449 - POP3 Extension Mechanism
RFC2060 - Internet Message Access Protocol - Version 4rev1
Sender Policy Framework

1.6 Copyright

This document contains information proprietary to Mobile Top Level Domain Limited ("mTLD" or "dotMobi"). You may not modify, copy, reproduce, republish, upload, post, transmit, or distribute in any way any material from this document including code and software without the express, written consent of mTLD.

This document as a whole is copyrighted as a collective work, and individual works appearing on or accessible through this document are likewise subject to copyright protection. You agree to honor the copyrights in this document (including the selection, coordination and arrangement of the contents of this document) and in the works available on or through this document. In addition, trademarks and tradedress belonging to us or to third parties appear on this site or are accessible through this site. The fact that we have permitted you access to this site does not constitute authorization to reproduce such trademarks for any other purpose.

Copyright © 2006 Mobile Top Level Domain Limited

2. Overview

2.1 Purpose of Switch On! Guides

DotMobi Switch On! Guides are a set of guides governing certain technical protocols and services in the ".mobi" (dotMobi) domain. These guides are a combination of mandatory rules and optional best practices that, when applied to content and services associated with the domain, ensure a good user experience for users interacting with the domain and associated services via a mobile device. The rules mentioned in Switch On! Guide documents are specifically designed to be:

DotMobi Switch On! Guides are primarily oriented at domain registrants, since registrants are the owner of and content and services hosted at any domain, but are also useful for tool vendors and solution providers whose products and services may be involved with dotMobi.

2.2 Mandatory Rules Audit, Notification & Enforcement Process

DotMobi domain name registrants agree to implement the mandatory registrant rules listed in this document whenever they publish a web site linked to a dotMobi name on the internet. It is strongly recommended that registrants also ensure that their applications also comply with the Highly Recommended Best Practices to improve the end-user experience.

2.3 Registrar's Obligations

Registrars are obliged to make registrants aware of all Switch On! Guides associated with the dotMobi domain in advance of any registration taking place. Registrars must either make a copy of these documents available to the registrant or point them to the authoritative versions on the web site.

3. Introduction to Switch On! Email Guide

3.1 Scope

The dotMobi domain is intended as a sign to users that email services associated with the domain are especially suitable for use on mobile devices. Service providers are expected to make sure that their dotMobi email service works well with mobile devices. Following the guidelines in this document will assist them in doing this.

This document is the authoritative source of rules governing public email services hosted on a dotMobi domain. A public email service is an email service that offers email accounts to the general public either as a free or paid-for service. These rules are designed to ensure a good user experience for users using dotMobi email services on their mobile devices.

The provisions in this guide apply to email systems that support RFC-822 in their interaction with other email systems where a .mobi email address is either the originator or recipient or both of an email. These best practices do not make any statement about the mailbox protocol used between the email user agent and server.

3.2 Use Cases Covered

The Switch On! Email Guide covers the use case of interacting with a dotMobi email service from a mobile phone, PDA or other hand-held device. This guide specifically does not cover use cases involving desktop PCs or other device types, nor does it cover other Internet-based applications such as browsing or instant messaging.

3.4 Structure of the Best Practices

DotMobi-specific best practices are identified as follows:

The text of a dotMobi rule or best practice.

Best practices are ranked in order of desirability.

4. Registrant Mandatory Requirements

4.1 Self-Declaration of Supported Functions

Service providers running publicly available services on a dotMobi domain, either as a free or paid service, must make a declaration of their supported email functions in a form on the mTLD website.

4.1.1 What it Means

In order to help users find appropriate email services to fit their needs, mTLD will provide a directory of dotMobi-compliant public email services on the mTLD website. For each service provider listed, the claimed features from the Registrant Best Practices supported by the service will be enumerated in a searchable directory. Service providers that are found not to live up to the claimed features may be removed from this directory.

5. Registrant Best Practices

5.1 Interoperability with Standards-Based Internet Email Systems

Services should support bi-directional interoperability with standards-based internet email systems.

5.1.1 What it Means

Users of a dotMobi email service should be able to send email to, and receive email from any other internet email service that supports RFC-822 in its interaction with external mail systems, subject to the other best practices mentioned in this document. RFC-822 is supported by a very large number of open source and commercial email servers. Furthermore, most proprietary email systems can be configured to communicate with RFC-822 compatible email systems via a gateway.

5.2 Automated Delivery of Email

Services should support a means for delivering a configurable selection of new emails to the user's mobile device in a timely and automated manner.

5.2.1 What it Means

There are several techniques by which this can be achieved including push email and regular polling. In the polling paradigm, the client contacts the message store on a regular basis to find out if new emails have arraved and, if so, retrieve them to the mobile device. In the push paradigm the mail server will indicate to the mobile device the arrival or availability of new messages, and subsequently initiate delivery of these emails to the mobile device.

When choosing a technique, service providers should have a regard to the timeliness, cost and use of network bandwidth.

5.3 New Email Notification

Services should support a means for alerting the user of the arrival at the server of all or a subset of incoming emails.

5.3.1 What it Means

New email notification means that there is some method in place by which the email service can notify the user's mobile device that there are new emails waiting on the server. New email notification is especially valuable in the mobile context where people are likely to be on the move, and not actively monitoring their inboxes. Furthermore, this event-driven use of mobile email fits the established pattern for existing mobile messaging systems such as SMS and MMS.

When choosing a technique, service providers should have a regard to the timeliness, cost and use of network bandwidth. Service providers should also ensure that the email notification algorithm is sensitive to whether or not an email has already been pushed to the mobile device.

5.4 Spam Protection

Services should offer a method for marking spam.

5.4.1 What it Means

Unsolicited bulk email is serious problem with existing desktop-email services and is even more acute and intrusive on a mobile-oriented email service due to personal nature of mobile devices, and their ability to interrupt you. For this reason, services should offer spam protection tools to reduce the impact of this problem.

5.5 Delivery Configuration

Services should support the configuration of criteria that support selective delivery of messages to the mobile device.

5.5.1 What it Means

Delivery configuration allows users of the email service to configure rules to ensure that only the most relevant emails are delivered to their mobile devices, to make the best use of the mobility premium offered by a mobile email service. Delivery configuration should offer the ability to selectively restrict emails delivered to the mobile device based on attributes within messages. The following criteria should be supported:

5.6 Sending User Authentication

Services should individually authenticate the senders of emails from their domain(s) and ensure that originator addresses of emails from their domain(s) match the authenticated sender.

5.6.1 What it Means

Sending user authentication means putting in place practices to ensure that the originator of an email can be trusted. Sending user authentication has two distinct components:

  1. Ensuring that any user who sends email from the service is authenticated before they are allowed to use its services. This helps to solve the problem of open relays, where a person or process can send an email through an email server without any form of authentication. Open relays are a major contributer to the spam problem.
  2. Ensuring that originator addresses in emails can be trusted so that that email address masquerading does not take place. This helps to ensure that people can trust that an email is really from the claimed address

5.7 Sending Server Authentication

Services should provide a means to allow themselves to validated as an email server for their domain(s) and should validate that the originating server for email is a valid originating server for the domain of the sender.

5.7.1 What it Means

Sending server authentication means that a trusted party has validated that the originating server for an email message is the correct originating email server for that domain, as opposed to another server masquerading as such. Sending server authentication allows for large volumes of spam messages to be filtered without further processing, since spam messages often falsely claim to originate from legitimate email addresses but sent from a non-authoritative email server.

5.8 Alternative Access to Mailbox

Services should provide alternative modes of access to mailboxes.

5.8.1 What it Means

Services should provide a means for users to access their email in a way that does not require the mobile device. This allows users to view their email when they are unable or unwilling to use their mobile device, and also allows users to view emails that they have chosen not to have delivered to their mobile device and manage other aspects of the mobile email service.

5.9 Adaptation of Incoming Emails

Services should offer the option to adapt incoming emails before delivery to the mobile device in such a way as to make them work better on these devices.

5.9.1 What it Means

Email messages that are delivered to the mobile device should be formatted such that they work well in this context. There are a number of ways in which this can be done including reformatting or removal of attachments and dividing large emails into smaller pieces.

Valid XHTML 1.0 Transitional