|
Bill, It depends on your customer makup. My FP rate with a MAILFROM filter would be close to 90% if not more because of several sites that are configured to send form submissions as being an account from the same domain. SPAMDOMAINS would be a better test because the Web sites and domain based E-mail often shares the same reverse DNS lookup, but not in cases where they are just using aliases for forwarding. I have several customers that have software that sends out automated messages claiming to be from their own domains, such as firewalls and the like, and then I have some customers with sites hosted in different facilities that forge the From address for ecommerce. All of this is before you get the refer-a-friend and gift card stuff. I see all of this with less than 250 actual accounts and just 50 domains hosted on my server at present. If you don't do a lot of Web hosting, you might not see much of a problem, or if you do hosting for sites without forms configured in that way, you also wouldn't notice it. I personally don't want to be whitelisting E-mail as the result of being alerted to the problem by a customer that rightfully assumed that the From address should be their own when setting up a script on a Web site. Spam that forges the from address is likely to fail many technical tests because forging isn't generally limited to the from address, typically they forge the HELO and screw many other things up in the headers. I almost never get spam that passes the filters that uses my own address anymore. As my own sample of FP's seen in the last 5,000 or so messages would be the following: - Used Vehicle Inquiry - [name removed] (about 20 of these) - New Vehicle Inquiry - [name removed] (about 20 of these) - Parts Inquiry - [name removed] (about 5 of these) - Website Contact Form (2 of these) - New firmware available. (1 of these, sent from a SonicWall) - From your friend: [name removed] (2 of these sent through SendAFriend) - Internet Order # [numbers] (3 of these) In addition to these there are GM and Mazda corporate Internet lead notifications that fake the from address as the address they are sending them to (these have problems with these poorly configured servers). Again though, depending on your customer makup, your mileage may vary. SPAMDOMAINS would have not FP'd on a few of the first 4 examples because they are locally hosted on the same domain as the receiver, but would have FP'd on MAILFROM.. Everything else would have FP'd on both tests. Matt Bill Landry wrote:
|
- RE: [Declude.JunkMail] blocking spam faked as coming from ... Colbeck, Andrew
- Re: [Declude.JunkMail] blocking spam faked as coming ... Glenn \\ WCNet
- Re: [Declude.JunkMail] blocking spam faked as com... R. Scott Perry
- RE: [Declude.JunkMail] blocking spam faked as coming ... Colbeck, Andrew
- Re: [Declude.JunkMail] blocking spam faked as com... Matthew Bramble
- Re: [Declude.JunkMail] blocking spam faked as... Bill Landry
- Re: [Declude.JunkMail] blocking spam fake... Matthew Bramble
- Re: [Declude.JunkMail] blocking spam... Bill Landry
- Re: [Declude.JunkMail] blocking ... Matthew Bramble
- Re: [Declude.JunkMail] block... Matthew Bramble
- [Declude.JunkMail] COUNTRY t... Scot Desort
- Re: [Declude.JunkMail] COUNT... R. Scott Perry
- Re: [Declude.JunkMail] blocking ... Matthew Bramble
- Re: [Declude.JunkMail] block... Bill Landry
- Re: [Declude.JunkMail] block... Matthew Bramble
- Re: [Declude.JunkMail] block... Eje Gustafsson
- Re: [Declude.JunkMail] block... Matthew Bramble
- Re: [Declude.JunkMail] block... Bill Landry
- Re: [Declude.JunkMail] block... Matthew Bramble
