Server Specifications

Verified o2 Poczta IMAP, SMTP & POP3 Server Settings

Authoritative reference for server hostnames, port numbers, SSL/TLS security standards, and authentication requirements for o2 email accounts.

Server Settings

Official o2 Mail Server Specifications

Verified server addresses, ports, and security protocols for configuring any third-party mail client.

Protocol Server Hostname Port Encryption Authentication Action
IMAP
Incoming (Sync)
poczta.o2.pl 993 SSL/TLS Full Email Address & Password
POP3
Incoming (Download)
poczta.o2.pl 995 SSL/TLS Full Email Address & Password
SMTP
Outgoing (Send)
poczta.o2.pl 465 SSL/TLS Required

1. Detailed Incoming Mail Configuration (IMAP vs. POP3)

To receive messages from o2 servers in external mail software, you can configure either IMAP or POP3. Below is an exhaustive breakdown of both protocols:

IMAP: Internet Message Access Protocol (Recommended)

  • Server Address: poczta.o2.pl
  • Port Number: 993
  • Encryption Protocol: SSL / TLS
  • Authentication: Normal Password / Full email address
  • Advantages: Messages remain stored on the cloud server. Folder structures, read/unread flags, sent messages, and drafts synchronize simultaneously across your laptop, desktop, iPhone, Android, and webmail.

POP3: Post Office Protocol version 3 (Legacy)

  • Server Address: poczta.o2.pl
  • Port Number: 995
  • Encryption Protocol: SSL / TLS
  • Authentication: Normal Password / Full email address
  • Considerations: POP3 downloads emails directly to a single device hard drive. Sent emails and custom folders created on your PC will NOT be visible in webmail or on your mobile phone.

2. Outgoing Mail Configuration (SMTP)

SMTP (Simple Mail Transfer Protocol) handles all outbound message delivery. o2 strictly enforces authenticated, encrypted SMTP on port 465:

  • Outgoing Server Hostname: poczta.o2.pl
  • Standard Port: 465 (SSL/TLS)
  • Alternative Port: 587 (STARTTLS - only if 465 is blocked by network firewall)
  • Authentication Requirement: Mandatory. "Outgoing server requires authentication" must be checked using your complete email address and password.
  • Why Port 25 Fails: Port 25 is unencrypted and blocked by almost all residential and commercial ISPs worldwide to prevent malware spam relays. Never configure port 25 for o2.

Security Requirement: Application Passwords

If your account uses 1login WP Two-Step Verification (2FA), standard passwords will be rejected by both IMAP and SMTP. You must generate a dedicated Application Password (hasło do aplikacji zewnętrznej) in your 1login WP profile.

3. DNS Routing & Anti-Spoofing Authenticator

Inspect official MX mail routing, SPF authorized sender policies, and DMARC enforcement records for o2 email services:

DNS & Deliverability

o2 Mail Server DNS & SPF/DKIM Authenticator

Inspect official MX routing, SPF anti-spoofing policies, DKIM signature standards, and DMARC enforcement protecting Poczta o2 mailboxes.

MX (Mail Exchanger)

Inbound Routing Record

Tells international mail transfer agents (MTAs) where to deliver inbound emails addressed to @o2.pl.

MX 10 mx.o2.pl
SPF (Sender Policy Framework)

Authorized Outbound Senders

Lists authorized IP clusters permitted to send outbound emails on behalf of o2 domains.

TXT v=spf1 include:_spf.o2.pl ~all
DKIM (DomainKeys)

Cryptographic Signature

Signs message headers using asymmetric RSA cryptography to guarantee messages were not modified in transit.

TXT s=default._domainkey.o2.pl
DMARC Policy

Enforcement & Reporting

Directs receiving mail systems (Gmail, Yahoo, Microsoft) to reject forged emails failing SPF/DKIM checks.

TXT v=DMARC1; p=reject; sp=reject; pct=100;

Interactive SPF Builder: Sending o2 Mail from Custom Domains or Relay Services

If you forward your personal domain to o2 or relay emails through Wirtualna Polska SMTP infrastructure, include the o2 SPF mechanism to prevent Gmail / Yahoo spam flag rejections.

TXT v=spf1 include:_spf.o2.pl ~all

4. SMTP Response Code Diagnostics Matrix

When an outbound transmission fails, the receiving or sending mail server issues a 3-digit RFC 5321 status code. Use this matrix to interpret and solve the error immediately:

SMTP Code Server Message Root Cause Required Action
250 OK Message accepted for delivery Successful transmission ✓ Normal Operation
535 5.7.8 Authentication credentials invalid Wrong password or 2FA active without app password Generate 1login WP Application Password
550 5.1.1 User unknown / Recipient address rejected Destination email address does not exist Verify spelling of recipient address
552 5.3.4 Message size exceeds fixed limit Attachment exceeds 25MB encoded limit Compress file or share via cloud storage link
554 5.7.1 Relay access denied / Client host blocked SMTP authentication disabled in mail app Check "My outgoing server requires authentication"
451 4.7.1 Greylisting temporary delay Anti-spam throttle on newly observed sending IP Mail client will automatically retry in 5–10 minutes

5. Technical FAQ on o2 Mail Servers

No. Always use poczta.o2.pl. While old subdomains like mail.o2.pl existed in the past, the official SSL/TLS security certificates are issued specifically for poczta.o2.pl. Using other hostnames will produce SSL certificate domain mismatch errors in modern clients.

No, o2 does not currently support OAuth2 for independent email clients. Instead, Wirtualna Polska utilizes the Application Password standard (Hasła do aplikacji) to safely bridge 2FA security with third-party software.

Port 25 is unencrypted plaintext. Internet service providers (ISPs) worldwide block outbound port 25 on residential and mobile connections to stop infected computers from operating as silent spam bots. Always use Port 465 with SSL/TLS encryption for o2.

Launch Email Setup Wizard Open All Interactive Tools