Event ID 1029: POP3/IMAP4 Errors - Complete Fix Guide
Complete troubleshooting guide for Exchange Server Event ID 1029 POP3 and IMAP4 errors. Learn to enable, configure, and troubleshoot legacy email protocols for third-party client access.
Table of Contents
Understanding Event ID 1029: POP3/IMAP4 Errors
📌 Version Compatibility: This guide applies to Exchange Server 2016, Exchange Server 2019, Exchange Server 2022 (SE). Commands may differ for other versions.
Event ID 1029 indicates issues with POP3 or IMAP4 services in Exchange Server. These legacy protocols provide email access for third-party clients like Thunderbird, Apple Mail, and mobile apps that don't support Exchange-native protocols. By default, these services are disabled in Exchange and must be configured manually.
Log Name: Application Source: MSExchange POP3 Event ID: 1029 Level: Error Description: The Microsoft Exchange POP3 service failed to start because it is disabled or there are no POP3 servers available. -or- IMAP4 connection from client 192.168.1.50 failed. Error: Authentication failure for user user@domain.com. Protocol: IMAP4
Symptoms & Detection
Primary Symptoms
- ●Third-party email clients cannot connect to Exchange
- ●Thunderbird/Apple Mail shows "Login failed" error
- ●Connection refused on ports 110, 143, 993, or 995
- ●POP3/IMAP4 services won't start
- ●Authentication failures despite correct password
Common Causes
1. Services Not Running
MSExchangePOP3 and MSExchangeIMAP4 services are disabled by default and must be started and set to Automatic startup.
2. Protocol Disabled for User
POP3 or IMAP4 access is disabled at the mailbox level via CASMailbox settings, preventing that specific user from using the protocol.
3. Certificate Not Assigned
SSL certificate doesn't have POP/IMAP services enabled, or the certificate doesn't include the hostname used for POP3/IMAP4 access.
4. Firewall Blocking Ports
Windows Firewall or network firewall blocking ports 110, 143, 993, or 995. SSL ports (993/995) require additional configuration.
Diagnostic Steps
Step 1: Check Service Status
# Check POP3 and IMAP4 service status
Get-Service MSExchangePOP3, MSExchangeIMAP4, MSExchangePOP3BE, MSExchangeIMAP4BE |
Select-Object Name, Status, StartType | Format-Table -AutoSize
# Check if services exist
Get-Service *POP3*, *IMAP4* | Format-Table Name, Status, StartTypeStep 2: Check User Protocol Settings
# Check if POP3/IMAP4 enabled for user
Get-CASMailbox -Identity user@domain.com |
Format-List PopEnabled, ImapEnabled, PopUseProtocolDefaults, ImapUseProtocolDefaults
# Check all users with POP3/IMAP4 disabled
Get-CASMailbox -ResultSize Unlimited |
Where-Object {$_.PopEnabled -eq $false -or $_.ImapEnabled -eq $false} |
Select-Object DisplayName, PopEnabled, ImapEnabledStep 3: Test Port Connectivity
# Test POP3/IMAP4 ports
$ports = @(
@{Port=110; Name="POP3"},
@{Port=995; Name="POP3-SSL"},
@{Port=143; Name="IMAP4"},
@{Port=993; Name="IMAP4-SSL"}
)
foreach ($p in $ports) {
$result = Test-NetConnection -ComputerName mail.domain.com -Port $p.Port -WarningAction SilentlyContinue
$status = if($result.TcpTestSucceeded){"OPEN"}else{"CLOSED"}
Write-Host "$($p.Name) ($($p.Port)): $status"$p.Port)): $status" -ForegroundColor $(if($result.TcpTestSucceeded){'Green'}else{'Red'})
}Quick Fix (5-15 minutes)
🚀 Immediate Resolution: Enable POP3/IMAP4
# Start and enable POP3 services
Set-Service MSExchangePOP3 -StartupType Automatic
Set-Service MSExchangePOP3BE -StartupType Automatic
Start-Service MSExchangePOP3, MSExchangePOP3BE
# Start and enable IMAP4 services
Set-Service MSExchangeIMAP4 -StartupType Automatic
Set-Service MSExchangeIMAP4BE -StartupType Automatic
Start-Service MSExchangeIMAP4, MSExchangeIMAP4BE
# Enable for specific user
Set-CASMailbox -Identity user@domain.com -PopEnabled $true -ImapEnabled $true
# Assign certificate to POP/IMAP
$cert = Get-ExchangeCertificate | Where-Object {$_.Services -match "IIS"}
Enable-ExchangeCertificate -Thumbprint $cert.Thumbprint -Services POP, IMAP
# Verify services
Get-Service MSExchangePOP3, MSExchangeIMAP4 | Format-Table Name, Status💡 Pro Tip
Detailed Solutions
Solution 1: Configure Virtual Directories
# Configure POP3 settings
Set-PopSettings -ExternalConnectionSettings "mail.domain.com:995:SSL" -InternalConnectionSettings "mail.domain.com:995:SSL" -X509CertificateName "mail.domain.com"
# Configure IMAP4 settings
Set-ImapSettings -ExternalConnectionSettings "mail.domain.com:993:SSL" -InternalConnectionSettings "mail.domain.com:993:SSL" -X509CertificateName "mail.domain.com"
# Restart services to apply
Restart-Service MSExchangePOP3, MSExchangeIMAP4Solution 2: Configure Firewall Rules
# Add Windows Firewall rules for POP3/IMAP4
New-NetFirewallRule -DisplayName "Exchange POP3-SSL" -Direction Inbound -LocalPort 995 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Exchange IMAP4-SSL" -Direction Inbound -LocalPort 993 -Protocol TCP -Action Allow
# Verify rules
Get-NetFirewallRule | Where-Object {$_.DisplayName -match "POP3|IMAP4"} |
Select-Object DisplayName, Enabled, ActionVerification Steps
# Test POP3 connectivity
Test-PopConnectivity -ClientAccessServer YOURSERVER | Format-List Scenario, Result
# Test IMAP4 connectivity
Test-ImapConnectivity -ClientAccessServer YOURSERVER | Format-List Scenario, Result
# Verify certificate assignment
Get-ExchangeCertificate | Where-Object {$_.Services -match "POP|IMAP"} |
Format-List Subject, Services, NotAfterPrevention Strategies
📊 Monitoring
- • Monitor POP3/IMAP4 service status
- • Track authentication failures
- • Alert on port connectivity issues
🔐 Security
- • Use SSL ports (993/995) only
- • Consider disabling if not needed
- • Plan OAuth migration for Exchange 2019
When to Escalate
Expert Exchange POP3/IMAP4 Support
Microsoft-certified engineers with 15 Minutes response time, 24/7
Frequently Asked Questions
Related Exchange Server Errors
Can't Resolve Event ID 1029?
Exchange errors can cause data loss or extended downtime. Our specialists are available 24/7 to help.
Emergency help - Chat with usMedha Cloud Exchange Server Team
Microsoft Exchange Specialists
Our Exchange Server specialists have 15+ years of combined experience managing enterprise email environments. We provide 24/7 support, emergency troubleshooting, and ongoing administration for businesses worldwide.