Bug 300916

Summary: Reply to a mailing list message sends reply to the list unconditionally instead of the sender
Product: [Applications] kmail2 Reporter: nine
Component: commands and actionsAssignee: kdepim bugs <kdepim-bugs>
Status: CONFIRMED ---    
Severity: critical CC: bugs, kde-bugs, kdenis, montel, tuukka.verho
Priority: NOR    
Version: 5.3.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description nine 2012-05-31 09:04:33 UTC
Today it happened again, that I replied to a message on our internal company mailing list and the answer went to the whole list (all employees) instead of only the single intended recipient. We use mailman as mailing list manager and configured it explicitely to have answers go to the sender only.

In the best case this causes great embarassment and lost productivity for the company. In the worst case this causes sensitive information or private communication to be leaked to a whole mailing list. Therefore this should be considered a security problem (which is the reason for choosing a severity of "Critical").

Reproducible: Always

Steps to Reproduce:
1. open an email that went to a mailing list
2. hit reply

Actual Results:  
The mailing list's address is in the To field instead of the sender's.

Expected Results:  
The sender's email address is in the To field.
Comment 1 Laurent Montel 2012-06-07 06:06:43 UTC
Do you have a "reply-to" header ?
is it configurate for reply to your mailing list ?
Comment 2 nine 2012-06-07 09:38:20 UTC
No. We explicitely configured Mailman to not set a reply-to header, so anwers would _not_ got to the mailing list.

The complete header of the message I replied to (anonymized):

Return-Path: <mitarbeiter-bounces@text.example>
Delivered-To: nine@test.example
Received: from localhost (localhost [127.0.0.1])
	by mail.test.example (Postfix) with ESMTP id 12D9E10B504;
	Thu, 31 May 2012 08:42:56 +0200 (CEST)
X-Virus-Scanned: amavisd-new at test.example
Received: from mail.test.example ([127.0.0.1])
	by localhost (smithers.test.example [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VfIJ3dGZAnD8; Thu, 31 May 2012 08:42:51 +0200 (CEST)
Received: from [10.119.52.1] (mail.test.example [10.119.52.4])
	by mail.test.example (Postfix) with ESMTP id E52FA10B150;
	Thu, 31 May 2012 08:42:50 +0200 (CEST)
X-Original-To: mitarbeiter@mail.test.example
Delivered-To: mitarbeiter@mail.test.example
Received: from localhost (localhost [127.0.0.1])
 by mail.test.example (Postfix) with ESMTP id C65B610B510
 for <mitarbeiter@mail.test.example>; Thu, 31 May 2012 08:42:49 +0200 (CEST)
X-Virus-Scanned: amavisd-new at test.example
Received: from mail.test.example ([127.0.0.1])
 by localhost (smithers.test.example [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 8OvYcSJic9Eq for <mitarbeiter@mail.test.example>;
 Thu, 31 May 2012 08:42:47 +0200 (CEST)
Received: from EXAMPLEJPPC (gateway.test.example
 [10.23.81.4]) (Authenticated sender: jp@test.example)
 by mail.test.example (Postfix) with ESMTPA id 20FD310B504
 for <mitarbeiter@test.example>; Thu, 31 May 2012 08:42:47 +0200 (CEST)
From: "JP" <jp@test.example>
To: <mitarbeiter@test.example>
References: <1338445209.c8B41817.56814@mrburns.test.example>
In-Reply-To: <1338445209.c8B41817.56814@mrburns.test.example>
Date: Thu, 31 May 2012 08:44:19 +0200
Message-ID: <00b101cd3ef8$cdf35420$69d9fc60$@test.example>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
thread-index: AQGX/4kgXwMgZ4EsjTQVrWtKeDpcYZdN8QlA
Content-Language: de-at
Subject: [Mitarbeiter] WG: NEWS LETTER
X-BeenThere: mitarbeiter@test.example
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: <mitarbeiter.test.example>
List-Unsubscribe: <https://mail.test.example/mailman/options/mitarbeiter>,
 <mailto:mitarbeiter-request@test.example?subject=unsubscribe>
List-Archive: <https://mail.test.example/mailman/private/mitarbeiter>
List-Post: <mailto:mitarbeiter@test.example>
List-Help: <mailto:mitarbeiter-request@test.example?subject=help>
List-Subscribe: <https://mail.test.example/mailman/listinfo/mitarbeiter>,
 <mailto:mitarbeiter-request@test.example?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2613704516788665952=="
Errors-To: mitarbeiter-bounces@test.example
Sender: mitarbeiter-bounces@test.example
Comment 3 Myriam Schweingruber 2012-08-18 09:07:15 UTC
Which exact Kmail version is this about and is it reproducible with Kmail 4.8.5 or later? Please set the version field accordingly.
Comment 4 nine 2012-08-18 20:30:21 UTC
Still the same on 4.9.00
Comment 5 Christian Boltz 2012-11-05 22:09:20 UTC
Are you aware that KMail offers multiple ways for reply? Right-click a message and check the "reply" submenu. Options are:
- Reply
- Reply to author
- Reply to all
- Reply to mailinglist

AFAIK "Reply" is the default action when pressing "r", which defaults to reply to the mailinglist if it finds a mailinglist header like List-Post. You might want to use "Reply to author" instead, and maybe change the "r" shortcut to it. (Needless to say that the behaviour of "Reply" isn't the best idea IMHO.)
Comment 6 nine 2012-11-06 07:26:04 UTC
Yes, I am aware. But it's not enough. Since every user has to learn this the hard way, the default should be sensible. I've seen this happen to every single new kmail user at our company and every time it caused quite some embarassment.

Changing keyboard shortcuts does not help if people use the mouse to click on reply. And having to click+hold, wait for a second and hit the right submenu item before releasing, is everything but appropriate for one of the most common actions when using the program.
Comment 7 Denis Kurz 2016-09-24 18:16:29 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 8 Christian Boltz 2016-09-24 18:26:12 UTC
Just tested (in KMail 5.3.0, Frameworks 5.25.0) - the strange behaviour of "reply" is still unchanged :-(

The "Version" dropdown doesn't offer 5.3.0, and it's unlikely that this was accidently fixed more than 4 years after being reported. Therefore I'm moving this bugreport to "Git (master)".
Comment 9 Graeme Hewson 2016-10-04 10:27:41 UTC
I have this problem in 5.1.3, with messages from the mailing list going into their own folder.

I found that in the Folder Properties dialogue, Mailing List tab, the Post to List address had been set automatically. When I removed this address, replies to private mail went to the correct address.
Comment 10 gjditchfield 2019-10-09 17:00:13 UTC
*** Bug 357464 has been marked as a duplicate of this bug. ***