When people learn Gmail will stop fetching mail over POP, the first idea is usually: “I will turn on forwarding at the host and be done.” It sounds clean. Sometimes it works for a while. Then the weird cases show up: messages that never arrive, land in spam, or the recipient never saw.
That is not superstition. It is email authentication.
What forwarding breaks
A message leaves signed for the original domain. If the hosting server forwards it to Gmail, the path changes. SPF says which servers may send for that domain. DKIM signs the content. After a forward, those signals often stop matching what Gmail expects. Typical result: quarantine, spam, or a quiet reject.
That is why Gmail POP was the preferred plan B for years. Gmail went to the original mailbox, pulled the message, and stored it in your account. You did not need the forward to “look legitimate.”
Forward vs sync
- Forward: the other server pushes a copy to Gmail. Gmail judges it as third-party inbound mail.
- Sync (IMAP/POP + API): a process reads the mailbox and writes the message into your Gmail. The source remains the mailbox server.
You feel the difference most with custom domains, cPanel mailboxes, and small ISP addresses. That is where forwarding tends to hurt.
When forwarding can still help
If you control DNS, SRS, and volume is low, you can sometimes build a decent forward. It can also work as a temporary backup. I would not treat it as a full Mail Fetcher replacement if your business cannot afford lost leads.
A practical path
If you want to keep opening everything in Gmail web, look for a sync setup. GetPopMail connects IMAP mailboxes (and POP when applicable) and places messages in Gmail with labels. You avoid fighting SPF every time the host changes something.
Before you disable the old POP connection, send a test message to each mailbox and confirm it lands where it should. It sounds obvious. It is the step most people skip.