FAQ
TL;DR: Thunderbird SMTP timeouts to WP had 1 root cause: a router blocked port 465; "check if the ports are blocked" solved it. Keep SSL/TLS and normal password, or ask your ISP to unblock. [Elektroda, badboy84, post #16707208]
Why it matters: This FAQ helps Thunderbird users fix WP Mail send failures caused by port 465/SSL/TLS connectivity or ISP/router blocks.
Quick Facts
- WP (smtp.wp.pl) works with SMTP port 465, SSL/TLS, and normal-password authentication in Thunderbird. [Elektroda, lufa9999, post #16706319]
- Symptom pattern: outgoing send times out; incoming mail still arrives. [Elektroda, lufa9999, post #16706319]
- A new ISP change coincided with the failure window (about one week). [Elektroda, lufa9999, post #16707189]
- Antivirus removal (ESET) did not resolve the timeout in this case. [Elektroda, lufa9999, post #16707180]
- Final fix: unblock the necessary SMTP ports in the router; sending resumes. [Elektroda, lufa9999, post #16707230]
How do I fix Thunderbird SMTP timeout errors when sending via WP?
Keep WP settings (smtp.wp.pl, port 465, SSL/TLS, normal password). Then remove router blocks on outgoing SMTP and test again. If needed, ask your ISP to lift any SMTP restrictions. After unblocking the router, sending worked immediately for the poster. [Elektroda, lufa9999, post #16707230]
What are the correct SMTP settings for WP Mail in Thunderbird?
Use server: smtp.wp.pl. Set port: 465. Enable SSL/TLS. Authentication method: Normal password. These settings received mail correctly, but sending failed until networking was fixed. They remain the baseline to configure before troubleshooting connectivity. [Elektroda, lufa9999, post #16706319]
Could my ISP be blocking WP’s SMTP and causing timeouts?
Yes. An experienced responder noted the provider may block access to WP or SMTP. This can cause send failures while everything else appears normal. If unblocking the router doesn’t help, contact the ISP to request SMTP allowance on your line. [Elektroda, Kolobos, post #16707184]
How can I quickly test whether my network is at fault?
Try sending from another device or network on the same connection. If all devices fail, suspect ISP or router blocking. If another network works, the fault is your local link. This isolates the issue before deeper client changes. [Elektroda, Kolobos, post #16707184]
How do I check if my router blocks port 465 (SSL/TLS SMTP)?
Look for firewall, parental control, or outbound filtering rules in your router. Allow outbound TCP 465 (and related SMTP ports if present). Save and reboot the router, then test sending. "Check if the ports are blocked" was the winning hint here. [Elektroda, badboy84, post #16707208]
Does uninstalling antivirus (like ESET) fix this SMTP timeout?
Not necessarily. The user removed ESET Smart Security, but the timeout persisted. This shows the failure was network-level, not client antivirus. Focus on router and ISP checks before extensive reinstalls. [Elektroda, lufa9999, post #16707180]
Why can I receive mail but not send with WP in Thunderbird?
Receiving uses inbound protocols (POP/IMAP) that were unaffected. Sending uses SMTP over port 465, which was blocked. That asymmetry explains successful downloads but failed uploads. Unblocking the router restored send while receive was always fine. [Elektroda, lufa9999, post #16706319]
I can’t create a WP account—the availability check hangs. What should I do?
Treat it as a connectivity block. The same network that timed out SMTP also stalled the account flow. Fix the router/ISP blocks first, then retry the sign-up page. Network-side constraints can freeze such checks. [Elektroda, lufa9999, post #16706668]
What should I ask my ISP when I call?
Describe repeated SMTP timeouts to smtp.wp.pl on port 465 with SSL/TLS. Request removal of any outbound SMTP blocks. As one helper put it: "Contact your internet provider!" Keep a brief log of failed attempts. [Elektroda, Kasek21, post #16707191]
Is there a simple 3-step process to restore sending?
- Confirm Thunderbird uses smtp.wp.pl:465 with SSL/TLS and normal password.
- Log into your router; remove outbound blocks on TCP 465; reboot it.
- If still failing, call the ISP to unblock SMTP on your line.
[Elektroda, badboy84, post #16707208]
How long did the issue last after switching providers?
About one week. The poster noted the problems started after changing to a new provider for roughly that period. This timing is a strong clue for ISP or router policy changes affecting SMTP. [Elektroda, lufa9999, post #16707189]
What is FRST and why was it requested here?
FRST (Farbar Recovery Scan Tool) gathers diagnostic logs for Windows troubleshooting. A helper asked for FRST logs to rule out system-level issues. In this case, the root cause was network blocking, not malware or OS faults. [Elektroda, Kolobos, post #16706670]
What’s an edge case to watch for during troubleshooting?
Antivirus removal alone may not help. In the thread, uninstalling ESET did nothing because the block lived in the router/ISP path. Always verify network routes before reinstalling mail clients. [Elektroda, lufa9999, post #16707180]
Can a quick settings change alone solve this?
If your settings already match WP’s requirements, client tweaks rarely help. The resolution came from unblocking ports, not changing Thunderbird fields. Fix the path first; settings are already correct. [Elektroda, lufa9999, post #16707230]
Where can I find WP’s official SMTP guidance?
A helper shared WP’s support reference during the thread. Review it to confirm server name, port, and security mode before network tests. Keep it handy when speaking with your ISP. [Elektroda, Kasek21, post #16706377]
