Reading time: 8 min · Last verified: August 2026 · SMTPedia editorial team
Cox no longer runs its own consumer mail platform. Residential @cox.net mailboxes were handed to Yahoo Mail, a transition Cox describes as complete since early 2025, and the three server names that every older guide still publishes for Cox residential mail do not resolve any more. Cox Business is a separate service on separate infrastructure and is still live. This page gives both sets of values, with the source for each.
If your mail client still points at imap.cox.net, pop.cox.net or smtp.cox.net, it will never connect again. Those hostnames were retired with the Yahoo migration and no longer exist in DNS. A residential @cox.net address now authenticates against Yahoo servers with a Yahoo app password, not your Cox account password. Cox Business customers on coxmail.com are unaffected and keep their own hostnames.
Cox Hostnames That No Longer Exist
These three names are still repeated across forum threads, migration tools and older setup guides. None of them returns a DNS record today. If a client shows a connection timeout or an “unable to find server” error on a Cox address, this table is usually the whole explanation.
| Retired hostname | What it used to do | Use instead |
|---|---|---|
imap.cox.net | Residential IMAP | imap.mail.yahoo.com |
pop.cox.net | Residential POP3 | pop.mail.yahoo.com |
smtp.cox.net | Residential SMTP submission | smtp.mail.yahoo.com |
Residential Settings for @cox.net Addresses
A @cox.net address keeps working and keeps its name. What changed is the platform behind it: the mailbox now lives on Yahoo Mail infrastructure, so the connection values are Yahoo’s, exactly the ones documented on our Yahoo Mail SMTP, IMAP and POP3 reference. Yahoo publishes a dedicated support article for cox.net accounts confirming these values.
| Protocol | Server | Port | Encryption | Password |
|---|---|---|---|---|
| SMTP (outgoing) | smtp.mail.yahoo.com | 465 or 587 | SSL/TLS | Yahoo app password |
| IMAP (incoming, recommended) | imap.mail.yahoo.com | 993 | SSL/TLS | Yahoo app password |
| POP3 (incoming, single device) | pop.mail.yahoo.com | 995 | SSL/TLS | Yahoo app password |
The username stays your full address, name@cox.net, not a Yahoo address. Only the password changes: Yahoo requires an app password for third-party clients and rejects the regular account password on IMAP, POP3 and SMTP. Generate it from the Yahoo account security page, paste it into the client’s password field, and use a distinct one per device rather than sharing a single string. The rules behind the encrypted ports are the same everywhere; if a value here is unfamiliar, our SSL and TLS setup guide for mail clients explains what each one negotiates.
Most people hit the password wall before they hit the hostname wall. A client that still holds the old Cox password will return an authentication rejection rather than a DNS error, which sends users looking for the wrong problem. If you see a 503 authentication required response or a 550 5.7.1 rejection on send, change the password field to an app password before touching anything else.
Cox Business Settings for coxmail.com Accounts
Cox Business email was never part of the Yahoo transition. It runs on its own platform and Cox still documents its hostnames in the business support section. The values below come from Cox Business setup articles for iOS and macOS.
| Protocol | Server | Port | Encryption | Authentication |
|---|---|---|---|---|
| SMTP (outgoing) | smtp.coxmail.com | 465 | SSL/TLS | Required, full email address |
| IMAP (incoming) | imap.coxmail.com | 993 | SSL | Required, full email address |
| POP3 (incoming) | pop.coxmail.com | 995 | SSL | Required, full email address |
Cox Business documents 465 with SSL for outgoing mail and states that the outgoing settings are identical whether the incoming side is POP or IMAP. The username is the entire address, which is the one behaviour Cox itself flags as different from the old residential setup. For the general trade-off between the two incoming protocols on any provider, see our IMAP configuration reference and its POP3 counterpart on server retention.
Two domains commonly listed as Cox email domains are not. coxwest.net returns no DNS record at all. cableone.net belongs to Cable One, which trades as Sparklight and is a separate company with no relationship to Cox Communications. Neither belongs in a Cox settings table, and we have removed both from this page.
What Changed, and When
Cox announced at the end of 2023 that it would stop operating its own webmail and move remaining cox.net users to Yahoo Mail. Cox’s own transition page states the move was complete as of early 2025. In practice this means three things for anyone configuring a client today.
- The mailbox is a Yahoo mailbox wearing a cox.net address. Folder behaviour, storage quota and spam handling follow Yahoo, not Cox.
- Password resets and account recovery happen through Yahoo, not through the Cox account portal. This is the single most common source of confusion in the Cox community forums.
- Cox is no longer the sender. Outbound mail leaves Yahoo infrastructure and inherits Yahoo’s sending reputation and its bulk sending rules, which we cover in the Google, Yahoo and Microsoft bulk sender requirements guide.
Cox is not alone in this. The pattern of a cable or telephone company keeping the address and outsourcing the platform now covers most of the large US providers, which is why a hostname that follows the brand name is so often wrong. Spectrum keys its server on the domain rather than the brand, AT&T runs on Yahoo infrastructure behind a Secure Mail Key, and Comcast is one of the few still operating its own mail servers. Our index of still-active legacy consumer domains tracks which brand sits on which platform.
Diagnosing a Cox Address That Will Not Connect
The error a client reports tells you which of the two changes you have not applied yet. Work through them in this order rather than rebuilding the account from scratch, which loses local folders for no reason.
“Cannot find server” or a connection timeout
The hostname is one of the retired cox.net names. Nothing is listening because nothing resolves. Replace the incoming and outgoing server fields with the Yahoo values, then retest before changing anything else.
Repeated password prompt, or “the server rejected your credentials”
The hostname is right and the password is the old Cox one. Generate a Yahoo app password and paste it in. A password manager that keeps autofilling the old value is a common cause of this loop repeating after a correct fix.
Mail arrives but sending fails
The incoming side was updated and the outgoing side was not. Mail clients store the SMTP server separately, and some keep a list of outgoing servers shared across accounts, so the old entry survives an otherwise complete edit. Check the outgoing server list explicitly.
Sending fails only on one network
This is not a Cox or Yahoo problem. Some corporate networks and mobile carriers block outbound port 587 while leaving 465 open. Both ports are documented for this mailbox, so switch to 465 with implicit SSL and retest on the same network.
If sending still fails after all four, read the actual rejection text rather than the client’s paraphrase of it. The three digit reply and its enhanced status code name the cause precisely, and our SMTP reply code directory maps each one to the setting that produces it.
Moving a cox.net Mailbox Elsewhere
Because the mailbox is a standard Yahoo IMAP mailbox, any normal IMAP migration works. Configure the cox.net account with the Yahoo values above in a desktop client, add the destination account alongside it, and copy folders across. Thunderbird handles this well because it exposes both accounts as ordinary IMAP trees.
Two cautions. First, the app password is required for the migration session as well; wizards that ask for “your email password” will fail silently or loop on authentication. Second, do not delete the cox.net account once the copy finishes. Keep it receiving and set up forwarding to the new address until you are confident nothing important still routes there, and be aware of the alignment pitfalls forwarding introduces.
IMAP, POP3 and SMTP Integration into Gmail
Configure Gmail with external IMAP/POP3/SMTP to send/receive emails from your custom domain through Gmail’s interface. Perfect for professionals managing multiple accounts in one place.
- Google Account β Security β App passwords (2-Step Verification must be enabled).
- Generate App Password for “Mail” β copy 16-character password.
- Gmail β Settings β See all settings β Forwarding and POP/IMAP.
- Enable IMAP β Save Changes.
- Incoming (IMAP):
[IMAP SERVER]:993 SSL| Outgoing (SMTP):[SMTP SERVER]:587 STARTTLS. - Use your full email + App Password (not regular password) for authentication.
β Gmail Result: Send/receive custom domain email directly in Gmail interface with full search/folder integration.
WordPress SMTP Plugin Configuration (WP Mail SMTP + MailPoet)
Configure SMTP in WordPress to fix email delivery issues and prevent spam folder placement. WP Mail SMTP and MailPoet ensure reliable transactional emails, contact forms, and newsletters deliver successfully.
- Install and activate WP Mail SMTP or MailPoet plugin from your WordPress dashboard.
- Navigate to WP Mail SMTP β Settings or MailPoet β Settings β Sending tab.
- Select “Other SMTP” as your mailer method from the dropdown.
- Enter SMTP settings with Port
587and STARTTLS encryption (when available). - Input your full email address and password in the authentication fields.
- Click Save Settings and send a test email to verify the configuration works.
β Result: WordPress contact forms, user registrations, and newsletter emails now deliver reliably via your SMTP server.
This configuration includes these plugins and tools within WordPress:
- HappyForms
- Elementor Forms
- Gravity Form
- WooCommerce Checkout Form
- Contact Form by BestWebSoft
- Fluent Forms
- Contact Form 7
- WPForms
- Ninja Forms
- Default WordPress Reg Form
- Forminator Forms
- Formidable Form
- WordPress Comment Form
- Mail Mint Form
Thunderbird OAuth2 Email Setup (IMAP + SMTP)
Secure IMAP & SMTP using OAuth2 token authentication in Thunderbird. This modern method eliminates password storage for enhanced security.
- Open Thunderbird β Account Settings β Account Actions β Add Mail Account.
- Enter your email address and click Continue to begin setup.
- Select IMAP protocol and choose OAuth2 authentication method.
- Thunderbird opens a browser window β log in to your provider β Grant access permissions.
- Automatic configuration applies: Incoming: use the IMAP server address from the settings table above, port 993, SSL
- Click Done β Thunderbird begins syncing folders and emails immediately.
OAuth2 advantage: Token-based authentication enhances security over traditional password methods while maintaining full functionality.
Outlook IMAP, POP3 & SMTP Setup (Auto + Manual)
Outlook configuration supports both automatic server detection and manual IMAP/POP3/SMTP settings for complete control over your email setup.
π Auto Setup (Recommended):
- Go to File β Add Account β Enter your email address + password.
- Outlook automatically detects IMAP, POP3, and SMTP server settings.
- Click Connect β setup completes in approximately 30 seconds.
βοΈ Manual Setup (Advanced Users):
- Authentication: Use your full email address + password for both servers
BlueMail Two-Factor Authentication + OAuth2 Setup
BlueMail security setup combines OAuth2 authentication with two-factor authentication (2FA) for maximum account protection.
- Open BlueMail β Account Settings β Security β Enable Two-Factor Authentication.
- Link your phone number or authenticator app for 2FA verification codes.
- Add email account β Choose OAuth2 or manual server configuration.
- Enter server details from the table above
- Complete login with 2FA code β enhanced security layer activated.
Apple Mail IMAP Configuration (iCloud + Manual)
Setup IMAP in Apple Mail for seamless synchronization across Mac, iPhone, and iPad devices with full folder support.
- Open Apple Mail β Mail β Add Account β Other Mail Account.
- Enter your name, email address, and password β click Continue.
- Select IMAP account type β Incoming server.
- Next: Outgoing server
- Click Sign In β Mail verifies settings and begins folder synchronization.
iOS Mail App Setup (iPhone/iPad)
iPhone/iPad Mail configuration syncs IMAP folders across all Apple devices with native push notifications.
- Go to Settings β Mail β Accounts β Add Account β Other.
- Enter name, email, password β Next.
- Account Type: IMAP β Incoming:
[IMAP SERVER]Port993SSL. - Enter your outgoing SMTP server and port.
- Next β Save β iOS verifies and syncs immediately.
Push enabled automatically: new emails appear instantly on Lock Screen.
Android Mail App Configuration
Android Gmail/Email app setup works with any IMAP/SMTP provider for native device integration.
- Go to: Settings β Accounts β Add Account β Email (or Gmail app).
- Enter email + password β Next.
- Account Type: IMAP
- Outgoing server details β Require authentication.
- Next β Sign In β Android syncs contacts/calendar if enabled.
Sync interval: 15min default (battery optimized) – change in Account Sync settings.
eM Client Manual IMAP & POP3 Sync Configuration
Configure your email settings on eM Client with either automatic setup or through precise IMAP/POP3 server settings for reliable email synchronization and full folder support.
- Click New Account β Mail
Authentication requires full email address + password for both incoming and outgoing servers.Click Next β Finish β Send/Receive All Folders to begin synchronization.
Mailbird OAuth2 IMAP & SMTP Integration
Secure Mailbird setup using OAuth2 authentication eliminates password storage while providing full IMAP/SMTP functionality.
- Mailbird β Add Account β Enter your email address to begin.
- Choose Manual Setup β OAuth2 authentication method from options.
- Browser opens your provider’s login page β enter credentials β Authorize Mailbird.
- Mailbird receives access token and automatically configures IMAP/SMTP servers.
- Setup completes β full email synchronization begins automatically.
Mailspring OAuth2 IMAP Configuration
Mailspring OAuth2 setup provides secure email access without storing passwords directly in the application.
- Add new email account β Select Custom IMAP configuration option.
- Incoming
IMAP SERVERand outgoingSMTP SERVER. - Mailspring prompts OAuth2 authorization via browser window for secure login.
- Log into your provider account and grant Mailspring access permissions.
- Mailspring automatically manages authentication tokens β seamless email access established.
Postbox Manual IMAP Synchronization
Postbox IMAP setup with manual synchronization control for precise email folder management and immediate updates.
- Add IMAP account β Enter IMAP Server details.
- Outgoing SMTP with full email authentication.
- Postbox connects and displays folder structure automatically.
- Right-click any folder β Get Messages for immediate manual synchronization.
- Manual sync updates local mailbox instantly with server changes (read status, deletions, organization).
SendBlaster SMTP Configuration (Bulk Email)
Bulk email SMTP configuration in SendBlaster requires precise server authentication for reliable campaign delivery.
- Open SendBlaster β Settings β SMTP Configuration section.
- Enter SMTP Server and Port: do not forget to Enable TLS encryption.
- Authentication: Your full email address + password (required).
- Click Test Connection β verify green success indicator appears.
- Save settings β SendBlaster ready for bulk email campaigns and newsletters.
MailJerry IMAP Real-Time Synchronization
MailJerry IMAP setup enables real-time access to email folders stored on your provider’s server across all devices.
- Incoming Server and encryption required.
- Authentication: Full email address + password for secure connection.
- Enable real-time folder synchronization settings in MailJerry preferences.
- Folders update instantly with new messages, read status, and deletions across devices.
Clean.email OAuth2 Synchronization Setup
Clean.email OAuth2 setup provides secure mailbox access without sharing passwords directly with the application.
- Add new account β Select OAuth2 authorization method.
- Your provider opens login portal β enter credentials securely.
- Grant Clean.email permissions for email read/write access.
- OAuth2 token enables real-time message management, filtering, and organization.
- Setup complete β Clean.email maintains secure, ongoing mailbox synchronization.
Common IMAP/POP3/SMTP Troubleshooting
- Authentication failed: Always use your complete email address, never just the username portion.
- Port blocked by ISP: Try alternative SMTP port as fallback.
- SSL certificate errors: Ensure certificate validation is enabled in client settings.
- Slow or no IMAP sync: Check folder subscriptions and enable all folders in client settings.
More Popular Email Settings Guides
| Guide | Region | Type |
|---|---|---|
| T-Online.de SMTP Settings | π©πͺ Germany | ISP |
| Fibertel.com.ar Webmail | π¦π· Argentina | ISP |
| QQ Mail SMTP Server | π¨π³ China | Global |
| Volny Mail Settings | π¨πΏ Czech Republic | ISP |
| Freemail.hu IMAP Settings | ππΊ Hungary | Regional |
| Etisalat/EIM Mail Settings | π¦πͺ UAE | ISP |
| Hotmail IMAP Settings | π Global | Global |
| 126.com IMAP Server Settings | π¨π³ China | Regional |
| Waoo Mail SMTP/IMAP | π©π° Denmark | ISP |
| GMX SMTP Server Settings | π Global | Global |
| 163.com IMAP Server Settings | π¨π³ China | Regional |
| Webmail.co.za IMAP Settings | πΏπ¦ South Africa | Regional |
Frequently Asked Questions
What happened to my cox.net email?
Cox stopped running its own mail platform and moved residential cox.net mailboxes to Yahoo Mail. Cox states the transition was complete as of early 2025. The address still works and still ends in cox.net; the servers behind it are Yahoo’s, and the old cox.net hostnames were retired.
Why is my Cox email not working in Outlook or Apple Mail?
Almost always one of two reasons. The client still points at imap.cox.net, pop.cox.net or smtp.cox.net, which no longer resolve, or it still holds the old Cox password, which Yahoo rejects. Repoint the servers to imap.mail.yahoo.com, pop.mail.yahoo.com and smtp.mail.yahoo.com, then replace the password with a Yahoo app password.
What are the IMAP settings for Cox email?
For a residential @cox.net address: imap.mail.yahoo.com, port 993, SSL/TLS, username is the full cox.net address, password is a Yahoo app password. For a Cox Business account: imap.coxmail.com, port 993 with SSL, username is the entire email address.
Do Cox Business accounts use the same servers as cox.net?
No. Cox Business email was not part of the Yahoo migration and keeps its own hostnames on coxmail.com: imap.coxmail.com on 993, pop.coxmail.com on 995, and smtp.coxmail.com on 465 with SSL. Cox notes that the username on business accounts is the entire email address, which differed from the old residential behaviour.
How do I move my Cox email to Gmail?
Gmail’s import wizard can add the account as a standard IMAP source using imap.mail.yahoo.com on 993 with a Yahoo app password. If the wizard refuses the credentials, it is the app password that is missing, not the hostname. A folder-by-folder copy in Thunderbird is the reliable fallback for large mailboxes.
Can I still get a new @cox.net address?
No. Cox stopped offering email to new customers before the Yahoo migration, and the transition covered existing mailboxes only. Providers in this position are tracked in our reference on discontinued and successor-hosted email services.
About This Guide
The residential values on this page were verified in August 2026 against Cox’s own cox.net transition notice and Yahoo’s support article for cox.net accounts in third-party clients. The Cox Business values were verified against Cox Business setup documentation for iOS and macOS. The three retired cox.net hostnames were checked directly and return no DNS record. We deliberately do not publish a figure for mailbox storage or attachment limits here, because those now follow Yahoo and Cox no longer documents them. Related references: the protocol and port matrix, the general SMTP client setup guide, and the timeline of discontinued email services. If Cox or Yahoo changes a value, report it and we will update the reference.
About the Author
Alaa Β· LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. Iβve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
