Matt Kettler writes: >That and SA might not be able to accurately determine what IP needs to be >reported.. (ie: is your first MX the most recent, or the second most recent >received: line? is one of them forged to make it appear that a message went >to your secondary MX, then to the primary and got scanned there, when in >fact it came directly in?)
This I think is what the poster is warning against. There are many tools which will send spam reports to entirely the wrong places; I get lots to the SpamAssassin.org abuse address as a result, due to that URL appearing in tagged-as-spam messages. They trigger on mailing list headers, forged IPs, URLs appearing in the message, etc. etc. etc. Many abuse desk staff have reported they bit-bucket automated report messages from several tools, for this reason -- 99% of them are FPs. However, I have heard that spamcop's reporting tool will do a decent job of it; and if I recall correctly Theo's "handlespam" script will report via spamcop if an account is set up. --j. ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
