Filters do not work on the body of the message if the message is in base64. Reproducible: Always Steps to Reproduce: 1. Create filter (Body messages) 2. 3. Actual Results: Not work filters
Could you give me an exemple ? Attach a email as mbox here. Give exact filter that you used please.
I'm able to replicate this easily. Most common message that _doesn't_ filter properly for me and which has a Base64 encoded body, are PayPal payment notifications. They used to arrive with: Content-Transfer-Encoding: quoted-printable Content-Type; text/plain; charset="windows-1252" and those ones would filter just fine. The new ones now arrive with: Content-Transfer-Encoding: base64 Content-Type: text/plain; charset=UTF-8 and do *not* match at all with the "Body of Message" filtering rule. My first guess would be that its trying to match/filter based on the raw message body, instead of the decoded message body.
Bug 311633 sounds similar to this, if not a duplicate.
Created attachment 101206 [details] email with the Base64 encoded text: "The file 4207_66496070.zip has been infected with the virus JS/Nemucod.SMK9!tr, and has been removed." Attaching an example email where a filter intendet to move to Spam if body contains "Nemucod" fails. This is the filter definition copied from .config/akonadi_mailfilter_agentrc): [Filter #0] Applicability=2 AutomaticName=true ConfigureShortcut=true ConfigureToolbar=false Enabled=true StopProcessingHere=true ToolbarName=<<body>>: Nemucod accounts-set=akonadi_imap_resource_0 action-args-0=224 action-name-0=transfer actions=1 apply-on=check-mail,manual-filtering contentsA=Nemucod fieldA=<body> funcA=contains identifier=CBlqQTvFEp7ZHSUb name=<<body>>: Nemucod operator=and rules=1 This is from the filter log viewer: [11:41:08] Esecuzione regole di filtro: (verifica tutti i criteri seguenti) "<body>" <contains> "Nemucod" [11:41:08] 0 = "<body>" <contains> "Nemucod"
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!