Bug 136281

Summary:	deny sending mail with certain (sender;recipient) "fingerprint"
Product:	[Applications] kmail2	Reporter:	Imre Péntek <pentek.imre>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	carl, luigi.toscano
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Imre Péntek 2006-10-25 09:19:38 UTC

Version:            (using KDE KDE 3.5.3)
Installed from:    Unlisted Binary Package

So in Kmail we all have a default sending account (default sending e-mail address), but maybe we forget to manually change it to send mail to a mailing lists. If we do so, this mail probably gets delayed, rejected. Maybe kmail should warn the user (or even better: it should override the sender e-mail address) if (sender;recipient) pair matches one of the preset list (or automatically override sending email address to the desired value if destination-address found in the (recipient;desired-sender-address) chart).
As I commonly forget to manually override sending email address, I would be happy with this feature.
Anyways, thank you for providing this nice software.

Comment 1 Myriam Schweingruber 2012-08-18 07:53:36 UTC

Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented.
Thank you for your understanding.

Comment 2 Luigi Toscano 2012-08-19 00:30:42 UTC

Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.

Comment 3 Imre Péntek 2012-08-19 10:55:17 UTC

Thank you, however for my besk knowledge, kmail2 doesn't contain the feature, right now I don't need it. Have a nice day!

Comment 4 Carl Schwan 2024-03-12 22:07:18 UTC

Marking it as duplicate of 182614 as it is fundamentally the same idea of making sure that an email is sent from the correct identity depending on the recipient.

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