Rackspace Email IMAP and SMTP settings
Rackspace Email (not Exchange) uses secure.emailsrvr.com for both IMAP and SMTP, which surprises a lot of migrations.
secure.emailsrvr.comport 993 · SSL/TLS
secure.emailsrvr.comport 465 · SSL/TLS
Username
your full email addressConnect in three steps
- 1
Use the full address as the username.
- 2
Rackspace Exchange mailboxes use different endpoints — check which product the domain is on.
What usually breaks
Rackspace Email and Rackspace Exchange are different products with different hosts.
The same hostname serves IMAP and SMTP; the port selects the protocol.
Resolve it instead of hardcoding it
A custom domain on Rackspace Email has the same MX infrastructure as the consumer product. That is what mailintel reads.
import { mailintel } from "mailintel";
const result = await mailintel("[email protected]");
result.provider; // "rackspace"
result.connection.imap; // { host: "secure.emailsrvr.com", port: 993, security: "tls" }
result.connection.smtp; // { host: "secure.emailsrvr.com", port: 465, security: "tls" }
result.connection.username; // "[email protected]"What is Rackspace Email's IMAP server?+
secure.emailsrvr.com on port 993 using SSL/TLS. The username is the full email address.
What is Rackspace Email's SMTP server?+
secure.emailsrvr.com on port 465 using SSL/TLS. Most clients also accept the alternate submission port with STARTTLS.
Does Rackspace Email need an app password?+
Not necessarily — a regular mailbox password works, though a dedicated app password is still a good idea if the provider offers one.