Bug 109071 - apparently uses random sender identity
Summary: apparently uses random sender identity
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-14 13:07 UTC by Peter Eisentraut
Modified: 2018-09-04 18:20 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Eisentraut 2005-07-14 13:07:18 UTC 
Version:            (using KDE KDE 3.4.1)
Installed from:    Debian testing/unstable Packages

I have several identities configured in KMail.  To one specific folder I have assigned one of those identities (not the default one) to be used as sender identity.  Nevertheless, it seems that KMail randomly uses other identities for specific messages in that folder based on some secret intelligence scheme.  But if I set an identity for a folder it should be straightforward to use exactly that identity always.
Comment 1 Kumaran Santhanam 2009-09-04 01:55:14 UTC 
This still happens in Kontact 4.3.0 / KMail 1.12.0.
Has anybody else experienced this behavior?
Comment 2 Martin Koller 2009-09-29 22:21:15 UTC 
Can you attach one message where the correct identity is used and one which uses the wrong one, please ?
Is this always reproducible with such 2 mesages ?
Comment 3 Kumaran Santhanam 2009-09-29 22:55:01 UTC 
The pattern of behavior on my version seems to be that it always sets the identity to the one that was used in the last sent message.  It seems to be completely independent of the folder or account.  This is quite inconvenient because it requires constant vigilance to send email with the correct identity.
Comment 4 Andrew Crouthamel 2018-09-04 18:20:54 UTC 
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!