Rackspace Email FAQ

The maximum size of a Rackspace Email box is 25 GB.

The maximum size for an attachment in the Rackspace environment is 50 MB.

You can find instructions for this in Add a signature to Rackspace Email.

You can find instructions for this in Add an alias with Rackspace Email.

You can create an unlimited number of group lists. Each group list can have an unlimited number of internal recipients and a maximum of 250 external recipients.

You can view and manage your email at Webmail Login.

A Rackspace Email user can change their password through Webmail Login. For more information, see Change a Rackspace Email mailbox password.

The main difference between IMAP and POP is that IMAP works with email directly on the server, while POP fetches mail from the server and works with it on your local computer. For more information, see IMAP and POP mail protocol comparison.

We strongly recommend using an IMAP connection with Rackspace Email.

You can view your billing invoice through the Cloud Office Control Panel. After you log in, click **My account** in the upper-right corner and select **Billing**. Then, click **Invoice** on the left-hand side of the page. You can then select any of your past invoices to view their history.

No worries. Just call our main support line so we can direct you to your dedicated support team for help: 1 800 961 4454.

For instructions, see Manage email administrators with the Cloud Office Control Panel.

Log in to your control panel and click the **Support** menu at the top of the screen. From the menu, select **Tickets**. To create a new ticket, click **New Ticket** and fill out the information describing your request or issue and submit. You can also view the history of your most recent tickets.

To view the Cloud Office system status, go to System Status.

Transport Layer Security (TLS) and its predecessor, Secure Socket Layer (SSL), are cryptographic protocols that provide security for communications over networks. TLS and SSL encrypt the segments of network connections at the application layer to ensure secure end-to-end transit at the transport layer. For our purposes, they create an encrypted tunnel through which we send plain text emails.

Cloud Office servers, by default, attempt a TLS connection for both in and outbound email. For outgoing mail (any of our servers sending to external MX servers), we perform TLS if the remote server advertises it. When performing outgoing TLS, our servers are permissive with the certificate. In other words, if the site is using an untrusted or self-signed certificate, as long as it is a working certificate, we should still accept it.

Our outgoing SMTP servers use TLS in an opportunistic fashion.

This means that our servers attempt to open an SMTP transaction with the recipient server by using TLS. If TLS cannot connect successfully, the communication defaults back to an unencrypted transmission of the data, also referred to as *PLAINTEXT*.

Our servers respond to TLS and SSL requests to send mail to us encrypted.