Bug 22789 - Kmail filter dialogue will scramble command line
Summary: Kmail filter dialogue will scramble command line
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-17 13:38 CET by Dag Nygren
Modified: 2020-08-16 16:31 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Dag Nygren 2018-03-17 13:38:02 CET
Description of problem:
Tried to set up a mail filter that would execute a command sending it the from info of the email. (Manual filter), The command line is scrambled when you apply it.

Version-Release number of selected component (if applicable):
Kmail 5.4.3

How reproducible:
Akways

Steps to Reproduce:
1. Enter filter action "Execute command" and give a command "foo %{from}"
2. Press Apply
3. Watch the % being replaced by %25 on the line

Additionally the From address is NOT sent to the script as documented, but only a path to a temporary copy of the message. Also tried to manually edit the config file, but there is still not any FROM info sent to the script.
Comment 1 Dag Nygren 2018-03-17 14:52:40 CET
Additional info:
Editing the config file manually does seem to work if I restart kmail and akonadi after the edit. In other words the only problem is the config dialog which will not allow the %{from} but transforms it into the wrong value "%25{from}" in the config file.
The %{from} is also replaced with the complete "From: c...." line from the header and NOT with the from address only. Not a big problem, but could be documented...
Marja Van Waes 2018-03-17 17:15:37 CET

Assignee: bugsquad => kde
CC: (none) => marja11

Comment 2 Aurelien Oudelet 2020-08-16 16:31:53 CEST
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Status: NEW => RESOLVED
CC: (none) => ouaurelien
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.