Bug 161706

Summary:	reply to mailing list: incorrect identity is used
Product:	[Unmaintained] kmail	Reporter:	Maciej Pilichowski <bluedzins>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bjoern, finex, lemma, martin.fitzpatrick
Priority:	NOR	Keywords:	testcase, triaged
Version:	SVN trunk (KDE 4)
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Maciej Pilichowski 2008-05-06 14:09:59 UTC

Version:            (using KDE 3.5.9)
Installed from:    SuSE RPMs

I get mail from mailing list but not address to me (To field) but to mailing list subscribers. When I try to reply to this mail my default identity is used instead of identity for this mail account which the mail was received.

I found several similar reports:
https://bugs.kde.org/show_bug.cgi?id=81416 -- the message is not moved though
https://bugs.kde.org/show_bug.cgi?id=73215 -- the mail account is known to KMail -- it is just another identity
https://bugs.kde.org/show_bug.cgi?id=58886 -- reverse complain, to use def.identity instead of To
https://bugs.kde.org/show_bug.cgi?id=140719 -- identity per folder issue

Comment 1 Martin Fitzpatrick 2009-04-04 03:43:03 UTC

Thanks for reporting the bug Maciej. I can confirm in KDE 4.2.2 (Kubuntu). 

[testcase]
Find an email in your Inbox directly address to you (same account), click Reply. Correct identity will be used.

Find an email in your Inbox not directly addressed to you (mailing list/distribution list), click Reply. Default identify will be used (incorrect).

Comment 2 Martin Fitzpatrick 2009-04-04 16:38:32 UTC

*** Bug 151933 has been marked as a duplicate of this bug. ***

Comment 3 Michael Leupold 2009-04-04 16:53:59 UTC

I can't reproduce this using dIMAP but if I copy such a mail to my local inbox
it will use the default address instead of the one I received this on. The mail
has a "Delivered-To" header which seems to be disregarded.

Comment 4 Björn Ruberg 2010-01-17 00:34:05 UTC


*** This bug has been marked as a duplicate of bug 58886 ***