[80200] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Port 25 - Blacklash

daemon@ATHENA.MIT.EDU (Alexei Roudnev)
Wed Apr 27 04:17:03 2005

From: "Alexei Roudnev" <alex@relcom.net>
To: "Daniel Golding" <dgolding@burtongroup.com>,
	"Hank Nussbacher" <hank@mail.iucc.ac.il>,
	"Adam Jacob Muller" <adam@gotlinux.us>
Cc: "Nanog Mailing list" <nanog@merit.edu>
Date: Wed, 27 Apr 2005 01:11:03 -0700
Errors-To: owner-nanog@merit.edu


Hmm, the onses who block everything and cut wires off send 0 spam. So what?

----- Original Message ----- 
From: "Daniel Golding" <dgolding@burtongroup.com>
To: "Hank Nussbacher" <hank@mail.iucc.ac.il>; "Adam Jacob Muller"
<adam@gotlinux.us>
Cc: "Nanog Mailing list" <nanog@merit.edu>
Sent: Tuesday, April 26, 2005 2:50 PM
Subject: Re: Port 25 - Blacklash


>
>
> Do all of Comcast's markets block port 25? Is there a correlation between
> spam volume and the ones that do (or don't)?
>
> In any event the malware is already ahead of port 25 blocking and is
> leveraging ISP smarthosting. SMTP-Auth is the pill to ease this pain/
>
> - Dan
>
>
> On 4/26/05 2:49 PM, "Hank Nussbacher" <hank@mail.iucc.ac.il> wrote:
>
> >
> > On Tue, 26 Apr 2005, Adam Jacob Muller wrote:
> >
> > Doesn't seem to be stemming the tide of emails from Comcast though:
> >
>
<http://www.senderbase.org/?searchBy=organization&searchString=Comcast%20Cab
le>
> >
> >
> > -Hank
> >
> >> For example, about 2 months ago, comcast decided to block outgoing
> >> port 25 from my entire neighborhood. I called comcast, and while
> >> sitting on hold I had the idea to setup a ssh tunnel to a machine at
> >> work and viola problem solved before anyone from comcast even
> >> answered the phone.
>
>


home help back first fref pref prev next nref lref last post