Set Up Hosted Email in Supported Outlook Editions

Use the setup flow for your installed, supported Outlook edition and the actual mailbox provider’s settings. New Outlook and classic Outlook have different interfaces and data-handling behavior. Historical Outlook 2007/2013 screenshots are not current secure-client instructions; those releases are out of support.

Collect verified connection details

Confirm that the mailbox already exists. Obtain its full username, approved authentication method, incoming protocol/server/port, outgoing SMTP server/port and required TLS mode. For cPanel, use Connect Devices. For Webuzo or historical Bread Basket, use the current account’s configuration. Do not assume the web domain is the correct mail hostname.

Open the appropriate add-account flow

In classic Outlook for Windows, start at File > Add Account. In new Outlook, use its settings/account section and Add Account. Follow the provider-specific sign-in prompts. If the offered account type or settings are wrong, use the supported manual/advanced setup rather than repeatedly accepting an incorrect discovery result.

Before connecting a non-Microsoft account through an Outlook edition that syncs it to Microsoft Cloud, review that data handling and your organization’s requirements. Microsoft documents this behavior for new Outlook and certain other Outlook clients; do not assume every edition connects directly with no third-party copy.

Match protocol, encryption and authentication

IMAP is commonly used for synchronized server folders; POP is a deliberate download/retention choice. Common implicit-TLS ports are 993 for IMAP and 995 for POP, not 993 for POP. SMTP submission commonly uses 465 with implicit TLS or 587 with required STARTTLS where offered. Use the exact provider-supported pairing and verify the certificate.

In classic manual settings, configure the outgoing server’s required authentication and the correct sending identity. Where the provider authorizes the same mailbox credentials for SMTP, use them; some providers require OAuth or an app password instead. Do not enable unencrypted login or bypass authentication by adding a client IP to a relay-allow file. The old CentOS/Outlook workaround is not a safe account-setup fix.

Test without risking the only mail copy

Verify both sending and receiving with harmless authorized messages, including replies and sent-folder placement. A successful incoming test does not prove SMTP is configured. Inspect the exact error before changing unrelated accounts or restarting shared services.

A POP “leave a copy on server” option is a retention preference, not an independent backup. Preserve local-only messages, calendars, contacts and profile data before removing or recreating an account. New Outlook removal options can have wider device/cloud effects; read the confirmation rather than treating removal as harmless troubleshooting.

References: Microsoft Outlook account setup and removal, Microsoft Cloud synchronization, Outlook 2007 lifecycle and Outlook 2013 lifecycle.

Reviewed October 15, 2026. Documentation review only; no Windows client, cloud connection, relay authorization or customer mailbox was changed or tested.