On 07/24/2012 10:00 AM, Camaleón wrote:
On Mon, 23 Jul 2012 20:44:46 +0300, Mika Suomalainen wrote:

Icedove always shows warning "This message might be scam" when the
sender is using @google.com address.

You really meant "scam" and not spam", right? I ask because they are two
different things treated differently from Icedove.

Is this intended behaviour, does anyone else see this too and should I
report a bug?

(...)

I don't think that's intended at all (btw, it does not happen here with
TB 14) but how did you determine the problem? I mean, all of these apply?

- You tested with messages that really came from Google servers.
- Those messages were not scam at all but legitime (i.e., no suspicious
content nor embbeded html code).
- E-mails coming from different senders remain unaffected
- You opened a message locally (file → open...) and it is still being
detected as scam.

Also, take a look into this article to understand how this functionality
works:

https://support.mozillamessaging.com/en-US/kb/thunderbirds-scam-detection

OTOH, I find TB's ratio of false possitives for "scam" to be very low.

Greetings,


I too received a message marked as "scam" by icedove recently but it was not from a googlemail addr.

I believe it might be correct as I don't have an account in Europe.

-------------------------------

Vi har for nylig fastslået, at forskellige computere på din Verified by Visa-konto,
kodeord og flere fejl var til stede før forbindelsen.

Vi har nu brug for dig til at bekræfte dine kontooplysninger
Verified by Visa.
dette ikke er afsluttet inden for 48 timer,
ville vi være tvunget til at indstille din konto på ubestemt tid, da det kan bruges til
svigagtige formål.
Tak for din forståelse på denne måde. For at bekræfte din online-konto:.


https://www.pbs.dk/eu/servver/done/nets-Acc990755

----------------------------



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/500eb9a3.2040...@gmail.com

Reply via email to