Description of problem: The Akonadi IMAPs daemon incorrectly uses the system wide proxy settings. It used to work fine, even when using a proxy (it would ignore it). Version-Release number of selected component (if applicable): How reproducible: This is my job computer, our company is behind a proxy. The IMAP server is inside the company. I tried to setup "no_proxy", change KDE/Plasma proxy setting to various values/no value at all : no change ! I cannot get my emails. PS : I installed this computer (Mageia 7) from scratch, it is not an upgrade from Mageia 6. I only have one Mageia 7 computer, cannot test on another one. Steps to Reproduce: 1. Setup the system wide proxy setting in Drakconf 2. Setup Kmail IMAPs account (inside the compagny, no need for proxy) 3. Kmail won't access the IMAPs server; packet sniffing shows that the process "akonadi_imap_resource" makes CONNECT requests to our company proxy (which refuses imaps) Temporary - but not acceptable - solution : I removed the system-wide proxy settings and configured it inside the various programs that need it. But this breaks some programs that don't have a proxy setting en rely on the system-wide setting. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.3.2-desktop-1.mga7 KDE Plasma Version: plasma-workspace-5.15.4-1.mga7, plasma-framework-5.57.0-1.mga7 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.2 akonadi-19.04.0-1.mga7
Another temporary workaround : start Akonadi from the command line. $ unset http_proxy; akonadictl start
In the imap account dialog, "Advanced" tab, there's a "connect using the system proxy settings" box. What's this checkbox state?
Created attachment 123084 [details] My Kmail version does not have any imap proxy settings checkbox Hi, I do not have such a checkbox; see included attachment.
it was implemented after your 19.04. So you need to update your pim version.
I'm one of the mageia's kde maintainer. Which packages should be updated? or which commits could fix this issue? this is on a stable release distro so it's a bit difficult to make a big update.
The affected package is KIMAP. See bug 407685 for reviews and commits. Maybe this bug should be marked as a duplicate of that?
(In reply to Jonathan Marten from comment #6) > The affected package is KIMAP. See bug 407685 for reviews and commits. Thank you, I'll look backporting these patches. > Maybe this bug should be marked as a duplicate of that? Yes it can :)