Email Objects allows you to add an email address where it is treated like a domain with its own policy assignments and delivery options. This option is useful when a single email address requires rules that are not normally allowed.
For example, domain example.com has a policy set that does not allow .zip files. However, firstname.lastname@example.org need to receive these .zip files. You can create a custom file policy and assign that to an object policy for email@example.com. This will allow firstname.lastname@example.org to receive the .zip files while it remains restricted for all other users.
Email Objects can also be used for custom routing. For example, email for example.com is normally routed to the IP address 172.16.10.25, but email@example.com requires his email be routed to a different server of 10.10.0.25.
*Adding an Email Object consumes one license per entry just as if it were a domain.