Scheduled message cleanup

#The amount of messages with which a typical user may interact in a given day is ever increasing. For example, a user may receive a multitude of emails that vary in an amount of importance to a recipient of the emails. The user, for instance, may receive work emails and personal emails in an account. The user may also receive emails that are sent periodically from a sender that may have varying degrees of interest to the user, such as newsletters, offers for sale, and so on.

#However, traditional techniques that were employed to interact with the messages generally did not differentiate between these messages. Consequently, a user was often forced to navigate through each of the messages using traditional techniques to locate a particular message of interest. This could be both time consuming and frustrating to the user especially when considering the vast number of emails and other messages even a typical user may receive in a day.

#Scheduled message cleanup techniques are described. In one or more implementations, a method implemented by one or more computing devices includes detecting that a message has been received from a sender for delivery via a user account. Responsive to a determination that an option has been selected for the sender in association with the user account, a previous message from the sender that is to be delivered via the user account is removed and the detected message is kept for delivery via the user account.

#The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items.

#FIG. 1 is an illustration of an environment in an example implementation that is operable to employ scheduled message cleanup techniques.

#FIG. 2 is an illustration of an example of a user interface of FIG. 1 as configured to cause output of a menu to schedule cleanup of one or more messages.

#Overview

#Users have access to a variety of different messages. However, some of these messages may have varying degrees of importance to the user. For example, a more recent email from a sender may supersede one or more previous emails from the sender. Consequently, the previous emails may add to the clutter of a user interface designed to provide interaction with the emails.

#Scheduled message cleanup techniques are described. In one or more implementations, options are provided that may help to manage which messages (e.g., emails) are available for output in a user interface. For example, the user interface may include an option to automatically remove previous emails from a sender upon receipt of a more recent email from the sender. A user, for instance, may set this option for a sender of a newsletter such that a most recent version of the newsletter is available via the user interface but previous versions are not.