Re: [Dshield] Re: [Full-Disclosure] Windows Messenger Popup Spam on UDP Port 1026
From: Roy S. Rapoport (full-disclosure_at_ols.inorganic.org)
Date: 06/22/03
- Previous message: JT: "RE: [Full-Disclosure] Destroying PCs remotely?"
- In reply to: Dietmar Goldbeck: "Re: [Dshield] Re: [Full-Disclosure] Windows Messenger Popup Spam on UDP Port 1026"
- Next in thread: Rick Updegrove: "Re: [Dshield] Re: [Full-Disclosure] Windows Messenger Popup Spam on UDP Port 1026"
- Reply: Rick Updegrove: "Re: [Dshield] Re: [Full-Disclosure] Windows Messenger Popup Spam on UDP Port 1026"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To: full-disclosure@lists.netsys.com Date: Sat, 21 Jun 2003 17:17:46 -0700
On Sat, Jun 21, 2003 at 09:41:18PM +0200, Dietmar Goldbeck wrote:
> If ISPs start blocking ports, i would vote for tcp/25.
> People should not be allowed to run smtp servers, unless
> they have proven knowledge in the relevant RFCs. :-))
You're a little behind the curve -- blocking outbound port 25 is
becoming more and more standard, especially with some of the larger ISPs
(e.g. earthlink) as a spam-blocking measure.
-roy
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
- Previous message: JT: "RE: [Full-Disclosure] Destroying PCs remotely?"
- In reply to: Dietmar Goldbeck: "Re: [Dshield] Re: [Full-Disclosure] Windows Messenger Popup Spam on UDP Port 1026"
- Next in thread: Rick Updegrove: "Re: [Dshield] Re: [Full-Disclosure] Windows Messenger Popup Spam on UDP Port 1026"
- Reply: Rick Updegrove: "Re: [Dshield] Re: [Full-Disclosure] Windows Messenger Popup Spam on UDP Port 1026"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|