On 11/21/05, Jeff Chan <[EMAIL PROTECTED]> wrote: > detect it, then yes your IPs can get blacklisted. The best way > to solve that is to stop the emission of spam from your network.
It's easier to do when the source is identified. > As was already suggested, one good way to do that is to block > direct port 25 output from your network and instead direct users Irrelevant in this case since it would appear this incident was instigated by an Exchange user, and Exchange itself is used for sending the mail. (Can Exchange be viewed as virusware?) > While SpamCop's trap addresses don't provide visible analyses of > headers IIRC, user reports do, so that you can see how the We never received a user report, nor was a report visible using our account, only the indication of the IP being blocked. (Perhaps our greylisting blocked the user report.) > You can also sign up for an account that gives periodic reports > for your networks. Yup. Already have. > As has already been noted, this is not an appropriate place to > b!tch about SpamCop. Better to discuss it on the SpamCop > forums: Thanks for the reminder, and the followups from others. Amos
