# Bayesian Kryptonite - spoofed email

**URL:** <https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069>\
**Category:** blog\
**Created:** [June 30, 2005, 12:00am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069 "2005-06-30T00:00:00Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![codinghorror](https://discourse.codinghorror.com/user_avatar/discourse.codinghorror.com/codinghorror/32/36371_2.png) [@codinghorror](https://discourse.codinghorror.com/u/codinghorror)\
**Post date:** [June 30, 2005, 12:00am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069/1 "2005-06-30T00:00:00Z")

</div>

I use [POPFile bayesian filtering](http://www.codinghorror.com/blog/archives/000086.html) to keep email spam at bay. With a little training, this works amazingly well-- I'm at 99.8% accuracy, and that's with a little over a month of "training" precipitated by a recent server migration. But bayesian filtering has one big weakness that I'm seeing more and more: [spoofed emails](http://www.cert.org/tech_tips/email_spoofing.html).

* * *
This is a companion discussion topic for the original blog entry at: [http://www.codinghorror.com/blog/2005/06/bayesian-kryptonite---spoofed-email.html](http://www.codinghorror.com/blog/2005/06/bayesian-kryptonite---spoofed-email.html)

---

<div class="post-metadata">

**Author:** ![SushantB](https://discourse.codinghorror.com/letter_avatar_proxy/v2/letter/s/e99b99/32.png) [@SushantB](https://discourse.codinghorror.com/u/SushantB)\
**Post date:** [June 30, 2005, 12:00am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069/2 "2005-06-30T00:00:00Z")

</div>

I wonder if they have filters that say more than 3 links and its junk…because I never get emails with more than 2 unless they are junk.

---

<div class="post-metadata">

**Author:** ![DanielP](https://discourse.codinghorror.com/letter_avatar_proxy/v2/letter/d/82dd89/32.png) [@DanielP](https://discourse.codinghorror.com/u/DanielP)\
**Post date:** [July 1, 2005, 12:00am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069/3 "2005-07-01T00:00:00Z")

</div>

How many people send from mail servers other than the name they’re actually claiming nowadays? I know for a long while I was using [name@pritchetts.us](mailto:name@pritchetts.us) but sending from [mail.comcast.net](http://mail.comcast.net). If most people don’t do that, maybe blacklist mails where the sender doesn’t match the server? I don’t have much spam blocking experience (I just stick with whatever Thunderbird does for me) but I did have to run a spam filter on a Win2k3 server for a few months. I used GFI MailEssentials, which has several different forms of filtering that work independently:

Blacklists, whitelists, bayesian, keyword, and some other stuff I don’t remember.

The upside was that I could pretty easily add and remove key words (prozac) to the word filter and let the bayesian filter take care of the rest. One of my favorite features was the auto whitelist, which whitelisted anyone I ever sent an outgoing mail to.

About web services (eBay etc.) not sending email, I don’t know if the world is ready for that yet. It’s still the only ubiquitous form of net communication that a lot of people are willing to give out their connection details for. What’s next, instant messenger?

---

<div class="post-metadata">

**Author:** ![DanielP](https://discourse.codinghorror.com/letter_avatar_proxy/v2/letter/d/82dd89/32.png) [@DanielP](https://discourse.codinghorror.com/u/DanielP)\
**Post date:** [July 1, 2005, 12:00am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069/4 "2005-07-01T00:00:00Z")

</div>

Sorry for not bothering to read your POPFile entry until after I commented, it looks like you’re on the right track looking at multiple filtering tools getting you from 98% to 100%. I certainly can’t think of anything better at the moment.

I’m glad you have an RSS feed.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://discourse.codinghorror.com/user_avatar/discourse.codinghorror.com/codinghorror/32/36371_2.png) [@codinghorror](https://discourse.codinghorror.com/u/codinghorror)\
**Post date:** [July 2, 2005, 12:00am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069/5 "2005-07-02T00:00:00Z")

</div>

How many people send from mail servers other than the name they’re actually claiming nowadays?

That is the other way to attack the problem: actually validate the identity of the sender (or at least the server sending the email). There have been some baby steps in this direction from Yahoo and Hotmail but I’m not sure if anything substantive has come from it yet.

It’s definitely a good idea, but the architecture of POP3/SMTP isn’t built around identity or even security-- so it’s hard to retrofit.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://discourse.codinghorror.com/user_avatar/discourse.codinghorror.com/codinghorror/32/36371_2.png) [@codinghorror](https://discourse.codinghorror.com/u/codinghorror)\
**Post date:** [July 2, 2005, 12:00am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069/6 "2005-07-02T00:00:00Z")

</div>

I mean, if you’re going to do something, at least try a little harder.

Right. Some of the spoofs I’ve seen recently were quite good. Very professional looking, no misspellings, etcetera.

My rule of thumb is “could my Mom tell this was fake?” For a lot of recent spoofs, the answer is no.

---

<div class="post-metadata">

**Author:** ![RodolfoS](https://discourse.codinghorror.com/letter_avatar_proxy/v2/letter/r/f19dbf/32.png) [@RodolfoS](https://discourse.codinghorror.com/u/RodolfoS)\
**Post date:** [July 5, 2005, 12:00am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069/7 "2005-07-05T00:00:00Z")

</div>

In paypal case:  
[paypal.com](http://paypal.com). 3600 IN TXT “v=spf1 mx include:s.\_spf.ebay.com include:m.\_spf.ebay.com include:p.\_spf.ebay.com include:c.\_spf.ebay.com ~all”  
[paypal.com](http://paypal.com). 3600 IN TXT “spf2.0/pra mx include:s.\_sid.ebay.com include:m.\_sid.ebay.com include:p.\_sid.ebay.com include:c.\_sid.ebay.com ~all”

That’s it.. everything coming thru paypal must come from those ranges… this way just block everything that fail on SPF tests.

Baysian by itself can’t handle problems like this one.

---

<div class="post-metadata">

**Author:** ![Jim\_McKeeth](https://discourse.codinghorror.com/letter_avatar_proxy/v2/letter/j/a88e4f/32.png) [@Jim\_McKeeth](https://discourse.codinghorror.com/u/Jim_McKeeth)\
**Post date:** [July 6, 2005, 12:00am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069/8 "2005-07-06T00:00:00Z")

</div>

Actually the logical choice would be for them to offer personalized RSS / ATOM / RDF feeds for their users. So I can get one feed from them that has all their general news (customized by me) and all news specific for me. Through in some HTTPS if they want and I know I am getting the straight dope from the horses mouth.

---

<div class="post-metadata">

**Author:** ![MichaelB](https://discourse.codinghorror.com/letter_avatar_proxy/v2/letter/m/b19c9b/32.png) [@MichaelB](https://discourse.codinghorror.com/u/MichaelB)\
**Post date:** [July 9, 2005, 12:00am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069/9 "2005-07-09T00:00:00Z")

</div>

It’s still in dev mode, but at a href="[http://www.feed-mail.com](http://www.feed-mail.com)"[http://www.feed-mail.com/a](http://www.feed-mail.com/a) we’re working on developing a Messaging over RSS application.

It sets up reciprocal RSS feeds between you and your contacts so that you can message back and forth (like email), but entirely over RSS.

Hopefully by switching from a SendTo to a PullFrom architecture it could drastically reduce the amount of spam and phishing people have to deal with.

---

<div class="post-metadata">

**Author:** ![MikeD](https://discourse.codinghorror.com/letter_avatar_proxy/v2/letter/m/ed655f/32.png) [@MikeD](https://discourse.codinghorror.com/u/MikeD)\
**Post date:** [July 15, 2005, 12:00am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069/10 "2005-07-15T00:00:00Z")

</div>

Both [spoof@paypal.com](mailto:spoof@paypal.com) and [spoof@ebay.com](mailto:spoof@ebay.com) work fine. I always report PayPal and Ebay spoof messages. Note, though, that [spoof@ebay.com](mailto:spoof@ebay.com) won’t accept an attached message - you have to forward the message to them.

---

<div class="post-metadata">

**Author:** ![MartyT](https://discourse.codinghorror.com/letter_avatar_proxy/v2/letter/m/8dc957/32.png) [@MartyT](https://discourse.codinghorror.com/u/MartyT)\
**Post date:** [February 6, 2010, 12:00am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069/11 "2010-02-06T00:00:00Z")

</div>

GMail actually has a decent spam filter, and it also has good spoof e-mail detection. I got a phishing e-mail the other day, that was spoofing the e-mail address, [service@paypal.com](mailto:service@paypal.com), and I got a bright red message at the top that said the following:

“Warning: This message may not be from whom it claims to be. Beware of following any links in it or of providing the sender with any personal information.”

Now admittedly, anybody in our line of business should know immediately whether an e-mail is legitimate or not, but it’s still a good thing for the more non-technical people using e-mail.

On an amusing note, the e-mail I’m referring to was the worst attempt at phishing I’ve ever seen. Check out this snippet from the body of the e-mail:

“U need to update ur account once again, u forgot fill in ATM PIN at from update, come to link below and do it.”

I mean, if you’re going to do something, at least try a little harder.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://discourse.codinghorror.com/user_avatar/discourse.codinghorror.com/codinghorror/32/36371_2.png) [@codinghorror](https://discourse.codinghorror.com/u/codinghorror)\
**Post date:** [January 7, 2025, 6:39am UTC](https://discourse.codinghorror.com/t/bayesian-kryptonite-spoofed-email/1069/12 "2025-01-07T06:39:55Z")

</div>

Closed on January 7, 2025, 6:39am UTC


