Email Settings Email Settings Guide

Verizon.net Email Settings: IMAP, SMTP and POP3

Every server, port and password step for @verizon.net addresses in Outlook, Apple Mail, Thunderbird or your phone. Copy each value with 1 tap. Your 3 servers do not share a hostname, which is the single thing most guides get wrong.

Tested with live connections 1 Tap Copy App Password Steps

Get an App Password →

Client Setup Guides →

Verizon Quick Settings

IMAP Server imap.aol.com
IMAP Port 993 (SSL/TLS)
SMTP Server smtp.verizon.net
SMTP Port 465 (SSL)
POP3 Server pop.verizon.net
Username Your full email address
Password App password required →

Quick answer: incoming IMAP for a verizon.net address is imap.aol.com, port 993, SSL. Outgoing is smtp.verizon.net, port 465, SSL. POP users take pop.verizon.net on 995. Yes, incoming says aol and outgoing says verizon and that is correct. AOL has run this mailbox since Verizon left the email business.

Checked against AOL's published table for verizon.net and confirmed by connecting. Univik tools have signed in to these 3 hostnames since before the handover and after it. See what changed →

On This Page

What Changed Recently Before You Begin About Verizon.net Mail Webmail Login The 3 Server Split IMAP Settings POP3 Settings SMTP Settings Check Settings Online Any Domain Lookup App Password Setup Client Setup Guides Webmail Settings POP3 vs IMAP Sending Limits Troubleshooting Backup Walkthrough Glossary How We Verify FAQ

What Changed Recently#

Almost everything written about verizon.net email predates the moment it stopped being Verizon's to run. That is the root of most connection failures on this domain.

The change that broke every old guide

Verizon left the email business and handed these mailboxes to AOL. The address kept working, so plenty of people never noticed. The servers did not stay the same though and imap.verizon.net stopped answering while smtp.verizon.net carried on. Any guide still printing an incoming server on verizon.net was written before the handover and cannot work now.

Your password moved companies too

The password your email app needs now comes from AOL, not Verizon. Because AOL runs the mailbox, an app password from AOL's security page is what a client will accept. Your old Verizon password has nothing to do with it. Verizon support cannot help with email at all any more, which surprises people who call them first.

The Gmail change

Gmail no longer pulls verizon.net mail across. Google removed the POP fetching that pulled outside accounts into Gmail, so anyone reading a Verizon address inside a Gmail inbox lost that feed. Mail already imported stays. Connect directly using the settings below or move the mailbox properly if Gmail is where you now live.

Current status: IMAP, POP and SMTP all work normally on the servers below. Nothing here is deprecated. The difficulty is entirely that the 3 hostnames do not match each other and that half the internet still prints the old ones.

Before You Begin#

Two things to accept before you start, both of which feel wrong and are correct.

1. Your incoming server says aol

A verizon.net address collects mail from imap.aol.com. It looks like a mistake and it is not. Typing imap.verizon.net instead is the most common cause of a Verizon setup that will not connect.

Where: The 3 hostname map →

2. Your password comes from AOL

Sign in at AOL to generate an app password, using your full verizon.net address as the username, exactly as Verizon itself instructs. Nothing on verizon.com will produce the code your email client wants.

Where: App password steps →

About Verizon.net Email#

A verizon.net address is now an AOL mailbox wearing a Verizon name, which explains every odd thing on this page.

Verizon decided in 2017 to stop running email and to concentrate on internet and television instead. Rather than close the addresses, it moved them onto AOL's platform, which was a sister company by then. Customers who acted kept their address. Mailboxes nobody migrated before the deadline were deleted along with their contents and Verizon states that those addresses cannot be recovered. If your address still works today, you are on the AOL platform and everything below applies.

Email Domain@verizon.net
Who Runs ItAOL, on behalf of the address you already had
Who Does NotVerizon, which exited email in 2017 and cannot support it
Webmail URLmail.aol.com, signing in with your verizon.net address
Incoming Serversimap.aol.com for IMAP, pop.verizon.net for POP
Outgoing Serversmtp.verizon.net
Password for Email AppsAn app password generated on AOL's account security page
Username FormatYour full address including @verizon.net, as Verizon itself instructs

Verizon.net Webmail Login#

Both places you need are AOL properties, which is the part people find hardest to believe:

Who actually supports a verizon.net mailbox Verizon no longer supports verizon.net email and cannot reset passwords, recover accounts or supply settings. AOL handles all of it, because the mailboxes moved to its platform. Searching for AOL answers rather than Verizon ones finds documentation that exists. Verizon Cannot reset your password Cannot recover the account Cannot give you settings It is not a brush off AOL Issues your app password Handles account recovery Publishes the server table Search AOL, not Verizon Anyone answering a Verizon email helpline is not Verizon
Knowing which company to ask is half the battle on this domain.

Webmail

mail.aol.com, using your full verizon.net address

Account Security

login.aol.com → Account Security

This domain is a favourite with support scammers. A retired email brand attracts pages offering a Verizon email helpline and they are counting on you not knowing the service moved. Verizon does not support this mailbox and has not for years, so anyone answering a Verizon email number is not Verizon. Your settings are free, published and printed on this page.

Three Servers, Two Company Names#

Nearly every provider gives you matching hostnames. Verizon gives you 3 that disagree with each other, because the mailbox changed hands while the address stayed put. Here is the whole picture in 1 view and it is worth a look even if you only came for a copy button.

The three verizon.net servers and who runs them A verizon.net address uses imap.aol.com on port 993 for IMAP incoming mail, pop.verizon.net on port 995 for POP incoming mail and smtp.verizon.net on port 465 for outgoing mail. There is no imap.verizon.net server, which is the hostname most outdated guides still print. Incoming, IMAP imap.aol.com port 993, SSL an AOL hostname Incoming, POP pop.verizon.net port 995, SSL a Verizon hostname Outgoing, SMTP smtp.verizon.net port 465, SSL a Verizon hostname imap.verizon.net does not exist and never will again The rule that gets you through it IMAP goes to AOL, everything else stays on verizon.net
Two company names across 3 fields, which is why copying any single guide rarely works.

If you take 1 thing from this page, make it that shape. IMAP incoming goes to AOL. POP incoming and all outgoing mail stay on verizon.net. Guides that predate the handover print imap.verizon.net for incoming. They are wrong in a way that produces a timeout rather than a helpful error, which is why the hunt usually turns to passwords and ports instead.

Verizon.net IMAP Settings#

Your mail stays server side, so each device you connect shows the same folders. This is the table where the hostname says aol rather than verizon and that is deliberate.

IMAP Serverimap.aol.com
Port993
EncryptionSSL/TLS (required)
UsernameYour full address, including @verizon.net
PasswordApp password from AOL
AuthenticationRequired

Verizon.net POP3 Settings#

POP3 downloads mail to 1 device and it is the 1 incoming route that kept a verizon.net hostname. If you inherited an old profile that still works, this is probably why. Not sure which to use? See the comparison below.

POP3 Serverpop.verizon.net
Port995
EncryptionSSL/TLS (required)
UsernameYour full @verizon.net address, not the name part alone
PasswordApp password from AOL
Careful with POP3 delete settings. Older profiles often strip the server copy as they collect. Tick the leave a copy option or POP empties mail.aol.com as it downloads.

Verizon.net SMTP Settings#

Encrypted only: all 3 hostnames refuse anything unencrypted. Plain ports 143 and 110 are dead here. Check what your client guessed before blaming the hostname.

SMTP handles outgoing mail and stayed on smtp.verizon.net through the handover. AOL documents port 465 with SSL for this domain. Where a network blocks 465, people commonly fall back to 587 with STARTTLS. Start with the documented pairing. Set this to an AOL hostname, as some guides suggest and you get the reverse of the usual failure: mail sends nowhere while your inbox fills perfectly.

SMTP Serversmtp.verizon.net
Port465 with SSL, the pairing AOL documents for verizon.net
EncryptionSSL or STARTTLS (required)
UsernameYour full @verizon.net address, not the name part alone
PasswordSame as incoming mail
AuthenticationRequired. Outgoing authentication has to stay ticked or smtp.verizon.net refuses you.

Check Verizon.net IMAP Settings Online#

You will find all 3 hostnames laid out above, where every value is verified and copies in 1 tap. Wondering whether an address is still on this platform? Check it below.

Does my email address use these settings?

Runs in your browser only. Your address is never sent anywhere or stored.

Two checks tell you where you stand. Sign in at mail.aol.com with your verizon.net address, then confirm you can reach the app password screen. Both working means the mailbox migrated and every table above applies.

Look Up IMAP Settings for Any Email Domain#

Everything printed above is specific to addresses ending @verizon.net. Setting up a different address at the same time? Our free lookup at imapsettings.com handles any domain.

imapsettings.com

Complete email settings database, by Univik

Check IMAP settings online →

Enter any email address and get the incoming and outgoing server settings for that domain in 1 step:

Incoming server: hostname, port, SSL/TLS and username format
Outgoing server: SMTP hostname, port and encryption

Your address is used only to find the settings for that domain. Nothing is stored or shared.

Getting an App Password From AOL#

Since AOL runs the mailbox, AOL issues the credential. Your email client needs an app password and your ordinary password is refused unless the client can open AOL's own sign in window.

  1. Go to AOL Account Security and sign in with your full verizon.net address as the username, which is what Verizon itself tells customers to use.
  2. Choose Generate app password, then Get Started.
  3. Name it for the app that will use it, so you can tell your codes apart later.
  4. Copy the generated code into your client, using it for both server passwords since they share the credential.
The generate button can refuse you. AOL decides whether a browser session is eligible to create app passwords and a private window or an unfamiliar browser can block it with no way for support to override. Our AOL Mail settings page covers that check in full, since it applies identically to verizon.net accounts.

Set Up Verizon.net in Email Clients#

No client offers Verizon by name any more, so every setup below is manual. Watch the incoming hostname in each one. Choose your client:

Outlook Apple Mail iPhone and iPad Android Thunderbird

Outlook (Windows and Mac)

  1. Outlook: File → Add Account or Settings → Accounts → Add account in new Outlook.
  2. Type the address, then open Advanced options and take the manual setup path with IMAP selected.
  3. Set the account type to IMAP, with imap.aol.com on 993 incoming and smtp.verizon.net on 465 outgoing.
  4. Incoming imap.aol.com, outgoing smtp.verizon.net, then paste the AOL app password and tick outgoing authentication.
  5. Mail yourself a test. With mismatched hostnames, 1 direction working proves nothing about the other.

Apple Mail (macOS)

  1. On a Mac, open Mail then Settings → Accounts.
  2. Choose Other Mail Account on a Mac, because Verizon has not been in Apple's provider list for years.
  3. Expect automatic setup to fail and to reach the server screens, which is where the aol hostname goes.
  4. When server fields appear, remember they take 2 different hostnames.
  5. Enable Mail in the checkbox list and finish.

iPhone and iPad

  1. iPhone owners start in Settings → Apps → Mail → Mail Accounts.
  2. Tap Other → Add Mail Account on an iPhone, since no Verizon option exists.
  3. Fill both server screens separately. iOS asks for incoming first, then outgoing and they take different hostnames.
  4. Leave IMAP chosen and give each server screen its own hostname.
  5. Tap Save and watch which of the 2 servers it complains about.

Android

  1. On Android, add an account in your mail app and choose Other or Personal (IMAP).
  2. Skip any automatic detection, which tends to guess verizon.net for incoming and fail.
  3. Type the servers yourself, imap.aol.com in and smtp.verizon.net out.
  4. Two hostnames, not one: imap.aol.com on 993 in, smtp.verizon.net on 465 out.
  5. Finish and swipe down once to pull the folders in.

Thunderbird

  1. Thunderbird keeps it behind Account Settings and Account Actions.
  2. Give it your name, address and the AOL app password and continue.
  3. Do not trust the detection here. Thunderbird has no reliable profile for this domain, so open Configure manually.
  4. Enter both hostnames by hand and confirm the outgoing one still reads verizon.net before saving.
  5. Select Done. Folders sync on first open.

Verizon.net Webmail Settings#

Servers connect your apps. These settings shape the mailbox itself and they live at mail.aol.com because that is where the mailbox lives now.

Signature

Settings → Compose. Applies to AOL webmail only, so your desktop client keeps whatever signature you set there.

Vacation Auto Reply

Under Settings → Auto Reply. Sent from the server, so it runs with everything switched off. Give it an end date.

Filters and Folders

Under Settings → Filter Settings. Applied before any device syncs, unlike rules you build inside a desktop client.

Spam and Blocked Senders

Under Settings → Blocked Addresses. Suspected spam is filed automatically, so look there before deciding a message never arrived.

POP3 vs IMAP#

FeatureIMAPPOP3
Where mail livesOn AOL servers (imap.aol.com)Downloaded to 1 device (pop.verizon.net)
Multiple devices✅ Everything stays in sync❌ Each device sees different mail
Sent and deleted mail✅ Synced everywhere⚠️ Stays only on that device
Offline reading⚠️ Cached mail only✅ Full local copy
Server storage usedYes, counts against your quotaCan be freed after download
Best forPhone + computer, everyday useSingle PC, local archives
Our verdict: pick IMAP, with 2 caveats specific to this domain. POP kept the verizon.net hostname, so an ancient working profile is probably POP and fetching your Inbox alone. And switching that profile to IMAP does not bring the old mail with it, because anything POP already downloaded lives on that computer rather than on the server. For a permanent offline archive, a backup tool beats POP here by a wide margin, since POP leaves your folders behind.

Verizon.net Size and Sending Limits#

These are AOL's limits now, because that is whose platform your mail sits on. Verizon publishes nothing about them any more:

Switching an old POP profile to IMAP Rebuilding a verizon.net account as IMAP brings every folder from the server and keeps all future mail in sync. Mail that POP already downloaded stays on that one computer and does not move across, so exporting or backing it up first is the safe order. What IMAP brings you Every folder still on the server All future mail, on every device Read state that matches everywhere you sign in What it does not bring Mail POP already downloaded to that 1 computer, which the server never kept a copy of Export it before you switch Back up the old profile first, then rebuild as IMAP Do it the other way round and years of mail can vanish with the profile
The order that matters when modernising a decades old Verizon profile.
Message size25 MB for the whole message, counting attachments, formatting and signature together
Mailbox storageSet by AOL rather than Verizon and it varies by account. The quota shown inside your own mailbox is the figure to trust
What counts toward itEverything, Sent and Trash included. Emptying Trash is the fastest space you will find
POP coverageThe Inbox alone. Folders never come down over POP, which matters if an old profile is all you have
EncryptionSSL on all 3 servers, on ports 993, 995 and 465

Troubleshooting Verizon.net Connections#

Find the exact error your email app shows, then apply the fix:

Which half of the setup is wrong On a verizon.net account, mail that will not arrive points to the incoming hostname being set to verizon.net when it should be imap.aol.com. Mail that arrives but will not send points to the outgoing hostname being changed to an AOL address when it should stay smtp.verizon.net. Because the two servers are independent, one working proves nothing about the other. Which way does it fail? Nothing arrives Your incoming server almost certainly says verizon.net change it to imap.aol.com Arrives but will not send Someone changed outgoing to match the aol incoming host put back smtp.verizon.net The 2 servers are independent, so 1 working tells you nothing about the other
Two opposite symptoms, two opposite causes, both from the same hostname mismatch.
Error you seeWhat it meansFix
Cannot find server or a connection timeout on incoming The incoming hostname is set to imap.verizon.net, which no longer exists The signature verizon.net failure and it comes straight from an outdated guide. Change incoming to imap.aol.com on 993 with SSL and leave outgoing alone. See the server split.
Password rejected everywhere you try it You are using a Verizon password rather than an AOL app password AOL runs the mailbox, so AOL issues the credential. Generate an app password signing in with your full verizon.net address as the username.
Receives fine, sending fails Someone changed the outgoing server to an AOL hostname to match the incoming one Understandable and wrong. Outgoing stays smtp.verizon.net on 465 with SSL, with authentication ticked. Only IMAP moved to AOL.
Outlook sets the account up as Yahoo on its own Auto detect follows the DNS records behind the domain and lands on Yahoo infrastructure Not wrong exactly, just not what AOL documents for this domain. Cancel the automatic setup, choose manual configuration and enter the 3 servers yourself. The server split shows what they should read.
Only the last few weeks of mail appeared A sync window rather than a connection fault Many clients default to syncing 30 days. Look for a setting named something like mail days to sync and change it to all or unlimited. Your older mail is safe on the server.
Only the Inbox downloaded The account is running over POP, which is common on profiles that survived the handover POP fetches the Inbox alone. Rebuild the account over IMAP with the AOL incoming hostname and every folder arrives.
Verizon support says they cannot help They genuinely cannot. Verizon exited email years ago Not a brush off. Support for this mailbox lives at AOL and our AOL settings page covers the account side that applies to you too.
The address stopped working entirely The mailbox may never have been migrated in the first place Accounts not moved to AOL before the deadline were deleted with their contents and Verizon states they cannot be recovered. If webmail at mail.aol.com refuses the address, that is the likely answer.

Reader Reported Fixes

Two fixes that come up constantly on this domain, both from real verizon.net cases.

Rebuild the account rather than editing the old one. Profiles that predate the handover carry stale hostnames in places the settings screen does not show you and correcting the visible field often leaves the rest cached. Deleting the account and adding it fresh with all 3 correct servers is quicker than hunting.

Search for AOL answers, not Verizon ones. Once you know AOL runs the mailbox, the whole troubleshooting landscape changes. Problems that look unsolvable under a Verizon search are documented under AOL, including the app password rules that decide whether you can generate a code at all.

Why a Verizon Address Lives at AOL#

The short version explains every strange thing on this page and it is worth knowing because it also tells you where to ask for help.

How verizon.net mail ended up on AOL Verizon exited the email business in 2017 and moved verizon.net mailboxes onto the AOL platform. Addresses that migrated kept working with new server settings. Mailboxes that were not migrated before the deadline were deleted along with their contents and Verizon states those addresses cannot be recovered. Verizon exits the email business 2017 Mailboxes move onto the AOL platform address kept Servers change IMAP moves to AOL guides do not Not migrated deleted with their contents Where this leaves you today A working verizon.net address means you are on AOL, whether you remember moving or not So AOL issues the password and AOL runs the support
One decision in 2017 and every outdated guide since traces back to it.

Verizon's own pages put it plainly. It no longer offers verizon.net email, customers had to move to the AOL platform to keep their address. Whatever was left behind got deleted. Verizon adds 1 instruction that matters here, which is to sign in using the full verizon.net address as your username on AOL. That is why the app password steps send you to an AOL page with a Verizon address in the username box.

Thinking of moving off this address entirely? Plenty of people do once they learn it runs on a platform they never chose. The Univik Email Migration Tool reads from all 3 hostnames above and writes your folders into whichever account you are moving to. Our Email Migration Services team will run the whole move and confirm what arrived.

Use These Settings in Univik Email Backup#

A verizon.net mailbox has already survived 1 company deciding it was no longer their problem. That is reason enough to hold your own copy and the IMAP values above are what a backup tool signs in with. Univik Email Backup writes the mailbox to PST, MBOX, EML or PDF on your own disk, which no corporate decision can reach.

  1. Launch Univik Email Backup on Windows.
  2. Choose IMAP in the source list, since Verizon rarely appears by name and paste imap.aol.com as the server.
  3. Use your full @verizon.net address with the AOL app password, which is what the mailbox actually answers to.
  4. Typing servers by hand? imap.aol.com on 993 with SSL, which is the aol hostname the table explains.
  5. Pick an output format and a destination, then run it. Large mailboxes download in the background.
Why this domain especially: mailboxes here were deleted once already for people who missed a deadline and the only copy that outlives a decision like that is one you hold. Every folder, attachment and date lands in files that outlive the account itself. Moving to a new account instead of archiving? The email migration tool shifts it into the new mailbox instead.

Email Settings Glossary#

IMAP

Internet Message Access Protocol. The protocol behind imap.aol.com, which is where verizon.net incoming mail actually lives. Every device mirrors the same folders.

POP3

Post Office Protocol version 3. The pop.verizon.net route, which fetches the Inbox and leaves your folders behind on the server. Kept a verizon.net hostname when IMAP did not.

SMTP

Simple Mail Transfer Protocol. Sends your outgoing mail. The outgoing half and the server that kept its verizon.net name through the handover.

SSL / TLS / STARTTLS

The encryption layer, required on all 3 hosts. How the connection is secured. All 3 verizon.net servers use SSL, on 993, 995 and 465 respectively.

App Password

A generated code that replaces your password inside an email app. For this domain it comes from AOL, not Verizon, which is the detail that trips everyone.

OAuth

A sign in window run by the provider, which for a verizon.net address means an AOL one. A client offering it skips the app password entirely.

How We Verify These Settings#

Univik has built email backup and migration software since 2013, spanning the whole period this domain changed hands. Legacy addresses like these are a steady part of that work, which is where mismatched hostnames get spotted.

Three checks stand behind these values. A working session from Univik Email Backup against all 3 hostnames. A line by line match with AOL's published table for verizon.net accounts, which is the authoritative source now. And Verizon's own statements about what it does and no longer does.

Spotted a value that has moved again? Tell us and the value gets rechecked, with whatever we find recorded in what changed recently.

 Help & Support

Verizon.net Email Settings: FAQ

Incoming IMAP is imap.aol.com on port 993 with SSL. Outgoing is smtp.verizon.net on port 465 with SSL. POP users take pop.verizon.net on 995. Sign in with the whole @verizon.net address, using an AOL app password as the password.

Because AOL runs the mailbox. Verizon left the email business and moved these accounts onto AOL's platform, keeping the addresses intact. IMAP moved with them while the outgoing and POP hostnames stayed on verizon.net, which is why the 3 servers disagree.

It stopped answering when the mailboxes moved. Guides written before the handover still print it and typing it in produces a timeout rather than a useful error, which sends people looking at passwords and ports instead of the hostname.

Because they genuinely cannot. Verizon exited email entirely and no longer runs this service. Everything about the account, including passwords and recovery, sits with AOL now.

An app password generated on AOL's account security page, signing in with your full verizon.net address as the username. Verizon passwords have no role here and your ordinary AOL password is refused by clients that cannot open AOL's sign in window.

Probably not and it is worth knowing why. Accounts that were never migrated to AOL before the deadline were deleted along with their mail and Verizon states those addresses cannot be recovered. If mail.aol.com refuses the address, that is usually the explanation.

IMAP, which keeps every device in sync and brings all your folders. POP is worth knowing about only because it kept a verizon.net hostname, so a very old working profile is likely POP and likely fetching your Inbox alone.

No and this catches people twice. Incoming and outgoing are separate hostnames on this domain, so correcting one leaves the other broken. Test both directions before assuming a fix worked.

Sign a backup tool in over IMAP and keep the output as PST, MBOX, EML or PDF. Moving instead of copying? An email migration tool connects to both mailboxes and recreates the structure at the destination. See the walkthrough.

No. Verizon stopped issuing these addresses when it left the email business, so only accounts that already existed and made the move to AOL are still running. If you need a new address you are choosing a different provider. The migration tool can carry your old mail into it.

Other Email Provider Settings

Gmail Settings Outlook.com Settings Yahoo Mail Settings AOL Mail Settings iCloud Mail Settings Comcast Settings

Summary: Verizon.net Settings at a Glance

  • IMAP: imap.aol.com, port 993, SSL/TLS
  • POP3: pop.verizon.net, port 995, SSL/TLS
  • SMTP: smtp.verizon.net, port 465 or 587
  • Username is always your full email address
  • App password required for third party apps
  • Pick IMAP for phone + computer sync
  • Message limit: 25 MB including signature
  • Username is always the full email address