I configured a socks proxy in the Proxy tab from the Misc section of KMail's configuration dialog. Even after restarting KMail and Akonadi, the proxy isn't being used to connect to the IMAP server. Reproducible: Always Steps to Reproduce: 1. Configure a proxy server in Settings → Configure KMail → Misc → Proxy. 2. Fetch IMAP emails. 3. Verify in the proxy's log or lsof of the imap resource process that the conection isn't going through the proxy. Actual Results: The conection isn't going through the proxy. Expected Results: The IMAP conection goes through the proxy.
I have the same problem in Debian Jessie (KDE 4.14.2). Although i configured the proxy in KDE's System Settings manually in exactly the same way as in Icedove (Debian's version of Thunderbird), I cannot send and receive mail with Kmail, while Icedove is working fine. The http proxy seems to work (Akregator downloads new feeds without a problem). Sometimes the imap resource of my mail account is shown as offline in Akonadi's settings, sometimes it is supposedly online, but fetching email fails without an error message.
I can confirm this bug. After successfully setting account up at home it would stop working at my work place (behind proxy environment). Getting error message "Unable to connect to the server, please verify the server address." System proxy settings are set up and functioning well, but seems akonadi/kmail ignoring proxy settings. Akonadi 1.13.0 KMail: 4.14.10
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.