Seems like a DNS problem or something? Webmail works fine, old Email account under same domain works fine, just not new account under any domain. Checked settings, software, tried alternative configs (different Pop servers, the IP instead of the name, etc). Uninstalled and reinstalled Outlook, deleted and recreated the Pop account both in Outlook and on the hosting company, still nothing. Checked settings a hundred times of course. The environment is a Windows 2003 Small business Server, the clients are all Win XP Pro running DHCP with DNS and DHCP running on the server. I’ve run all the Windows updates & virus protection scans. No other known problems exist.

Any other ideas??? thanks

Dani AI

Generated

Good thread — the key clue is that receiving works when you log onto the machine with a different Windows account. That strongly points to a client-side, per-user problem (Outlook profile, data file or per-user security/config), not a pure DNS or ISP block. The next checks should focus on the user profile and where Outlook writes incoming mail.

Try these practical, ordered steps:

  • Create a brand-new Outlook profile for the affected Windows user (Control Panel -> Mail -> Show Profiles -> Add). Configure the POP account in that fresh profile and test. If it receives, migrate data into the new profile rather than fiddling with the old one.

  • Back up the current PST/OST used by the problem profile and run the Inbox Repair Tool (scanpst.exe) on it. Repair until no errors remain. Always work on a copy and keep the backup.

  • Confirm the delivery data file path and permissions (Mail Setup -> Data Files). If the PST is on a network share or a redirected folder, move it locally for testing and check NTFS permissions and read-only attributes. A locked or non-writable PST will let you send but prevent downloads.

  • Run Outlook in safe mode (outlook.exe /safe) to rule out add-ins, and temporarily disable on-access mail scanning in any AV suite. Some AV or per-user firewall settings can block POP downloads for a specific profile.

  • If still failing, test POP connectivity from the client (telnet to the POP port or use an SSL client) to verify server handshake and credential acceptance, and enable Outlook logging (Tools -> Options -> Other -> Advanced Options -> Enable logging) to capture the session for inspection.

If a new profile + local PST fixes it, export contacts/calendar and retire the old profile. If not, capture the POP session and provider-side logs and escalate with that evidence. This avoids repeating prior re-installs and targets the per-user area that the colleague-login symptom highlights.

Recommended Answers

All 2 Replies

Are you hosting the email account or is it hosted by an ISP?

It is hosted with Godaddy. I talked to several people there including one of their top dogs, and even he had no clue after trying a few things...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.