Bug 335254

Summary:	Scam detection does detect scam, but composer does not warn when sending scam
Product:	[Applications] kmail2	Reporter:	Florian Reinhard <florian.reinhard>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel
Priority:	NOR
Version:	4.13.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Florian Reinhard 2014-05-23 20:05:12 UTC

Scam detection does detect scam, but composer does not warn when sending scam

Reproducible: Always

Steps to Reproduce:
1. Go to google maps
2. Create a link
3. Use the built in shorten feature
4. Compose a new mail in Kmail
5. paste the provided http://goo.gl/... URL to your messge
6. send it to your self
Actual Results:  
The message you recieve is marked as scam.

Expected Results:  
Get warned that you are about to send scam prior to sending it

Comment 1 Laurent Montel 2014-05-24 05:55:18 UTC

If you send a short url you know it no ?
So why I will mark as scam when you paste it ?

Comment 2 Florian Reinhard 2014-05-24 10:04:29 UTC

Yes you know that you send a short url, but in first place you don't know that kmail (and maybe other mail programms) are going to mark this mail as scam! So the user (stupid users like me) should be informed that they are about to produce a mail that looks like scam to kmail.

I don't know if i am able to explain my self well enough. It just does not make sense to be able to send a mail without warning that is detected as scam by your very own mail program.

What i would expect is:
1. click send
2. kmail does the scam detection on the composed mail
3. inform the user that this mail looks like scam and what makes it look like scam. Just like the dialog you get when you click on "(Details...)" in the scam notification of an incoming mail
4. optionally re-edit the mail or send it anyways

Comment 3 Denis Kurz 2016-09-24 18:05:43 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 4 Denis Kurz 2017-01-07 21:37:30 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.