If your IP was blocked by the server firewall with a message about POP3 or IMAP logins exceeding an hourly limit, your password is probably fine. This guide explains what that block actually means, how to get back online, and how to fix the mail client behavior that triggered it so it does not keep happening.
The stock explanation attached to these block notices is often wrong. It tells you to check your password, but the most common trigger is a mail program stuck in a reconnect loop on an oversized POP3 mailbox. There is nothing wrong with your credentials. Switching that account from POP3 to IMAP fixes it permanently.
01. What the Block Message Actually Means
The notice you received looks something like this:
lfd - pop3d - 181 logins in 1369 secs from 203.0.113.45
for [email protected] exceeds 180/hour
There are two completely different firewall rules that can block a mail connection, and they mean opposite things:
Failed Login Blocks
Triggered when a program repeatedly submits the wrong password. The log entry says "authentication failed" or "login failed". This is the rule that protects against password guessing, and this is the one the stock explanation was written for.
Login Tracking Blocks
Triggered by too many successful logins per hour from one IP. The wording is "X logins in Y secs exceeds Z/hour". Your password worked every single time. The problem is how often your mail program is connecting.
If your message uses the second wording, you can stop worrying about your password. It is correct, it is current, and re-entering it will not help.
The block notice ships with a single generic explanation covering both rule types, and it defaults to the password wording because that is the more common case across all servers. It is not customized to your specific block. Read the log line, not the explanation underneath it.
02. First, Get Yourself Unblocked
These blocks are temporary and expire on their own, usually within an hour. If you cannot wait, or if it has already expired and come back, you have three options:
- Wait it out - the block lifts automatically once the timer runs down. If the underlying cause is still running, it will simply block again, so use the wait to work through the rest of this guide.
- Unblock yourself - our firewall unblock page lets you clear your own IP without opening a ticket. See Firewall Block: How to Unblock Your IP for the walkthrough.
- Open a ticket - if you have been blocked more than once, ask us to look at the mail logs. We can tell you exactly which program is looping and how much mail is sitting in the mailbox.
Use webmail while you sort this out. Log in at https://yourdomain.com/webmail to read and send mail from any browser. Webmail runs on the web ports, so a mail-port block does not affect it.
03. Why Your Mail Program Connects Hundreds of Times
Customers who get this block are usually surprised by the numbers, because their phone is set to check every 5 or 15 minutes. A phone on a 5-minute schedule connects about 12 times an hour. The blocks fire at 180 an hour, and the accounts that trip them are often running far above that.
Here is what is happening. POP3 was designed in an era when people downloaded their mail and deleted it from the server. Every time a POP3 client checks for new mail, the very first thing it does is ask the server for a complete list of every message currently in the inbox, including a unique ID for each one. It uses that list to work out which messages it has already seen.
That is fine with 200 messages in the inbox. It is a problem with 20,000.
One account we looked at had 21,804 messages and 4.8 GB sitting in the inbox with "leave a copy on the server" enabled. Every single check pulled down a 564 KB index listing all 21,804 message IDs. Something in the client was choking partway through parsing it, so the program gave up and immediately reconnected.
The result: 829 logins in a few hours, roughly one every 1.5 seconds, and zero messages actually downloaded. Nearly half a gigabyte of traffic to deliver no mail at all.
Once a client falls into that loop it will not recover on its own. It retries forever, which is why the block comes straight back after it expires.
04. Check How Much Mail Is on the Server
Before changing any settings, find out what you are dealing with:
- Log in to cPanel and open Email Accounts.
- Find the address that appeared in the block message.
- Look at the disk usage figure next to it.
Then check the message count. In webmail, open the inbox and look at the total shown at the bottom of the message list, or in your mail program look at the folder properties for the inbox.
Rough guidance on what you will find:
- Under 2,000 messages - not the cause. Skip to section 07, you likely have extra devices or an antivirus scanner involved.
- 2,000 to 10,000 messages - borderline. Many clients handle this, some do not. Switching to IMAP is still the right move.
- Over 10,000 messages - this is your cause. Both the protocol switch and a cleanup are needed.
Mail stored on the server counts against your hosting disk space. See Does Email on the Server Count Towards My Allotted Space and Understanding and Managing Disk Space.
05. The Real Fix: Switch From POP3 to IMAP
IMAP does not enumerate your whole mailbox on every check. It holds one connection open and the server tells it about new mail as it arrives. A mailbox size that breaks POP3 is a non-issue for IMAP.
The other benefits matter just as much if you use more than one device:
- Everything stays in sync - read a message on your phone and it shows as read on your desktop. Delete it in one place and it is gone everywhere.
- Folders work across devices - the folders you create are stored on the server, so every device sees the same filing.
- Sent mail is shared - replies sent from your phone appear in the Sent folder on your computer.
- Nothing is trapped on one machine - if a laptop dies, your mail is still on the server.
Settings to use
Incoming (IMAP)
Server: yourserver.ultrawebhosting.com
Port: 993
Security: SSL/TLS
Username: full email address
Password: your email account password
Outgoing (SMTP)
Server: yourserver.ultrawebhosting.com
Port: 465
Security: SSL/TLS
Authentication: required, same username and password
Use the server hostname rather than mail.yourdomain.com. The server hostname always has a valid SSL certificate, so you avoid certificate mismatch warnings. You can find yours in the cPanel welcome email or by asking us. See Fixing Outlook SSL Certificate Warnings.
Step-by-step instructions for each platform:
- How to Set Up Email in Microsoft Outlook
- How to Set Up Email on Your iPhone or iPad
- How to Set Up Email on Android
- POP3 vs IMAP - Choosing the Right Email Protocol
Do not delete the old POP3 account profile until the new IMAP account has finished its first sync and you have confirmed your mail is all there. If your POP3 setup was downloading and removing mail from the server, those older messages exist only in your local mail file, and deleting the profile can take them with it. Export or archive first if you are unsure.
Every device using that address needs to be switched, not just the one you suspect. A single leftover POP3 configuration on a machine in the back office is enough to keep triggering the block.
06. Archive or Clean Up Old Mail
Switching to IMAP stops the blocks. Trimming the mailbox makes everything faster and keeps your disk usage under control. An inbox with 20,000 messages is slow in any mail program, on any protocol.
You do not need to delete anything. Filing is enough:
- Create folders by year in webmail or your IMAP client, such as Archive/2023 and Archive/2024.
- Sort the inbox by date and move each year's mail into its folder. Work oldest first.
- Leave the last 12 to 18 months in the inbox. Aim for under about 2,000 messages there.
- Empty Trash and Junk once you are done. These are often larger than people expect.
- Look for oversized attachments and save them to your computer, then delete the message. A handful of 30 MB messages can account for a large share of the total.
Moving 20,000 messages through a mail client is slow and can time out. Open a ticket and we can file them into yearly folders directly on the server in a few minutes, with a backup taken first. Nothing gets deleted without your say-so.
07. Extra Devices and Antivirus Scanners
If your mailbox is small and you are still getting blocked, the connection count is coming from somewhere else. Work through these:
Forgotten devices
Count every device and program that has ever had this address configured. Phone, tablet, work desktop, home laptop, an old machine in a spare room, a shared computer at the front desk. Each one connects on its own schedule, and they all share your office IP address as far as the firewall is concerned. Five devices checking every 2 minutes is 150 logins an hour before anyone touches anything.
Aggressive check intervals
In Outlook, go to Send / Receive > Send/Receive Groups > Define Send/Receive Groups and check the scheduled interval. Anything under 5 minutes is unnecessary and adds up quickly across devices. Multiple send/receive groups configured against the same account will multiply it further.
Antivirus mail scanning
Some security suites proxy your mail connections to scan messages, which can double every check or introduce its own retry behavior. If you have mail scanning enabled in your antivirus, disable that specific feature and see whether the login count drops. Your mail is already filtered on our side.
Duplicate accounts in one program
It is common to find the same address configured twice in a single mail program after a migration or repair, with both copies polling independently. Check the account list for duplicates.
A quick way to narrow it down: shut down every device except one for an hour. If the blocks stop, add devices back one at a time until they resume. The last one you added is the culprit.
08. When It Really Is a Password Problem
The tracking block is not a credential problem, but there are two situations worth ruling out.
You did change the password recently. If you updated the email password in cPanel and one device still has the old one saved, that device will produce failed logins and trip the other rule. The wording in the notice will say "failed" rather than "logins in X secs". Update the saved password on every device.
The connections are not coming from you. Look at the IP address and location in the block message. If it names a city, state, or country you have no connection to, treat that as a possible account compromise rather than a misbehaving client. In that case:
- Change the email account password immediately in cPanel under Email Accounts, and use something long and unique.
- Check for forwarders in cPanel under Email > Forwarders. Attackers commonly add a quiet copy-to address.
- Check email filters for rules that auto-delete or redirect mail, which are used to hide activity.
- Check the autoresponder for anything you did not set up.
- Open a ticket so we can review the authentication logs and confirm what accessed the account.
See Email Troubleshooting Guide for general mail problems, Common Outlook Email Errors, Common Thunderbird Email Errors, and How to Change Your cPanel Password.
Not Sure Which Device Is Causing It?
We can read the mail logs and tell you exactly which program is looping, how many messages are in the mailbox, and what it is doing on each connection. We can also file old mail into yearly folders on the server for you.
Open a Support TicketQuick Recap: Fixing a Mail Login Block
If you only do five things from this guide, do these:
- Read the log line, not the explanation - "X logins in Y secs" means successful logins, so your password is fine
- Unblock your IP using our firewall unblock page, or wait for the block to expire on its own
- Check your mailbox size in cPanel under Email Accounts - over 10,000 messages is almost certainly the cause
- Switch every device from POP3 to IMAP on ports 993 and 465 with SSL/TLS, leaving none behind
- Archive old mail into yearly folders so the inbox stays under about 2,000 messages
