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 Mageia 7 from scratch, it is not an upgrade from 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.
Another temporary workaround : start Akonadi from the command line. $ unset http_proxy; akonadictl start
Please file a bug upstream for such as issue: https://bugs.kde.org/
CC: (none) => geiger.david68210
I did : https://bugs.kde.org/show_bug.cgi?id=412702
Thank you Nicolas for this report, for bugging it upstream, and noting here the upstream bug URL. Thank you DavidG for giving the upstream bug reporting URL. With all that done, this bug header fields set accordingly, assigning to the KDE team.
Keywords: (none) => UPSTREAMAssignee: bugsquad => kdeURL: (none) => https://bugs.kde.org/show_bug.cgi?id=412702
I have got a reply from upstream (Laurent Montel <montel@kde.org>), he marked the bug as RESOLVED FIXED : "it was implemented after your 19.04. So you need to update your pim version." Is there any chance we can backport the change in Mageia 7 ?
Assigning to QA, Advisory: ======================== This kimap update is to provide an explicit option to not use the system proxy setting for IMAP connections. If the system proxy settings are set to use the environment variables http_proxy etc (for compatibility with non-KDE applications), then they are also used for IMAP connections. This is rarely required and will fail unless the proxy is transparent enough. See https://bugs.kde.org/show_bug.cgi?id=407685 and related bugs. These changes adds an IMAP account option to use the proxy for connection (the default is off) and adds in kdepim-runtime the GUI for the setting, which appears as an additional option in the "Advanced" tab of the account settings dialogue. For reference: https://phabricator.kde.org/D21463 https://phabricator.kde.org/D21464 ======================== Packages in 7/core/updates_testing: ======================== kimap-common-19.04.0-1.1.mga7.i586.rpm libkf5imap5-19.04.0-1.1.mga7.i586.rpm libkf5imap-devel-19.04.0-1.1.mga7.i586.rpm kimap-common-19.04.0-1.1.mga7.x86_64.rpm lib64kf5imap5-19.04.0-1.1.mga7.x86_64.rpm lib64kf5imap-devel-19.04.0-1.1.mga7.x86_64.rpm akonadi-kde-19.04.0-1.1.mga7.i586.rpm libakonadi-singlefileresource5-19.04.0-1.1.mga7.i586.rpm libmaildir5-19.04.0-1.1.mga7.i586.rpm libakonadi-filestore5-19.04.0-1.1.mga7.i586.rpm libkmindexreader5-19.04.0-1.1.mga7.i586.rpm libfolderarchivesettings5-19.04.0-1.1.mga7.i586.rpm kdepim-runtime-handbook-19.04.0-1.1.mga7.noarch.rpm akonadi-kde-19.04.0-1.1.mga7.x86_64.rpm lib64akonadi-singlefileresource5-19.04.0-1.1.mga7.x86_64.rpm lib64maildir5-19.04.0-1.1.mga7.x86_64.rpm lib64akonadi-filestore5-19.04.0-1.1.mga7.x86_64.rpm lib64kmindexreader5-19.04.0-1.1.mga7.x86_64.rpm lib64folderarchivesettings5-19.04.0-1.1.mga7.x86_64.rpm Source RPM: ======================== kimap-19.04.0-1.1.mga7.src.rpm kdepim-runtime-19.04.0-1.1.mga7.src.rpm
Source RPM: (none) => kimap-19.04.0-1.mga7.src.rpmAssignee: kde => qa-bugs
Created attachment 11340 [details] List of installed packages, akonadi messages
CC: (none) => bequimao.de
Created attachment 11341 [details] CLI output of akonadictl restart I don't use a system proxy or a proxy setup for Akonadi. I upgrade the packages and found no regressions. Ulrich
As there is no taker from qa with a dedicated proxy, I set the test as ok. Ulrich
Whiteboard: (none) => MGA7-64-OK
Hello, how can I help test the fix ? Or will it be soon pushed to the updates ?
You are welcome to give your ok as the bug reporter. If any doubts about the procedure, please ask on the mailing list qa-discuss@ml.mageia.org or in the Mageia forums. Anyhow, next and last step will be the validation of the bug report and tests. That will happen in a few days. Ulrich
Ok, I will test and confirm it works, when the new packages are pushed to 7. :)
(In reply to Nicolas Costes from comment #12) > Ok, I will test and confirm it works, when the new packages are pushed to 7. > :) Nop, you have to test it right now with the "Testing" one, it's still you who made this request. Without test it can't be pushed to the "Update" repo!
Good, where are the packages, can you please tell me ?
(In reply to Nicolas Costes from comment #14) > Good, where are the packages, can you please tell me ? see the list in comment 6 (Packages in 7/core/updates_testing)
Ok, great. I updated selectively some packages (I wanted to avoid the side effects of updating the numerous packages awaiting for testing) : Kmail now works fine, the "connect using the system proxy settings" checkbox appeared and does its job when checked/unchecked. Thanks a lot :) ! Updated packages : akonadi-kde-2:19.04.0-1.1.mga7.x86_64 glibc-6:2.29-18.mga7.x86_64 lib64kf5imap5-19.04.0-1.1.mga7.x86_64 lib64maildir5-2:19.04.0-1.1.mga7.x86_64
Since the reporter has confirmed that his issue has been fixed, I'm validating, and removing the UPSTREAM marker. Advisory in Comment 6. Thank you, Nicolas.
Keywords: UPSTREAM => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
CC: (none) => tmbKeywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2019-0202.html
Status: NEW => RESOLVEDResolution: (none) => FIXED