Bug 329988 - Pipe Trough filter breaks 'To:' field for messages sent to undisclosed recepients
Summary: Pipe Trough filter breaks 'To:' field for messages sent to undisclosed recepi...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Mail Filter Agent (show other bugs)
Version: 4.12
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-15 07:37 UTC by Patrick
Modified: 2017-01-07 23:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick 2014-01-15 07:37:33 UTC
Messages sent by Arch Linux AUR notification system have a 'To:' field which contains 'undisclosed-recipients: ;'. After filtering this message for spam or viruses, the field is stripped to 'To' without a colon. This causes Kmail to misinterpret the next line in the header, in this case the subject.

Reproducible: Always

Steps to Reproduce:
To reproduce the bug, you have to be subscribed to an Arch Linux AUR notification feed.
1. Disable automatic filtering and add one of the pipe trough filters to the Apply Filter menu (e.g. clamav).
2. When a message from the Arch Linux AUR notification system arrives, apply a pipe through filter.
Actual Results:  
Part of the header:
Received: by alderaan.archlinux.org (Postfix, from userid 992) id 4541624047; Tue, 14 Jan 2014 19:13:53 +0000 (UTC)
To
Subject: AUR Comment for chromium-pepper-flash-stable
Reply-To: nobody@archlinux.org
From: aur-notify@archlinux.org

Expected Results:  
Part of the header:
Received: by alderaan.archlinux.org (Postfix, from userid 992)
	id 4541624047; Tue, 14 Jan 2014 19:13:53 +0000 (UTC)
To: undisclosed-recipients: ;
Subject: AUR Comment for chromium-pepper-flash-stable
Reply-to: nobody@archlinux.org
From: aur-notify@archlinux.org

I haven't been able to reproduce the bug by sending a mail to undisclosed recipients by myself.
Comment 1 Denis Kurz 2016-09-24 20:45:19 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Patrick 2016-09-25 08:52:24 UTC
I can't reproduce this bug because I don't receive messages addressed to unresolved recipients anymore.
Comment 3 Denis Kurz 2017-01-07 23:17:55 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.