Re: Update: Messenger Spam
From: David J. Grabiner (grabiner_at_alumni.princeton.edu)
Date: 09/13/03
- Next message: George: "Re: TCP Port 53 Closed"
- Previous message: BoB: "Re: M$ Messenger still has to be blocked after disable....any help ? TIA"
- In reply to: Lawrence Baldwin: "Update: Messenger Spam"
- Next in thread: derek / nul: "Re: Update: Messenger Spam"
- Reply: derek / nul: "Re: Update: Messenger Spam"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 12 Sep 2003 21:57:05 -0400
"Lawrence Baldwin" <baldwinL@SPAMMENOTmynetwatchman.com> writes:
> I spent a good amount of time updating my documentation the the blasted
> Messenger Spam phenom:
>
> http://www.mynetwatchman.com/kb/security/articles/popupspam/index.htm
Interesting. Microsoft explains how to block these with a firewall, and
which ports to close, but doesn't discuss the obvious step of turning
off Messenger.
> Psloss was also good enough to update our WinPopUP tester to include the new
> ports the blasted spammers are jamming these messages to: udp/1026-1029 as a
> result of udp/135 filtering by most ISPs.
And by firewalls; I closed the ports that Microsoft said to close but it
still didn't block all the spam.
-- David Grabiner, grabiner@alumni.princeton.edu, http://remarque.org/~grabiner Baseball labor negotiations FAQ: http://remarque.org/~grabiner/laborfaq.html Shop at the Mobius Strip Mall: Always on the same side of the street! Klein Glassworks, Torus Coffee and Donuts, Projective Airlines, etc.
- Next message: George: "Re: TCP Port 53 Closed"
- Previous message: BoB: "Re: M$ Messenger still has to be blocked after disable....any help ? TIA"
- In reply to: Lawrence Baldwin: "Update: Messenger Spam"
- Next in thread: derek / nul: "Re: Update: Messenger Spam"
- Reply: derek / nul: "Re: Update: Messenger Spam"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|