http://blogs.msdn.com/tzink/archive/2008/11/17/categories-of-problems-in-outbound-spam.aspxBeing a hosted service, we have a number of customers who share an outbound IP range.&#160; If one of those customers starts to misbehave, their actions can affect everyone else. We've lot about outbound spam this past year.&#160; We've implemented aenCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/tzink/archive/2008/11/17/categories-of-problems-in-outbound-spam.aspx#9115484Tue, 18 Nov 2008 05:28:14 GMT91d46819-8472-40ad-a661-2c78acb4018c:9115484Categories of problems in outbound spam | Tmao Coders<p>PingBack from <a rel="nofollow" target="_new" href="http://www.tmao.info/categories-of-problems-in-outbound-spam/">http://www.tmao.info/categories-of-problems-in-outbound-spam/</a></p> http://blogs.msdn.com/tzink/archive/2008/11/17/categories-of-problems-in-outbound-spam.aspx#9927490Mon, 23 Nov 2009 20:06:49 GMT91d46819-8472-40ad-a661-2c78acb4018c:9927490Darrell<p>Is it feasible to apply some volume-based checking on top of normal filtering for outbound mail? The most troublesome false positives we get with our outbound spam filters are the single emails (with less than a dozen or so addresses included in cc) that our filters reject as spam due to content their content. These false positives draw the most ire from the affected users. It seems to me that actual spam being sent from a compromised account would not send individual emails at this low of volume and/or with this low a number of cc recipients. Would it help if outbound spam filters could factor in this type of non-spammer like behavior? If not, do you have other suggestions?</p>