Re: The Bat!: A Better Mousetrap

example, you could catch most spam by simply rejecting email that didn't contain your address on the To or CC lines. Spammers learned this and now individually address most of their spam. Here's a Web page that discusses spam and Bayesian Filtering in detail: http://www.paulgraham.co

Re[2]: A Useful spam filter

mail out of hand. This seems kinda draconian to me. I'll bet a lot of those rejections are false positives. POPFile actually reads the HTML and can correctly distinguish spam-HTML from non-spam-HTML. Anyway, that's my (limited) experience. -- Joel Johnstone Using The Bat! v1.53t

Re[2]: A Useful spam filter

I spent about six months writing software that looked for individual > spam features before I tried the statistical approach. What I found > was that recognizing that last few percent of spams got very hard, and > that as I made the filters stricter I got more false positives. -- Joel Johnst

Re[3]: Multiple Email Clients running simultaneously?

mailbox so only one client can connect at a time. But even that generally won't cause a problem. The clients should just retry until they get through. -- Joel Johnstone Using The Bat! v1.53t on Windows NT 5.0 Build 2195 Service Pack 3 Current ver

Re: Setting up a "Kill Filter"

rings with the pipe | character to create a Logical Or condition. For example, to filter out Sam & Dan, you could write: [EMAIL PROTECTED]|[EMAIL PROTECTED] Sender Yes -- Joel Johnstone Using The Bat! v1.53t on Windows NT 5.0 Build 2195 Service Pack 3 _

Re[2]: Setting up a "Kill Filter"

OTECTED]|[EMAIL PROTECTED] As it turns out, you don't need to select Regular Expressions to use the '|' operator. I guess they included that as a simple shorthand. -- Joel Johnstone Using The Bat! v1.53t on Windows NT 5.0 Build 2195 Service Pack 3